mounting problem

mounting problem

[Greg Bradner]

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

mounting problem

[Greg Bradner]

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

Re: mounting problem

[Jeff Moyer]

==> Regarding [autofs] mounting problem; Greg Bradner <gregb@rhythm.com> adds:

gregb> This happens with autofs or using mount directly.

gregb> However I mount the disk the first time, the same characteristics are 
gregb> passed to future mounts.

I can't reproduce this.  Can you please post a procedure to trigger this
without automount?  Exact commandlines would be helpful.

Also, if you can trigger this with mount, then I fail to see how this is an
autofs bug.

Thanks,

Jeff


gregb> ## This is a read only mount point and you can see the options in the 
gregb> /proc/mounts file at the bottom

>> cd /nfs/ro3/fs14/a/rla/

>> df -k .
gregb> Filesystem 1K-blocks Used Available Use% Mounted on
gregb> fs14:/a/rla 657148928 545010048 112138880 83% /nfs/ro3/fs14/a/rla

gregb> ## Then when I go to a mount point that shouldn't be read only, it take 
gregb> the options from the previous mount.
>> cd /fs14a/rla/

>> df -k .
gregb> Filesystem 1K-blocks Used Available Use% Mounted on
gregb> fs14:/a/rla 657148928 545010048 112138880 83% /fs14a/rla

>> touch test
gregb> touch: cannot touch `test': Read-only file system

>> tail /proc/mounts
gregb> automount(pid3481) /ntap10 autofs rw 0 0
gregb> automount(pid3599) /morph autofs rw 0 0
gregb> automount(pid3538) /systems autofs rw 0 0
gregb> /dev/hda7 /home/gregb ext3 rw 0 0
gregb> fs14:/a/jobs /nfs/ro3/fs14/a/jobs nfs 
gregb> ro,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
gregb> fs14:/a/rla /nfs/ro3/fs14/a/rla nfs 
gregb> ro,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
gregb> fs14:/b/rla /nfs/ro3/fs14/b/rla nfs 
gregb> ro,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
gregb> fs14:/root0 /nfs/ro3/fs14/root0 nfs 
gregb> ro,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
gregb> fs14:/root1 /nfs/ro3/fs14/root1 nfs 
gregb> ro,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0
gregb> fs14:/a/rla /fs14a/rla nfs 
gregb> ro,nosuid,nodev,v3,rsize=32768,wsize=32768,hard,intr,udp,lock,addr=fs14 0 0


gregb> Has anyone seen this before?  This is stock SuSE 9.2.  Thanks for any help.


gregb> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> rpm -qa | grep autofs
gregb> autofs4-4.0.0-105

>> uname -ar
gregb> Linux lid2 2.6.5-7.112-suse #6 SMP Wed Mar 23 10:16:11 PST 2005 i686 
gregb> athlon i386 GNU/Linux

>> cat /etc/issue
gregb> Welcome to SuSE Linux 9.2 (i586)

>> /usr/sbin/automount -V
gregb> Linux automount version 4.1.3
 
gregb> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
gregb> gregb@rhythm.com

gregb> _______________________________________________
gregb> autofs mailing list
gregb> autofs@linux.kernel.org
gregb> http://linux.kernel.org/mailman/listinfo/autofs

mounting problem

[nimeesh]

hello sir,

I'm new to linux.I'm trying network booting of linux
system.System Conf.(intel 815 chipset ,PXE
bios,3com905c-ethernet card)

In that i'm facing problem with kernel image and it's
file system.

In that when i get the kernel image and filesystem.
It gives me error as
kernel panic : unable to mount root fs on 01:00

Is it necessary to use NFS or is it possible without
that? Any special specification while creating kernel
image and filesystem?
If any body can tell me any doc available on net,i'll
very thankful.

Thanks in Advance..
nimeesh patel

________________________________________________________________________
Looking for a job?  Visit Yahoo! India Careers
      Visit http://in.careers.yahoo.com