![]() | ||||||||||
Messages in this thread |
On Thursday 2008-05-08 01:14, Morten Welinder wrote: >> Suppose you had an N GB file that just filled up the disk. You now >> delete it, but get control back before it is really deleted. You >> now start to write a new file that will eventually just fill up >> the disk. [...] > >NFS does not do that -- in fact, I don't believe any file system does that >unless you can guarantee at least that no other process or the kernel has >that file open; Iff a process still has the file open, your unlink will succeed immediately anyway, and the real deallocation takes place when the last process runs close(). Which shows an interesting fact too: not only unlink can block. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2008-05-11 12:33 [from the cache] ©2003-2008 | ||||||||||