Re: ext2 errors w/2.5.x

David S. Miller (davem@redhat.com)
Mon, 17 Jun 2002 21:17:02 -0700 (PDT)


From: Andrew Morton <akpm@zip.com.au>
Date: Mon, 17 Jun 2002 21:15:46 -0700

Andreas Dilger wrote:
> On Jun 17, 2002 19:56 -0700, David S. Miller wrote:
> > EXT2-fs error (device sd(8,17)): ext2_find_entry: zero-length directory entry
>
> This would appear to be from accessing a buffer (page) which has not yet
> been read from disk. Otherwise you would have an error from e2fsck also.
> Andrew has been mucking the most in this area...

Not that, I hope. Possibly it's the interaction between
block_write_full_pages's memset outside i_size, truncate and lookup.
It took me a ridiculous amount of time to get that "correct", so
it's a suspicion point. Or possibly locking between lookup and
truncate (rmdir) and/or creat.

Dave, I assume this is with 8k pages and 4k blocks?

Yes, that is the case here.

Is it repeatable enough to conduct a little experiment? Like, lock the page
in ext2_find_entry?

I'll try out your patch and get back to you, thanks.

Franks a lot,
David S. Miller
davem@redhat.com
-
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/