Mike81 n00b
Joined: 05 Jan 2011 Posts: 39
|
Posted: Fri Dec 14, 2012 11:10 am Post subject: Separate portage partition causing unexpected inconsistency? |
|
|
Hello,
I installed some servers following this guide: http://www.gentoo.org/doc/en/gentoo-x86+raid+lvm2-quickinstall.xml
Well, I did not everything... but I created a LVM with volumes for rootfs, swap, portage and distfiles.
Code: | /dev/sda1 -> /boot
/dev/sda2 -> LVM
|
Code: | LVM:
/dev/vg/rootfs
/dev/vg/swap
/dev/vg/portage (I disabled journal for this partition)
/dev/vg/distfiles
|
When I mount everything I have multiple lost+found directories - that's normal I think:
Code: | /boot/lost+found (comes from /dev/sda1 partition)
/lost+found (comes from /dev/vg/rootfs partition)
/usr/portage/lost+found (comes from /dev/vg/portage partition)
/usr/portage/distfiles/lost+found (comes from /dev/vg/distfiles partition)
|
Today we had a power failure. All system crashed.
After power was restored, all systems booted with ro mounted volumes. That was a problem, because network didn't come up. However I was wondering, that no auto fsck fixed the problem. Instead I saw the message
Code: | Unexpected inconsistency, run fsck manually |
I booted each system via SysRescCD and run fsck. Every filesystem was fine, excepted /dev/vg/portage on each system:
Code: | sysrescd ~# fsck.ext4 -f -v /dev/vg/portage
e2fsck 1.42 (29-Nov-2011)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'lost+found' in / (2) is a link to directory /lost+found (6815).
Clear<y>? yes
Entry 'lost+found' in / (2) is a link to directory /lost+found (6815).
Clear<y>? yes
Entry 'lost+found' in / (2) is a link to directory /lost+found (6815).
Clear<y>? yes
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Pass 5: Checking group summary information
portage: ***** FILE SYSTEM WAS MODIFIED *****
...
|
I don't understand this problem. For me it looks like fsck is complaining about "/dev/vg/portage/lost+found". After fsck fixed /dev/vg/portage, this folder was removed. So was /dev/vg/portage/lost+found just broken? Why? Why wasn't /dev/vg/distfiles/lost+found or /dev/vg/rootfs/lost+found or /dev/sda1/lost+found also broken? Has it something to do with the disabled journaling option?
Thanks for any help/explanation. |
|