https://bugzilla.novell.com/show_bug.cgi?id=626580
https://bugzilla.novell.com/show_bug.cgi?id=626580#c20
Petr Uzel
Yes - since I switched off RUN_PARALLEL, the partitions got always unmounted.
OK, so it seems disabling RUN_PARALLEL helps. Werner, could you please look into this? I think the following part of /etc/init.d/halt is interesting, however, I'm afraid I don't know how to debug this further. (Furthermore, this doesn't seem to be util-linux/umount issue). -------------- if test -z "$COLD_BOOT" ; then # # set back system boot configuration # if test "$RUN_PARALLEL" = "yes" ; then startopt="-p4 -t 30 -T 3" eval $(startpar $startopt -M halt) unset failed_service skipped_service elif test -d /etc/init.d/boot.d/ ; then # # call modules in boot.d via K* symlinks # for link in /etc/init.d/boot.d/K[0-9][0-9]*; do test -x $link || continue $link stop done unset link fi fi --------------
But this does not mean, that all of the filesystems are going to be unmounted cleanly. Sometimes, the /var and/or /home-partition can't be unmounted cleanly, because they have open files.
What do you mean by "not cleanly unmounted"? - either the FS is busy and it is not unmounted at all, or it is not busy and it is cleanly unmounted. (Do you mean that umount is called, but fails?) -- 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.