https://bugzilla.novell.com/show_bug.cgi?id=450196 User mrmazda@ij.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c1 --- Comment #1 from Felix Miata 2008-11-29 02:21:00 MST --- I just remembered that Smart on host gx150 is broken, so zypper dup did the whole job. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450196 User coyli@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c3 coly li changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |coyli@novell.com --- Comment #3 from coly li 2008-12-02 07:22:05 MST --- Could you try "Reboot='cd && umount -a && shutdown -r 0'" ? Because I suspect the umount might not success during reboot. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450196 User coyli@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c5 --- Comment #5 from coly li 2008-12-02 20:29:09 MST --- Yes, that's what I suspected. From your feedback, it seems the file system was not clearly umount during reboot, which resulted fsck in boot time. Could you please to help finding out who was using the file system during reboot ? The 'fuser -v' output might be helpful. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450196 User mrmazda@ij.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c7 --- Comment #7 from Felix Miata 2008-12-02 20:57:21 MST --- Created an attachment (id=257559) --> (https://bugzilla.novell.com/attachment.cgi?id=257559) runlevel 3 sole login output of 'ps -A' after 'umount -a' before first boot on 2.6.27.7-4-pae -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450196 User mrmazda@ij.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c9 --- Comment #9 from Felix Miata 2008-12-02 22:41:53 MST --- (In reply to comment #8 from coly li)

Could you please provide output of fuser from the saem running system ? It could be helpful.

Comment 6 explained I don't know how to use fuser to get what you might want. I don't see options useful for this bug in its man page. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450196 User mrmazda@ij.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c11 --- Comment #11 from Felix Miata 2008-12-03 08:11:35 MST --- Created an attachment (id=257741) --> (https://bugzilla.novell.com/attachment.cgi?id=257741) 'fuser -v -m /dev/hda22' & 'ps -A' output -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450196 User mrmazda@ij.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c13 --- Comment #13 from Felix Miata 2008-12-03 10:17:58 MST --- (In reply to comment #12 from Coly Yong Li)

Wow, quite a lot processes. Could you try to use "Reboot='cd && fuser -kv MOUNTPOINT && umount -a && shutdown -r 0'" to reboot your system ? MOUNTPOINT is the directory which you mount the filesystem.

I don't think I understand this. MOUNTPOINT must be /, since this bug is about forced fsck only on /. However, since this is obvious, maybe you wrote what you wrote because you want the device (hda22) which is mounted on /, and thus I would do?: Reboot='cd && fuser -kv /dev/hda22 && umount -a && shutdown -r 0' -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450196 User mrmazda@ij.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c15 --- Comment #15 from Felix Miata 2008-12-03 11:55:13 MST --- Created an attachment (id=257805) --> (https://bugzilla.novell.com/attachment.cgi?id=257805) dmesg output I haven't really done anything with the system, so this dmesg should be little or no different from having done it contemporaneously with creation of attachment 257741. (In reply to comment #14 from coly li)

Yes, MOUNTPOINT should be /. this is the first time I see hda22 mounted to /, are you sure there are double 2 :)

When I created this bug, / on host gx150 was "Factory" aka 11.1 beta 5.2 on hda10. The original installation was to hda21 (which remains as 11.0), but I cloned it to hda10 to become 11.1 Factory, and allow use of libata, a switch I never made on this system. Yesterday I cloned hda10 to the next available freespace, which became hda22.

But after I know MOUNTPOINT is /, I don't suggest you to try this anymore. Could you tell me how did you update the system ? I will try to reproduce on my workstation.

After cloning, I changed the smart and yast sources from factory to 11.1-RC1, edited fstab & menu.lst to reflect the new / location, and used the grub command line: root (hd0,21); setup (hd0,21). I see now I forgot to update /etc/grub.conf until right now. After the clone and edit operations, I updated nearly everything except kernel using smart. The smart process I normally run through short scripts in order to break the process into bunches instead of downloading everything before installing anything, which is smart's idiotic default behavior. To the best of my recollection, here's approximately how it went: smart update zypper ref zypper in rpm zypper libzypp smart upgrade --yes \*suse\* \*yast\* \*splash\* smart upgrade --yes dbus\* gli\* hal kpartx mkinitrd perl-Bootloader \*splash\* udev smart upgrade --yes z\* y\* x\* mozilla\* \*openSUSE\* smart upgrade --yes k\* f\* m\* s\* t\* u\* v\* w\* opera epiphany smart upgrade --yes a\* b\* c\* d\* e\* g\* smart upgrade --yes zypper in kernel-pae kernel-pae-base Before running zypper kernel*, I started zypper dup, but seeing that another massive amount of updates was proposed, I did not answer yes to continue. I did not subsequently run zypper dup, and doing so now I see a proposal to downgrade many packages, upgrade a few packages, reinstall a significant number of packages, install 2 new packages, and change vendor and arch on several packages. Enabled zypper repos are RC1 oss, RC1 non-oss, packman 11.1, videolan 11.1. I'm a-865 on #opensuse-factory on Freenode, but going out now for a couple of hours. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450196 User coyli@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c17 --- Comment #17 from coly li 2008-12-06 01:47:21 MST --- Sounds great. For previous issue, I guess there is any other network file system hold the resource inside ext4, or something sick inside ext4. But all were guess, need to confirm with more info. I suggest to keep this bug open for a while longer, unless we make sure it could not reproduce in your environment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450196 User mrmazda@ij.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c19 --- Comment #19 from Felix Miata 2008-12-06 19:25:18 MST --- On my 2.4GHz Celeron I just replicated the comment 15 upgrade process (other than different partitions), rebooting immediately afterward with 2.6.27.7-4-pae, and / fsck/recovering journal was required. After smart upgrade & zypper in kernel-pae kernel-pae-base processes and reboot completed, login still shows beta 5.2. Doing zypper dup did 377 packages and transformed into 11.1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=450196 User mrmazda@ij.net added comment https://bugzilla.novell.com/show_bug.cgi?id=450196#c21 --- Comment #21 from Felix Miata 2008-12-19 07:16:42 MST --- I did a 100% zypper upgrade to 11.1 final on the Celeron, which got me 2.6.27.7-9, and again fsck/recovering journal was required. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.