On Wed Jul 04 21:33, Vincent Fourmond wrote:
>
> Hello,
>
> I've recently taken over maintenance of pmount, and I'm going through
> bug reports. I am not convinced that the problem you have is really
> pmount's fault : when I have a stale smb mount and that I ls (--color)
> on the parent directory, it may take a very long while to actually get
> the output.
I've just run such a scenario again. I have a samba mountpoint "/mnt/bulk"
that's gone stale (mounted when I'm on my home network, but now I'm elsewhere,
not a chance of it re-establishing). My current working directory is /root .
Running "pmount -d /dev/cdrom" just hangs - no debugging output. Doing the same
with strace enabled (and running as root - strace clobbers setuid) -
getcwd("/root", 4096) = 6
lstat64("/root/none", 0xbf98b89c) = -1 ENOENT (No such file or directory)
lstat64("/home", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat64("/mnt", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
lstat64("/mnt/bulk", <unfinished ...>
^ this is the point at which it hangs, I hit ctrl+c after about 10 seconds
which yielded the 'unfinished' part. To clarify, it's entirely unnecessary for
pmount to lstat this network mount, it's nothing to do with /dev/cdrom , the
destination mountpoint, or my cwd (which is /root) . Obviously, lstat-ing a
stale network mountpoint hangs while the kernel keeps retrying requests to the
samba server until some timeout (takes about a minute I think?), but there's
really no reason pmount needs to do this. In previous cases, once I've let it
go timeout on that mountpoint, it's gone on to my next stale network mount and
hung similarly. Eventually it gets round to mounting the CD like I told it to
:-)
Richard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
