On Fri, 2007-05-18 at 15:51 +0200, Martin Mokrejs wrote:
> On Fri, May 18, 2007 at 05:17:06PM +0530, Kalpak Shah wrote:
> > On Fri, 2007-05-18 at 11:06 +0200, Martin Mokrejs wrote:
> > > Hi,
> > > I just tried the 2.6.22-r1 candidate to test whether some bug I have
> > > hit in the past still exists. I did use 2.6.20.6 so far. So, I have
> > > cleanly rebooted to use the new kernel, after the machine came up I
> > > tried to mess with the bug, and had to reboot again to play with kernel
> > > commandline parameters. Unfortunately, on the next reboot fsck was
> > > schedules on my filesystem after 38 clean mounts. :( And the problem
> > > started. The fsck found some unused inodes, but probably did not know
> > > where do they belong to, but it deleted them automagically. Finally, the
> > > fsck died because it cannot fine some '..' entry.
> > >
> > > /dev/hda3: Entry '..' in .../??? (5701636) has deleted/unused inode
> > > 5570561. CLEARED.
> > > Unconnected directory inode 5570567 (...)
> > >
> > > /dev/hda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
> > > (i.e., without -a or -p options)
> > >
> >
> > This means that e2fsck has reached a point where it needs user
> > intervention. So you should not run e2fsck with -p, -a or -y options.
> > Look up the e2fsck man page for more on this.
>
> Yeah, stupid init.d script in Gentoo. I will report at Gentoo as well but
> how can I revert the changes? Can you say which directories were affected?
No there is nothing wrong with your script, most problems get solved by
-a or -p and hence your init.d script is correct in using these options.
I don't understand what you mean by reverting your changes.
An unconnected directory inode means that this directory (inode 5570567)
does not have a valid ".." entry (which is the backpointer to its
parent). So this directory will be moved to lost+found.
Thanks,
Kalpak.
> Thanks,
> Martin
-
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]
