Re: Filesystem check

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03-May-2006 10:42.37 (BST), Emeric Maschino wrote:
 > Indeed, at startup, once the logical volumes are configured and
 > activated, my filesystem is checked but the check fails with the
 > following message:
 > e2fsck: Cannot continue, aborting.
 [snip]
 > Yesterday, I had the bad idea to finally enter the root password and
 > manually run fsck as requested. Of course, this ended up with a totally
 > corrupted filesystem.
 [snip]
 > Any hint ? This is on an Itanium workstation (ia64) and I don't know if
 > this problem also appears on other architectures.

Yeah, I'm seeing this too on an x86_64 machine, so I guess it's not
architecture specific. I also have LVM, and an earlier kernel package
works Just Fine(tm). I think the version is 2.6.16-1.2157_FC6, but ICBW
(I'm relying on memory here).

As a future note, I suspect you received filesystem corruption because
the filesystem you ran e2fsck upon was mounted at the time. It might help
to check /proc/mounts to see if the root filesystem is mounted read/write
before running e2fsck by hand, or just perform "mount / -r -o remount" in
a blanket fashion before running e2fsck on the root filesystem.

-- 
rob                               :: pgp 0xb35ff721 :: rob@xxxxxxxxxxxxx

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux