https://bugzilla.novell.com/show_bug.cgi?id=770962 https://bugzilla.novell.com/show_bug.cgi?id=770962#c0 Summary: umount.nfs return code on busy volumes Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: nfbrown@suse.com ReportedBy: lchiquitto@suse.com QAContact: qa-bugs@suse.de Found By: Community User Blocker: --- This is more of a request for expert advise than a bug report. Older versions of nfs-client, such as the one we ship with SLE 11-SP2 (nfs-client-1.2.3), return error code 16 (EBUSY) when attempting to unmount a busy volume: n76:/mnt # umount.nfs /mnt umount.nfs: /mnt: device is busy n76:/mnt # echo $? 16 Newer versions, such as the one we ship with openSUSE 12.1 (nfs-client-1.2.5), return error code 32: n53:/mnt # umount.nfs /mnt umount.nfs: /mnt: device is busy n53:/mnt # echo $? 32 Which one is correct? Both? The reason I'm asking is that this confuses AutoFS, who tries to make some smart decisions based on the return code. Actually, it tries to distinguish between a successful unmount, an unmount that succeeded but failed to update /etc/mtab and an unsuccessful unmount. -- 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.