[opensuse-factory] fsck prblms with latest update, 27 Sept
x86_64 11.2 M7 kde4 kernel-default-2.6.31-8.3.x86_64 Completed the updates from the build over the weekend and had a zipper notice that *many* of the running applications had been deleted (replaced) and suggested restarting them. There were so many I opted to restart the system. My system has 6 internal drives, 3 sata and 3 ata, and 1 external sata which combine to provide a lot of space. They are formatted ext3, ext4 and vfat. Within this arrangement I maintain a large lvm drive for storing photographs. When rebooting I get the message that an fsck.ext3 has failed noting the lvm drive suggesting fsck the errant file system and dropping to maintenance mode. There is notice that the filesystem cannot be mounted for too many open inodes (from memory, may not be complete accurate). Performing, fsct.ext3 -a /dev/mapper/pictures-Pix-lvm, completes successfully with no errors found. ctrl-D to reboot and I get the same messages and problem. note: I have bypassed the problem by commenting the lvm drive in /etc/fstab, booting, and then removing the comment and mounting the lvm drive. System originates from install of: openSUSE-kde-11.2-livecd-kde-read-only.x86_64-2.8.0 and regular zdup updates since. What to do? What package is causing the problem and does it deserve a bug report? -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sunday 27 September 2009 11:19:17 pm Patrick Shanahan wrote:
x86_64 11.2 M7 kde4 kernel-default-2.6.31-8.3.x86_64
Completed the updates from the build over the weekend and had a zipper notice that *many* of the running applications had been deleted (replaced) and suggested restarting them. There were so many I opted to restart the system.
My system has 6 internal drives, 3 sata and 3 ata, and 1 external sata which combine to provide a lot of space. They are formatted ext3, ext4 and vfat. Within this arrangement I maintain a large lvm drive for storing photographs.
When rebooting I get the message that an fsck.ext3 has failed noting the lvm drive suggesting fsck the errant file system and dropping to maintenance mode. There is notice that the filesystem cannot be mounted for too many open inodes (from memory, may not be complete accurate).
Performing, fsct.ext3 -a /dev/mapper/pictures-Pix-lvm, completes successfully with no errors found.
ctrl-D to reboot and I get the same messages and problem.
note: I have bypassed the problem by commenting the lvm drive in /etc/fstab, booting, and then removing the comment and mounting the lvm drive.
System originates from install of: openSUSE-kde-11.2-livecd-kde-read-only.x86_64-2.8.0 and regular zdup updates since.
What to do? What package is causing the problem and does it deserve a bug report?
Patrick, Two thoughts on two changes (to linux in general in the past week or so) that may be involved. dmraid has been updated and timezone data has changed. I haven't been following 11.2 development to know where this stands in factory, but for some of the other distros, these changes have caught a couple of folks. If there is something that has changed with the timezone data and the sysclock is getting set in the past on boot when it reads the hwclock, that will cause the exact behavior you are seeing. I saw a release not that accompanied the dmraid update that applies specifically to LVM setups. (I can't recall the exact language, I don't have LVM) That release note may address your issue as well. Check and then hit the del key. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
* David C. Rankin <drankinatty@suddenlinkmail.com> [09-29-09 17:45]:
Two thoughts on two changes (to linux in general in the past week or so) that may be involved. dmraid has been updated and timezone data has changed. I haven't been following 11.2 development to know where this stands in factory, but for some of the other distros, these changes have caught a couple of folks. If there is something that has changed with the timezone data and the sysclock is getting set in the past on boot when it reads the hwclock, that will cause the exact behavior you are seeing.
The only recent timezone changes/updates I see relate directly to kde which shouldn't affect the system boot before starting X and to YaST which appear to be for making changes/adjustments after the fact or during installation.
I saw a release not that accompanied the dmraid update that applies specifically to LVM setups. (I can't recall the exact language, I don't have LVM) That release note may address your issue as well.
18:59 wahoo:~ > rpm -q --last dmraid dmraid-1.0.0.rc15-7.2 Tue 01 Sep 2009 09:23:40 AM EDT so, probably not this as I have rebooted several times for kernel updates since 01 Sept.
Check and then hit the del key.
?? tks, -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (2)
-
David C. Rankin
-
Patrick Shanahan