Package: mount
Version: 2.12r-10
Severity: normal
Hi,
The nfs mount "bg" option is useful when a temporary server problem means
that mount cannot complete immediately but may complete sucessfully some
time soon.
On the other hand, backgrounding is not going to help if the reason for the
failure is a local fault that is not going to go away by itself.
In my case, I had failed to mkdir the mount point before invoking mount.
The resulting message, 'mount: backgrounding "server:/somewhere"', and
behaviour did not point me towards the correct fix.
I note from strace that mount does stat the missing mount point:
stat64("/mountpoint", 0xbfacb594) = -1 ENOENT (No such file or directory)
I suggest that when it gets this result it does not fork a background mount
process and instead reports an error immediately.
Regards
Phil.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages mount depends on:
ii libblkid1 1.38+1.39-WIP-2005.12.31-1 block device id library
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libuuid1 1.38+1.39-WIP-2005.12.31-1 universally unique id library
mount recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
