From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Urban Widmark <urban@teststation.com>
Cc: <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
pdan@spiral.extreme.ro
Subject: Re: netfs allows multiple identical mounts (was: smb/mount
Date: Wed, 8 Aug 2001 14:00:10 MET-1 [thread overview]
Message-ID: <32C99E30BA@vcnet.vc.cvut.cz> (raw)
On 8 Aug 01 at 1:20, Urban Widmark wrote:
> On Mon, 6 Aug 2001, Dan Podeanu wrote:
> > This should be self explanatory. My guess is, its probably the smb
> > filesystem reporting as mounting again a share after network failure.
>
> A very simple way to reproduce this (on 2.4.7):
>
> $ mount -t smbfs -o username=puw //srv/share /mnt/smb
> $ mount -t smbfs -o username=puw //srv/share /mnt/smb
> $ cat /proc/mounts | grep smbfs
> //srv/share /mnt/smb smbfs rw 0 0
> //srv/share /mnt/smb smbfs rw 0 0
>
> This is probably something that smbmount could check before mounting.
> But I'm not sure if that is the best fix.
For sure it is, as doing
mount -t smbfs -o username=a //srv/share /mnt/smb
mount -t smbfs -o username=b //srv/share /mnt/smb
looks quite legal to me, as both //srv/share can display completely
different set of files, and nobody except smbfs knows that username=a/
username=b matters, but fmode=700/fmode=755 does not...
> It could compare the server string ("//srv/share") but what if that server
> listens to more than one name?
ncpfs (mount.ncp) will warn you if //srv/share is listed anywhere in
/etc/mtab and it is mounted by you. If you'll use '-o multiple', then
it is assumed that you know what you are doing, and nothing prevents you
from mounting same thing on same place 255 times.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2001-08-08 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 14:00 Petr Vandrovec [this message]
2001-08-09 7:52 ` Urban Widmark
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32C99E30BA@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pdan@spiral.extreme.ro \
--cc=trond.myklebust@fys.uio.no \
--cc=urban@teststation.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®