[Bug 809226] New: unable to shutdown the system
https://bugzilla.novell.com/show_bug.cgi?id=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c0 Summary: unable to shutdown the system Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: chris@infosun.fim.uni-passau.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 I made an update installation of openSUSE 12.3 final over openSUSE 12.2. In 12.2 shutdown issues were NOT present. After a shutdown command the system hangs: no output, no log, no HW power off. Using log off or restart in kde or graphical login manager, using reboot, shutdown -h -P now, shutdown -h now, shutdown -r now, reboot, halt, halt -p on a (root) console is all the same. Using acpi=off or fail safe boot mode does not help. My mainboard is an Intel 5 Series DP55WG if this should be of interest. What type of log file should I provide? /var/log/messages, /var/log/boot.log and dmesg shows nothing significant, at least for me. Reproducible: Always Steps to Reproduce: 1. start system 2. shutdown via different possibilities, eg, shutdown -h now from console 3. Actual Results: The systems hangs and does not react. Gettys on ALT-STRG-F2 to F6 are gone (cursor blinks) -F7 is empty, F10 -shows the start log. Changing these consoles is the only thing I can do in this situation, despite of a HW-reset. Expected Results: List of services stop and finally a message System stopped and HW power off. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c1 --- Comment #1 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-14 05:07:44 UTC --- Unnecessary to say that I have already tried Auto, Halt, Poweroff in yat2 sysconfig > System > Boot > HALT . Although the yast module brings an error while calling /sbin/SuSEconfig which is gone. See Bug 784654 . I always use the kernel boot parameter splash=verbose (eliminating this parameter does not help) so that I can see what is going on. Btw, although configured in sysconfig, I do not hear the halt sound. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c FeiXiang Zhang <fxzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |werner@suse.com |ovo.novell.com | -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c2 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |werner@suse.com AssignedTo|werner@suse.com |fcrozat@suse.com --- Comment #2 from Dr. Werner Fink <werner@suse.com> 2013-03-14 07:36:46 UTC --- This is systemd not SysVinit, reassign to correct maintainer -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c3 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |chris@infosun.fim.uni-passa | |u.de --- Comment #3 from Frederic Crozat <fcrozat@suse.com> 2013-03-14 09:06:04 UTC --- please have a look at http://freedesktop.org/wiki/Software/systemd/Debugging#Diagnosing_Shutdown_P... and give us the debug trace. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c4 --- Comment #4 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-14 10:46:21 UTC --- Created an attachment (id=529681) --> (http://bugzilla.novell.com/attachment.cgi?id=529681) dmesg > dmesg.txt during hang -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c5 --- Comment #5 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-14 10:47:16 UTC --- Created an attachment (id=529682) --> (http://bugzilla.novell.com/attachment.cgi?id=529682) last lines, containing all messages during shutdown -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c6 Christian Bachmaier <chris@infosun.fim.uni-passau.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|chris@infosun.fim.uni-passa | |u.de | --- Comment #6 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-14 10:47:36 UTC --- Worked through the guide: 1. Waiting 10 mnutes after the hang does not help. The shutdown (now always exectued by 'reboot' never finishes. Pressing CTRL+ALT+DEL does nothing during hang. 2. 'sync && reboot -f' operates as desired, so probably no kernel issue. 3. Boot with systemd debug Options (HW reset necessary after 10 minutes) delivers no log file. Probably as the shutdown never finishes. 4. Unfortunately, the Computer das no serial connector to use ttyS0 for Debugging. 5. On the debug Shell tty9 using 'systemctl list-jobs' delviers only an error message 'Failed to get D-Bus Connection: ...' during the hang. 6. The output of dmesg during hang executed on the debug Shell is attached as a file. The last lines indicate that there are some unresolvable dependencies which prevents the shutdown. I also have attached the last lines of /var/log/message . @Frederic: thanx for your help. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c Christian Bachmaier <chris@infosun.fim.uni-passau.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c7 --- Comment #7 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-14 13:51:03 UTC --- Created an attachment (id=529725) --> (http://bugzilla.novell.com/attachment.cgi?id=529725) journalctl -a > journalctl.txt during hang -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c8 --- Comment #8 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-14 13:52:15 UTC --- Btw. I am using kernel-default, and not kernel-desktop. Hope that is not the problem... -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c9 --- Comment #9 from Frederic Crozat <fcrozat@suse.com> 2013-03-14 14:08:40 UTC --- (In reply to comment #8)
Btw. I am using kernel-default, and not kernel-desktop. Hope that is not the problem...
clearly not, don't worry :) -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c10 --- Comment #10 from Frederic Crozat <fcrozat@suse.com> 2013-03-14 14:08:55 UTC --- dmesg output is incomplete. Could you post dmesg output after boot but before initiating shutdown (with systemd.log_level=debug systemd.log_target=kmsg on kernel command line) ? I saw iscsi for your rootfs ? -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c11 --- Comment #11 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-14 18:10:37 UTC --- Created an attachment (id=529777) --> (http://bugzilla.novell.com/attachment.cgi?id=529777) dmesg > dmesg_after_boot.txt after booting with syslogd debug kernel params set I completely deinstalled openiscsi rpm, although systemctl said was not active. Wtf? However, this does not change anything. Afterwards I created the demanded dmesg 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c12 --- Comment #12 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-14 20:09:43 UTC --- I think I have found the trigger of the problem. Executing 'systemctl stop nfsserver.service' empties the directory /proc ! I never have seen something likewise before. This is only true if /etc/exports is not empty. However, before shutting down the exports work like a charm and can be mounted. My current content of /etc/exports is /srv/export *(bind=/,rw,fsid=0,insecure,no_root_squash,sync,no_subtree_check) /srv/export/bak *(bind=/bak,rw,nohide,no_root_squash,sync,no_subtree_check) It is the same configuration which I used under SUSE 12.2 and some version before without any problem. Of course /srv/export ... directories exist. I cannot see any configuration error. Now I have disabled the nfs server with 'systemctl disable nfsserver.service' and shutting down works like a charm. However, this stays a no go. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c15 --- Comment #15 from Frederic Crozat <fcrozat@suse.com> 2013-03-15 09:51:48 UTC --- (In reply to comment #12)
I think I have found the trigger of the problem. Executing 'systemctl stop nfsserver.service' empties the directory /proc ! I never have seen something likewise before. This is only true if /etc/exports is not empty. However, before shutting down the exports work like a charm and can be mounted.
My current content of /etc/exports is
/srv/export *(bind=/,rw,fsid=0,insecure,no_root_squash,sync,no_subtree_check) /srv/export/bak *(bind=/bak,rw,nohide,no_root_squash,sync,no_subtree_check)
Reproduced. It think it is related to bind=/ I'll investigate. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c16 --- Comment #16 from Frederic Crozat <fcrozat@suse.com> 2013-03-15 12:50:26 UTC --- The error wasn't in systemd but in /etc/init.d/nfsserver which was writing warnings to /run/nfs/bind.mounts instead of stderr, causing all kind of crazy unmount.. Please test package from http://download.opensuse.org/repositories/home:/fcrozat:/branches:/openSUSE:... (it would be available in a few minutes), it fixes the issue for me. -- 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=809226
https://bugzilla.novell.com/show_bug.cgi?id=809226#c17
--- Comment #17 from Dr. Werner Fink <werner@suse.com> 2013-03-15 13:07:28 UTC ---
Why is writting to stdout cause such an error? Shouldn't stdout not be
connected to the same device as stderr? Is this realted to bug #728774 ?
@@ -103,10 +103,10 @@
sort |
while read export dir; do
if [ $warned = no ] ; then
- echo
- echo "NFS: The usage of 'bind=' in /etc/exports is deprecated."
- echo "NFS: Is it no longer needed and may cease to work."
- echo "NFS: Please remove these settings."
+ echo >&2
+ echo "NFS: The usage of 'bind=' in /etc/exports is deprecated."
>&2
+ echo "NFS: Is it no longer needed and may cease to work." >&2
+ echo "NFS: Please remove these settings." >&2
warned=yes
fi
test -d "$export" || mkdir -p "$export"
--
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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c18 --- Comment #18 from Frederic Crozat <fcrozat@suse.com> 2013-03-15 14:32:39 UTC --- (In reply to comment #17)
Why is writting to stdout cause such an error? Shouldn't stdout not be connected to the same device as stderr? Is this realted to bug #728774 ?
It is not, it is writing to /run/nfs/binds.mount instead of stdout / stderr :) I just used stderr because it looked better (and also because stdout is redirected to /run/nfs/bind.mounts in this part of the shell, see line 115 -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c19 --- Comment #19 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-15 16:07:49 UTC --- Yep, that fixes the issues. Looking forward to see an official update in the near future. Although I have doubts like Werner whether this is/was a rock stable implementation with redirecting stdout to the mount file. However, if bind= is deprecated, why is there is not any word about that in the official documentation http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n..., which in contrast make highly use of it, or why there are not any changes in Yast > NFS-Server? Further, what is the suggested alternative? Some mount -bind ... entries in /etc/fstab , then I would like to have the bind= option back. @Frederic: thanx for your prompt help! -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c20 --- Comment #20 from Neil Brown <nfbrown@suse.com> 2013-03-20 05:44:17 UTC --- The deprecation has not filtered out because while I maintain nfs-utils I don't maintain the documentation (I didn't even know it existed to be honest, though logically it must) and I just haven't thought about who I should tell. bind= still works, but it is completely unnecessary with current nfs-utils. If you have no "bind=" in your /etc/exports, and no "fsid=0" either, then NFSv4 will "just work" exactly like NFSv3 and v2 do. So if you export "/foo/bar/baz", then from the client you can mount -o vers=4 server:/foo/bar/baz and get exactly what you expect. "mountd" and the kernel work together to do equivalent magic that used to be done by "bind=". -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c21 --- Comment #21 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-20 17:59:18 UTC --- Ok, tried as Neil suggested / *(rw,insecure,no_root_squash,sync,no_subtree_check) /bak *(rw,no_root_squash,sync,no_subtree_check) /srv/tftpboot/systemrescuecd *(ro,no_subtree_check,all_squash,insecure) instead of my original operating config /srv/export *(bind=/,rw,fsid=0,insecure,no_root_squash,sync,no_subtree_check) /srv/export/bak *(bind=/bak,rw,nohide,no_root_squash,sync,no_subtree_check) /srv/tftpboot/systemrescuecd *(ro,no_subtree_check,all_squash,insecure) in /etc/exportfs . As you may notice, in my original config the third entry is an nfs3 export since systemrescuecd linux cannot boot over nfs4. However, the both first entries as nfs 4, as they contain fsid and or bind. The docu http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.n... says (what is imho correct):
NFSv3 and NFSv4 exports can coexist on a server. After enabling the support for NFSv4 in the initial configuration dialog, those exports for which fsid=0 and bind=/target/path are not included in the option list are considered v3 exports.
Thus the suggested config at the top only exports via nfs3, ie, 'mount -o vers=4 server:/bak /mnt' or 'mount server:/bak /mnt' fail, ie, they hang for at least 5 minutes! Although both should automatically fall back to nfs3, as man nfs tells:
nfsvers=n The NFS protocol version number used to contact the server's NFS service. If the server does not support the requested version, the mount request fails. If this option is not specified, the client negotiates a suit- able version with the server, trying version 4 first, version 3 second, and version 2 last.
It is very likely that Neil's test was over nfs3. In /etc/sysconfig/nfs I have set USE_KERNEL_NFSD_NUMBER="4" NFS3_SERVER_Support="yes" which should be correct, but maybe that is of interest. For the suggested version: Executing 'mount -o nfsvers=3 server:/ /mnt' logs
2013-03-20T18:50:29.576808+01:00 server rpc.mountd[8598]: Cannot export /, possibly unsupported filesystem or fsid= required in the clients /var/log/messages
A further reason pro bind=... . Under /bak I have a different file system mounted as under /, ie, a partition on another hard disk. Using my configuration makes it possible on the client with a simple 'mount server:/ /mnt' to have full access to /mnt/bak = /bak on the server. Please note that the provided examples are a simplifies version of my server config, eg, I use Kerberos. If you are asking me, bind= is useful and necessary in the current situation. It should not be deprecated. The only option I see is to use bind-mounts within /etc/fstab, which will always be present even if the nfsserver is not running, however. @Neil: What is your advice? -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c22 --- Comment #22 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-20 18:13:24 UTC ---
Thus the suggested config at the top only exports via nfs3, ie, 'mount -o vers=4 server:/bak /mnt' or 'mount server:/bak /mnt' fail, ie, they hang for at least 5 minutes!
Maybe these hangs are gone if executing the mount commands on a different client machine, not on the server itself. !!!!!! However, the exports seem to be nfs3. !!!!!! With my config 'mount server:/ /mnt' is no problem.
For the suggested version: Executing 'mount -o nfsvers=3 server:/ /mnt' logs
2013-03-20T18:50:29.576808+01:00 server rpc.mountd[8598]: Cannot export /, possibly unsupported filesystem or fsid= required in the clients /var/log/messages
These messages are gone if removing the insecure option. This seems also to trigger the entry as a nfs4 export. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c23 --- Comment #23 from Neil Brown <nfbrown@suse.com> 2013-03-20 21:54:55 UTC --- The "insecure" flag certainly should not affect whether v3 or v4 is chosen. Maybe something else changed at the same time? You description in comment #21 suggested to me that you had only edited /etc/exports and hadn't caused mountd to reload the file. This is done by running either exportfs -av or rcnfsserver reload or similar. You say "seem to be". The easiest way to check is to look in /proc/mounts. I just tried mount localhost:/ /mnt with a /etc/exports similar to your and # grep /mnt /proc/mounts localhost:/ /mnt nfs4 rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,clientaddr=::1,local_lock=none,addr=::1 0 0 clearly shows nfsv4 is being used. -- 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.
su
https://bugzilla.novell.com/show_bug.cgi?id=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c24 --- Comment #24 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-21 19:08:45 UTC --- password:
cat /etc/exports / *(rw,no_root_squash,sync,no_subtree_check,sec=sys:krb5:krb5i:krb5p) /bak *(rw,no_root_squash,sync,no_subtree_check) /srv/tftpboot/systemrescuecd *(ro,no_subtree_check,all_squash,insecure) service nfsserver restart exportfs -av mount localhost:/bak /mnt cat /proc/mounts | grep /mnt server:/bak /mnt nfs rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,mountaddr=fd7c:878c:ae10:5cd4::2,mountvers=3,mountport=49193,mountproto=udp6,local_lock=none,addr=fd7c:878c:ae10:5cd4::2 0 0 umount /mnt mount -o vers=4 localhost:/bak /mnt
mcedit /etc/exports
cat /etc/exports / *(rw,no_root_squash,sync,no_subtree_check) /bak *(rw,no_root_squash,sync,no_subtree_check) /srv/tftpboot/systemrescuecd *(ro,no_subtree_check,all_squash,insecure) service nfsserver restart exportfs -av mount localhost:/bak /mnt cat /proc/mounts | grep /mnt server:/bak /mnt nfs4 rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=fd7c:878c:ae10:5cd4::2,local_lock=none,addr=fd7c:878c:ae10:5cd4::2 0 0
The only change was to eliminate the sec= parameter in the first line... I executed no other cmds in the meanwhile and now this is the full content in my /etc/exportfs. Probably this is the reason why I could not reproduce Neil's advice. Without the sec= param, he seems to be right. My orig. bind= config (above) does not suffer from that. A further problem:
cat /etc/exports / *(rw,no_root_squash,sync,no_subtree_check) /bak *(rw,no_root_squash,sync,no_subtree_check) /srv/tftpboot/systemrescuecd *(ro,no_subtree_check,all_squash,insecure) service nfsserver restart exportfs -av mount localhost:/ /mnt cat /proc/mounts | grep /mnt betty:/ /mnt nfs4 rw,relatime,vers=4.0,rsize=1048576,wslsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /var/run/user/1000/gvfs Output information may be incomplete. ize=1048576,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=fd7c:878c:ae10:5cd4::2,local_lock=none,addr=fd7c:878c:ae10:5cd4::2 0 0 cd /mnt ls -la cd / umount /mnt umount.nfs4: /mnt: device is busy umount -f /mnt umount.nfs4: /mnt: device is busy lsof | grep /mnt lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /var/run/user/1000/gvfs Output information may be incomplete.
I found no suitable way to unmount /mnt then. This behavior only shows when mount / to /mnt. Mounting /bak to /mnt and then unmouting it makes no busy problem. Again, my orig. config with bind= (above) does not have this problem. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c25 --- Comment #25 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-22 05:27:30 UTC --- Note that I cannot try the kerberos features, as kererbos does not start. See bug 810926 . -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c26 --- Comment #26 from Dr. Werner Fink <werner@suse.com> 2013-03-22 07:33:11 UTC --- To be able to unmount busy nfs the option -l for lazy umount may help. From manual page: -l Lazy unmount. Detach the filesystem from the filesystem hierarchy now, and cleanup all references to the filesystem as soon as it is not busy anymore. (Requires kernel 2.4.11 or later.) -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c27 --- Comment #27 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-22 07:44:43 UTC --- I know the -l switch. However, according to my log above, the fs should not be busy: I only switched into it (cd), list files and leave it. When mounting /bak then there is no problem... Why is nfs 3 used when sec= is applied? Is my kereros config (sec=...) wrong or outdated? -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|unable to shutdown the |nfs initscript incorrectly |system |unmounts mountpoints at | |shutdown (bind= directive) -- 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.
su
https://bugzilla.novell.com/show_bug.cgi?id=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c28 --- Comment #28 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-03-30 06:42:38 UTC --- Having the fixed configuration of Kerberos running does not change the picture of my comment 24. However, the sec parameter works for a "sub"-Export. Notice, now sec=... is set only for /bak and neither only for / nor for both / and /bak . password:
cat /etc/exports / *(rw,no_root_squash,sync,no_subtree_check) /bak *(rw,no_root_squash,sync,no_subtree_check,sec=sys:krb5:krb5i:krb5p) /srv/tftpboot/systemrescuecd *(ro,no_subtree_check,all_squash,insecure) service nfsserver restart exportfs -av mount localhost:/bak /mnt cat /proc/mounts | grep /mnt server:/bak /mnt nfs4 rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=xxxx:xxxx:xxxx:xxxx::2,local_lock=none,addr=xxxx:xxxx:xxxx:xxxx::2 0 0
Please, what is the right thing to do, using bind=... further on? Imho comment 24 shows another bug then. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c29 Christian Bachmaier <chris@infosun.fim.uni-passau.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent --- Comment #29 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-04-05 13:53:47 UTC --- Anyone? -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c30 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |chris@infosun.fim.uni-passa | |u.de --- Comment #30 from Neil Brown <nfbrown@suse.com> 2013-04-11 00:48:46 UTC --- I've found a bug that is causing some of your problems, though maybe not all. It particularly affects exporting the root directory with sec= set. I'll attach new nfs-client and and nfs-kernel-server rpms for you to test (rpm -U nfs-kernel-server-1.2.7-0.x86_64.rpm). You shouldn't need to nfs-client rpm, but I'm including it incase 'rpm' complains about version differences. I'll also attach the patch that I applied. Please install the test package, retest, and report. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c31 --- Comment #31 from Neil Brown <nfbrown@suse.com> 2013-04-11 00:49:23 UTC --- Created an attachment (id=534682) --> (http://bugzilla.novell.com/attachment.cgi?id=534682) TEST nfs-kernel-server RPM -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c32 --- Comment #32 from Neil Brown <nfbrown@suse.com> 2013-04-11 00:49:54 UTC --- Created an attachment (id=534683) --> (http://bugzilla.novell.com/attachment.cgi?id=534683) TEST nfs-client rpm (may not be needed) -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c33 --- Comment #33 from Neil Brown <nfbrown@suse.com> 2013-04-11 00:50:37 UTC --- Created an attachment (id=534684) --> (http://bugzilla.novell.com/attachment.cgi?id=534684) Patch applied to create above RPMs -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c34 Christian Bachmaier <chris@infosun.fim.uni-passau.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|chris@infosun.fim.uni-passa | |u.de | --- Comment #34 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-04-11 15:53:41 UTC --- $ rpm -Uhv --oldpackage bug-809226_nfs-kernel-server-1.2.7-0.x86_64.rpm $ mcedit /etc/exports # include sec to / line $ cat /etx/exports / *(rw,no_root_squash,sync,no_subtree_check,sec=sys:krb5:krb5i:krb5p) /bak *(rw,no_root_squash,sync,no_subtree_check,sec=sys:krb5:krb5i:krb5p) /srv/tftpboot/systemrescuecd *(ro,no_subtree_check,all_squash,insecure) $ service nfsserver restart $ exportfs -av exporting *:/bak exporting *:/ exporting *:/srv/tftpboot/systemrescuecd $ mount localhost:/bak /mnt $ cat /proc/mounts | grep /mnt server:/bak /mnt nfs4 rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,port=0,timeo=600,retrans=2,sec=sys,clientaddr=xxxx:xxxx:xxxx:xxxx::x,local_lock=none,addr=xxxx:xxxx:xxxx:xxxx::x 0 0 $ umount /mnt $ mount localhost:/ /mnt $ cat /proc/mounts | grep /mnt server:/ /mnt nfs4 rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp6,timeo=600,retrans=2,sec=sys,clientaddr=xxxx:xxxx:xxxx:xxxx::x,local_lock=none,addr=xxxx:xxxx:xxxx:xxxx::x 0 0 $ # proto=0 is missing compared to above, is this characteristic? $ cd /mnt $ ls -la $ cd / $ umount /mnt umount.nfs4: /mnt: device is busy $ umount -f /mnt umount.nfs4: /mnt: device is busy $ lsof | grep /mnt lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /var/run/user/1000/gvfs Output information may be incomplete. The provided version seems to fix the sec parameter switching back to nfs3 bug for / exports. Unfortunately, the bug to not be able to umount the / export remains. Is it at least reproducable? Does the missing proto=0 as indicated above mean something? @Neil: thanks for your help! -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c35 --- Comment #35 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-04-15 16:11:20 UTC --- The locking seems only to occur when mounting to mount point under / like /mnt or /temp . However, the following works flawlessly. $ mkdir /temp $ mkdir /temp/mnt $ mount localhost:/ /temp/mnt $ cd /temp/mnt $ ls -la $ cd / $ umount /temp/mnt $ Can at least anyone reproduce that? Neil? -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c36 --- Comment #36 from Frederic Crozat <fcrozat@suse.com> 2013-04-18 13:01:54 UTC --- Guys, I gave you the fix for this bug in comment16.. It is just a matter of making sure the warning goes to the stderr and not redirect to the state file.. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c37 --- Comment #37 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-04-19 16:07:09 UTC --- Ok. 2 Bugs seem to be fixed. However one of the tree bugs (comment 34) remains up to now. I am not able to umount a share of a filesystems root dirextory if mounted under a mount point in the root directoy at least at the same host. I could imagine that this bug may also prevent a clean shutdown. So maybe it is wise to treat this seperately in another bug report or with a succeeding update. Frederic, can you at least reproduce it? Seems that Neil gives no answer about reproducability :-/ -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c38 --- Comment #38 from Frederic Crozat <fcrozat@suse.com> 2013-04-19 16:20:04 UTC --- (In reply to comment #37)
Frederic, can you at least reproduce it? Seems that Neil gives no answer about reproducability :-/
sorry but I'm only here to fix systemd bugs (and there is none here, in fact). I was able to fix the initial bug which was basicaly making /proc and /sys unmounted. I didn't try to reproduce nor fix other bugs, since they don't seem related to systemd at all (and my TODO list is huge already). Sorry. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c39 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |chris@infosun.fim.uni-passa | |u.de AssignedTo|fcrozat@suse.com |nfbrown@suse.com --- Comment #39 from Neil Brown <nfbrown@suse.com> 2013-04-23 00:23:52 UTC --- I haven't tried very hard to reproduce it - I've been someone distracted by other things unfortunately. I think I tried once and couldn't easily reproduce it. Can you try to reproduce again and then immediately after the umount fails, wait a few minutes and try again. I'm guessing that something is touching the filesystem that lsof doesn't see for some reason. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c40 Christian Bachmaier <chris@infosun.fim.uni-passau.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|chris@infosun.fim.uni-passa | |u.de | --- Comment #40 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-04-23 16:56:48 UTC --- Waiting 12 minutes did not help. I have suspected autofs, however, shutting down the autofs service before the experiment did not help. Don't know if that says something: while using bind= syntax the problem was not there. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c41 --- Comment #41 from Neil Brown <nfbrown@suse.com> 2013-04-29 07:15:04 UTC --- I've tried again and I can reproduce it. It seems to only happen once. If I "umount -l" the filesystem and then try again, it works. If I then kill and restart mounted, then the next mount attempt will be impossible to unmount with -l. I suspect it is related to subordinate filesystems being automatically mounted under the main mountpoint. e.g. if I "ls -l /mnt", I can see an entry for "/mnt/tmp", but if I try to "ls -l /mnt/tmp" it fails with "Stale NFS file handle". If I then "umount -l" and remount (without killing mountd), then "ls -l /mnt" shows d????????? ? ? ? ? ? tmp suggesting that something is different with /tmp. I'll explore more deeply tomorrow and see if I can figure out what is happening. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c42 --- Comment #42 from Neil Brown <nfbrown@suse.com> 2013-05-02 00:38:13 UTC --- I figured it out. When you mount localhost:/ on /mnt, and then 'ls -l /mnt", one of the things that it tries to 'stat' is /mnt/mnt, which is also /mnt. mountd checkis if it is ok to export /mnt but it isn't (you cannot reexport NFS filesystem). So mountd tell the kernel that /mnt cannot be exported. This information sits in the export cache holding a reference to /mnt So you cannot umount /mnt (it has a reference). The cache entry will time out after 30 minutes after which you should be able to unmount. Alternatively run "exportfs -f". This will flush the cache (a harmless process) and then allow you to unmount. In general if you have been using nfs you might need to "exportfs -f" before an unmount will succeed. (this doesn't explain the strange thing happening with /tmp for me, but that only happens on one machine, so might not be relevant). -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c43 --- Comment #43 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-05-02 15:46:07 UTC --- Thanks! Indeed exportfs -f helps. Is this a feature or a bug? Tend to the latter one. This caching strategy is faulty, if you are asking me. However, now I think it is time to provide an official opensuse patch. 1. error message redirection 2. sec=-parameter issues 3. wrong cache entry At least for 1 und 2, 3 would be nice. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c44 --- Comment #44 from Christian Bachmaier <chris@infosun.fim.uni-passau.de> 2013-05-25 07:25:06 UTC --- Any news on an official patch for such a severe problem? -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c Christian Bachmaier <chris@infosun.fim.uni-passau.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P0 - Crit Sit -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c45 --- Comment #45 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-05-28 02:00:21 CEST --- This is an autogenerated message for OBS integration: This bug (809226) was mentioned in https://build.opensuse.org/request/show/176798 Maintenance / -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |obs:running:1710:moderate -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c46 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #46 from Neil Brown <nfbrown@suse.com> 2013-06-02 19:53:52 UTC --- I've submitted an update for 12.3 to address 1 and 2 (in comment #43). '3' is somewhat harder to fix, and is easy enough to work around, so I don't propose to fix it at present. I may pursue it with upstream in which case a fix will eventually filter into openSUSE. -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c47 --- Comment #47 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-06-02 22:00:09 CEST --- This is an autogenerated message for OBS integration: This bug (809226) was mentioned in https://build.opensuse.org/request/show/177207 Maintenance / -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|obs:running:1710:moderate |obs:running:1710:moderate | |obs:running:1730:moderate -- 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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c48 --- Comment #48 from Swamp Workflow Management <swamp@suse.de> 2013-06-14 09:07:21 UTC --- openSUSE-SU-2013:1012-1: An update that solves one vulnerability and has one errata is now available. Category: security (moderate) Bug References: 809226,813464 CVE References: CVE-2013-1923 Sources used: openSUSE 12.2 (src): nfs-utils-1.2.6-2.16.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=809226 https://bugzilla.novell.com/show_bug.cgi?id=809226#c49 --- Comment #49 from Swamp Workflow Management <swamp@suse.de> 2013-06-14 09:08:51 UTC --- openSUSE-SU-2013:1016-1: An update that solves one vulnerability and has two fixes is now available. Category: security (moderate) Bug References: 809226,813464,817651 CVE References: CVE-2013-1923 Sources used: openSUSE 12.3 (src): nfs-utils-1.2.7-2.6.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.
http://bugzilla.novell.com/show_bug.cgi?id=809226 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:1710:moderate |obs:running:1710:moderate |obs:running:1730:moderate | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=809226 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:1710:moderate | -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com