From: Greg Bradner <gregb@rhythm.com>
To: nfs@lists.sourceforge.net
Subject: mounting problem
Date: Wed, 15 Jun 2005 06:46:16 -0700 [thread overview]
Message-ID: <42B03128.7070807@rhythm.com> (raw)
I'm new to the list and apologize if this is a rehash.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This happens with autofs or using mount directly.
However I mount the NAS disk the first time, the same characteristics
are passed to future mounts.
## This is a read only mount point and you can see the options in the
/proc/mounts file at the bottom
> cd /nfs/ro3/fs14/a/rla/
> df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
fs14:/a/rla 657148928 545010048 112138880 83% /nfs/ro3/fs14/a/rla
## Then when I go to a mount point that shouldn't be read only, it take
the options from the previous mount.
> cd /fs14a/rla/
> df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
fs14:/a/rla 657148928 545010048 112138880 83% /fs14a/rla
> touch test
touch: cannot touch `test': Read-only file system
> tail /proc/mounts
automount(pid3481) /ntap10 autofs rw 0 0
automount(pid3599) /morph autofs rw 0 0
automount(pid3538) /systems autofs rw 0 0
/dev/hda7 /home/gregb ext3 rw 0 0
fs14:/a/jobs /nfs/ro3/fs14/a/jobs nfs
ro,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
fs14:/a/rla /nfs/ro3/fs14/a/rla nfs
ro,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
fs14:/b/rla /nfs/ro3/fs14/b/rla nfs
ro,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
fs14:/root0 /nfs/ro3/fs14/root0 nfs
ro,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
fs14:/root1 /nfs/ro3/fs14/root1 nfs
ro,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
fs14:/a/rla /fs14a/rla nfs
ro,nosuid,nodev,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
What is the culprit and is there a fix?
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
gregb@rhythm.com
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2005-06-15 13:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42B03128.7070807@rhythm.com \
--to=gregb@rhythm.com \
--cc=nfs@lists.sourceforge.net \
/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