Messages in this thread |  | | Date | Thu, 15 Nov 2001 22:20:55 -0500 | From | Ben Collins <> | Subject | Re: Bug in ext3 |
| |
On Thu, Nov 15, 2001 at 08:09:16PM -0700, Andreas Dilger wrote: > On Nov 15, 2001 19:55 -0500, Ben Collins wrote: > > On Thu, Nov 15, 2001 at 05:07:42PM -0700, Andreas Dilger wrote: > > > What would be interesting to correlate is what inode 48 is (probably a > > > directory, or you wouldn't have noticed it at all), with the corruption > > > problems you are having while ext3 is loaded. > > > > 48 /usr/lib/perl5/5.005/File/Copy.pm > > > > Since this file is pretty small, I can only assume that it overwrote > > some adjacent files. There is some corruption in this file (luckily in > > the comment area :) starting at the 25th byte, and extending 12 bytes in > > length. Here's the values from hexedit: > > > > 00 00 00 01 00 00 00 00 00 00 00 00 > > No, this would be the only expected corruption - there are 3 32-bit > fields that that get written to disk in journal_update_superblock(), > and these are consistent with that. > > That means the source of the other corruption is unknown.
The "other" corruption only occured while booted with the ext3-enabled kernel. They haven't appeared under the non-ext3 kernel at all. Even after it got mounted read-only, performing an fsck, and remounting read-write, it would reoccur over and over. So this "other" corruption doesn't even sound like it can be caused by the scenario you described (which sounds like a one shot problem).
Ben
-- .----------=======-=-======-=========-----------=====------------=-=-----. / Ben Collins -- Debian GNU/Linux \ ` bcollins@debian.org -- bcollins@openldap.org -- bcollins@linux.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/
|  |