From: Greg Bradner <gregb@rhythm.com>
To: autofs@linux.kernel.org
Subject: mounting problem
Date: Fri, 03 Jun 2005 06:41:53 -0700 [thread overview]
Message-ID: <42A05E21.4090802@rhythm.com> (raw)
This happens with autofs or using mount directly.
However I mount the 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
Has anyone seen this before? This is stock SuSE 9.2. Thanks for any help.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> rpm -qa | grep autofs
autofs4-4.0.0-105
> uname -ar
Linux lid2 2.6.5-7.112-suse #6 SMP Wed Mar 23 10:16:11 PST 2005 i686
athlon i386 GNU/Linux
> cat /etc/issue
Welcome to SuSE Linux 9.2 (i586)
> /usr/sbin/automount -V
Linux automount version 4.1.3
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
gregb@rhythm.com
next reply other threads:[~2005-06-03 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 13:41 Greg Bradner [this message]
2005-06-03 16:07 ` mounting problem Jeff Moyer
-- strict thread matches above, loose matches on Subject: below --
2005-06-15 13:46 Greg Bradner
2002-02-20 6:49 nimeesh
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=42A05E21.4090802@rhythm.com \
--to=gregb@rhythm.com \
--cc=autofs@linux.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.