On Friday 19 November 2010 05:14:26 Allan Gottlieb wrote: > Allan Gottlieb <gottl...@nyu.edu> writes: > > Stroller <strol...@stellar.eclipse.co.uk> writes:
> >> You don't have to chroot to run fsck. You can just boot from the LiveCD > >> and run `fsck -o -p -t -i -o -n -s /dev/sda1`. > >> > >> I feel a bit more confident fscking my root filesystem from a LiveCD, > >> because you know that you're not repairing the floor you're standing > >> on, and fsck can have full leeway to do what it needs to do to clear up > >> the problem properly. > > > > The question was about emerge -e world not fsck (see quoted material > > above). > > > > The fsck succeeded prior to this (I did touch /forcefsck; reboot). [snip ...] > I now understand your comment better. I should have run my previous > fsck's under a liveCD. You are right and I am running them again now > under a liveCD. I am please to report that no errors were found. OK, that shows that nothing worse happened by your running fsck while booted into the same fs. As I said this has caused problems for me with reiser4, but not other fs and from what Alan McKinnon said in another thread the fsck.reiser4 is a bit of a suspect command to play with. > So is it now an appropriate time for me to run an > > emerge -e world Yep, let it rip. Good luck! -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
