http://bugzilla.novell.com/show_bug.cgi?id=590744
http://bugzilla.novell.com/show_bug.cgi?id=590744#c7
Richard Creighton changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mailbox@rccj.net
--- Comment #7 from Richard Creighton 2010-07-14 23:24:36 UTC ---
I have a problem that seems related. It seems to be related to the unmount at
shutdown and in my case affects my LVM.
In my case, my LVM handles /home which is ALWAYS fsck'ed when I reboot because
it isn't cleanly unmounted. The other day, I tried a 'umount /home' as root
and fsck'ed it and it was bad without the reboot. Therefore, I think that
even if the shutdown corrupts the LVM, it is not because of the shutdown, it is
because of the unmount operation itself, and like you, I think this may well be
a kernel issue as I doubt 'umount' itself would cause this.
Now, so far, if I switch to root after logging out of the user acct and forego
umounting the /home directory (on the LVM), a fsck shows clean but umount it
and re-run the fsck, more often than not it tells me it is not clean and the
full fsck is required. I have run fsck with the Badblocks check and it found
no bad blocks on the LVM.
This problem was first noticed on 11.3 M7 -> RC1 update. I have tested every
drive in the LVM with a separate diagnostic tool on another machine and it
passes every test and these are quite new drives (WD 1TB drives). I have also
tested overnight with 2 different memory testers (2Gb AMD dual-core 4000+). I
don't believe this to be a hardware problem.
FWIW, it is currently formatted EXT4 but it did the same thing as EXT3.
If this is a different problem, I will file another bug report, but I believe
it is a kernel problem that shows during umount, most often noticed when
shutting down, which seems to be the theme of this bug report.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.