Messages in this thread | | | Date | Fri, 11 Apr 2003 15:40:06 -0700 | From | Andrew Morton <> | Subject | Re: ext3 weirdness |
| |
Andreas Dilger <adilger@clusterfs.com> wrote: > > Because you can't reallocate in-use blocks until the dirty bitmaps have > been committed to disk in a transaction.
Also, in 2.5 pdflush will take a ref on the inode while writing it out. So an unlink while pdflush is writing back the inode's pages will be magically instantaneous, and pdflush actually does the truncate.
This is pretty ugly, because it is reasonable to expect that if you know there are no other refs to the inode, your disk space should be available when the unlink returns.
I don't know what to do about it though. The userspace workaround is to run sync before rm. - 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/
| |