Re: debugging nfs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 
I tried to use autofs. However before that I obsevred this:
 
when I manually mount the shared folder on one client, it is not 
possible anymore to mount that on another client even with
"mount" command. That sounds the folder is locked by the first
client. I don't know is it related to mount command or nfs. I
also don't know is it a bug or not.
 
When I looked at mount options for nfs, I noticed "nolock" option.
So instead of "defaults" in /etc/fstab I wrote:
 
server:/opt   /opt   nolock  0  0
 
After a reboot all things are now working fine. So there is no need
to use autofs :)
 
// Naderan *Mahmood;


----- Original Message -----
From: Hiroyuki Sato <hiroysato@xxxxxxxxx>
To: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
Cc: nfs <linux-nfs@xxxxxxxxxxxxxxx>
Sent: Friday, May 6, 2011 5:01 AM
Subject: Re: debugging nfs

Hello Mahmood

What kind of OS are you using??

If you want to use automount, you have to setup automount.
  ex) http://freespace.sourceforge.net/guidod/howto/autofs.html

I you wan to mount /opt at boot time, but now you can't
Could you please check autofs (If you are using RHEL, CentOS, Fedora...)

# /sbin/chkconfig --list netfs
netfs              0:off    1:off    2:off    3:on    4:on    5:on    6:off

--
Hiroyuki Sato


2011/5/6 Mahmood Naderan <nt_mahmood@xxxxxxxxx>:
> Hi Hiroyuki,
>
> I tried what you said, but no success. Here are the configs:
>
> on server:
>
> root@server:~# cat /etc/hosts
> 127.0.0.1       localhost     localhost,server
> 194.225.69.105  server
> 192.168.1.3     client1
> 192.168.1.4     client2
>
> root@server:~# cat /etc/exports
> /home/nfsroot        192.168.1.0/255.255.255.0(rw,async,no_root_squash)
> /opt                 192.168.1.0/255.255.255.0(rw,sync,no_root_squash)
>
> root@server:~# cat /etc/hosts.allow
> sendmail: all
> ALL: 192.168.1.0/255.255.255.0
>
>
>
> On clients:
>
> mahmood@client1:~$ cat /etc/fstab
> # UNCONFIGURED FSTAB FOR BASE SYSTEM
> # <file system> <mount point> <type> <options> <dump> <pass>
> proc            /proc         proc   defaults       0      0
> /dev/nfs        /             nfs    defaults       0      0
> 192.168.1.1:/opt       /opt          nfs    defaults       0      0
>
> mahmood@client1:~$ cat /etc/hosts
> 127.0.0.1 localhost
> 192.168.1.1 server
> 192.168.1.3 client1
> 192.168.1.4 client2
>
>
> However, there is no sign of proper automount:
>
> mahmood@client1:~$ ls /opt/
> mahmood@client1:~$
>
>
> // Naderan *Mahmood;
>
>
> ----- Original Message -----
> From: Hiroyuki Sato <hiroysato@xxxxxxxxx>
> To: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
> Cc: Brian R Cowan <brcowan@xxxxxxxxxx>; nfs <linux-nfs@xxxxxxxxxxxxxxx>
> Sent: Thursday, May 5, 2011 7:55 PM
> Subject: Re: debugging nfs
>
> Hello Mahmood.
>
> Have you ever tried to write ip address instead of server fqdn??
> or have you ever tries write server entry in /etc/hosts??
>
> It is mean that
>
> /etc/fstab
> ip.ad.re.ss:/opt /opt nfs mount_opt 0 0
>
> or /etc/hosts
> ip.add.re.ss server
>
>
> I met same problem today, and I resolve it.
>
> My friend were using NIS on scientific linux .
> and It tried to mount before NIS started.
>
> --
> Hiroyuki Sato
>
>
> 2011/5/5 Mahmood Naderan <nt_mahmood@xxxxxxxxx>:
>> Well, I found the problem very nasty and in my previous posts, I mentioned some of them.
>>
>> The big problem:
>> when the clients boots, it doesn't automatically mount the shared folders via /etc/fstab.
>> However after login to client, I can mount the folder manually with
>>
>> "sudo mount -t nfs server:/opt /opt"
>>
>> I really don't know why fstab doesn't work. I searched a lot.... some say disbale IPV6.
>> I did that but still have that problem.
>>
>> So how can I tell nfs (on server or client) to be verbose so that I can see what is going on
>> and what is not going on.
>>
>> Any feedback and comment is welcomed.
>>
>> // Naderan *Mahmood;
>>
>> From: Brian R Cowan <brcowan@xxxxxxxxxx>
>> To: Mahmood Naderan <nt_mahmood@xxxxxxxxx>
>> Cc: nfs <linux-nfs@xxxxxxxxxxxxxxx>; linux-nfs-owner@xxxxxxxxxxxxxxx
>> Sent: Thursday, May 5, 2011 6:40 PM
>> Subject: Re: debugging nfs
>>
>>
>> It would probably help to explain the problem
>> so you can get targeted debugging assistance...
>>
>> =================================================================
>> Brian Cowan
>> Advisory Software Engineer
>> ClearCase Software Advisory Team (SWAT)
>> Rational Software
>> IBM Software Group
>> 550 King St
>> Littleton, MA 01460
>>
>> Phone: 1.978.899.9471
>> Web: http://www.ibm.com/software/rational/support/
>>
>>
>>
>>
>> From:
>>  Mahmood Naderan <nt_mahmood@xxxxxxxxx>
>> To:
>>  nfs <linux-nfs@xxxxxxxxxxxxxxx>,
>> Date:
>>  05/05/2011 09:30 AM
>> Subject:
>>    debugging nfs
>> Sent by:
>>    linux-nfs-owner@xxxxxxxxxxxxxxx
>>
>>
>>
>> Hi,
>> I didn't find a method for debugging NFS for debain based systems. Is there
>> any verbose switch or debuging method for that?
>>
>> // Naderan *Mahmood;
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs"
>> in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux