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