On September 27, 2002 18:20, Ryan Cumming wrote:
> Okay, got another one:
> "EXT3-fs error (device loop(7,0)): ext3_add_entry: bad entry in directory
> #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=8,
> name_len=0" fsck then reported:
> "Directory inode 2, block 166, offset 0: directory corrupted"
>
> This is while deleteing an old fsstress directory (a full fsck had been
> performed since the last time the fsstress directory had been touched)
> while running a few instances of the attached program.
You can get a 6.1MiB bzip2'ed image of the broken filesystem (fsck hasn't
touched this copy) at:
http://completely.kicks-ass.org/image-broken.ext3.bz2
- -Ryan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (GNU/Linux)
iD8DBQE9lQnrLGMzRzbJfbQRAqhBAJ9EuJ6OhH13W1B4LWjnj8IhyIMX6QCgobUt
gphiPMuRMSdewLp+67phv4g=
=10yO
-----END PGP SIGNATURE-----
-
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/