When using a hardened-sources 2.6.14-r1 kernel the root partition will frequently fail to unmount properly during shutdown causing filesystem corruption requiring an fsck upon next boot of system.
I should add that the problem appears to be solved by running the hardened-sources-2.6.14-r2 ebuild proposed in bug 115771
Created attachment 75575 [details] emerge --info output from hardened-sources 2.6.14-r1 system
This appears to be a regression caused by the hardened patches which is solved in the latest release. In view of this, I'm adding a depend on bug 115771.
Should be solved by -r2 when it hits mirrors.
After futher testing I have found in fact that problem takes place on -r2 kernel as well and simply install does not fix issue as was thought. So far / unmount failure has been reproducible on hardened-2.6.14, hardened-2.6.14-r1, hardened-2.6.14-r2. I am starting to form the opinion after a great deal more testing that the trigger for the issue may in fact lie elsewhere. Still working to determine beyond all doubt actual cause of issue.
Could you please attach your /etc/fstab and briefly explain your disk partition layout for us? anything unusual? lvm root fs fex?
reopening also.
bug #99413 might be somehow related to this one
Created attachment 75628 [details] requested /etc/fstab file from effected system
(In reply to comment #6) > Could you please attach your /etc/fstab and briefly explain your disk partition > layout for us? > anything unusual? lvm root fs fex? > Since this is a test install the setup is not too complex...I do not know if the fact that I used a regular amd64 multilib stage 3 (running on EM64T 3GHZ P4) and then set the needed flags for hardened and CFLAGS as well qualifies. The setup itself is on it's own dedicated 30 gig IDE drive for / and needed swap. Neither LVM nor RAID is being used for those. FS on that drive is EXT3. LVM2 is being used but only to gain access to data from my old install. The old install is in same box. LVM2 on top of md RAID 5 (4x80 Gig SATA WD800JD). I only manually mounted as need to gain access to that data. Mainboard is Asus P5AD2-E Premium with 1 GIG DDR2
Created attachment 75629 [details] config used by a kernel on effected system
Created attachment 75644 [details] output from "ps aux" after giving "root password password for maintience" also after giving root password for maintience as prompted but before running "ps aux" I view the following output from terminal: remounting remaining filesystems readonly. umount: devpts busy -remounted read-only umount: udev busy -remounted read-only umount: /: device is busy umount: /: device is busy umount: /: device is busy
Bug 99413 seems similar enough for this to be a duplicate I reckon (thanks to Petre for the link). *** This bug has been marked as a duplicate of 99413 ***
