On Thu, Apr 28, 2005 at 04:55:36PM -0400, Lennart Sorensen wrote:
>
> I think I have seen this once or twice in the past. A reboot always
> made it go away and it didn't seem to come back. fsck never showed
> anything so I assumed it was just the kernel having lost its mind about
> the state of the FS.
>
> I think I was using 2.4.18 or so at the time I last saw it. It is quite
> a while ago but it was ext3 as well as far as I recall.
That's a different problem; in this case apparently the corruption is
extending to the on-disk superblock accounting information (so fsck is
detecting evidence of it). Fortunately this sort of corruption won't
cause data loss, but we should figure out what the heck is going on.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
