Return-Path: Received: from nm4-vm0.bullet.mail.sp2.yahoo.com ([98.139.91.190]:24574 "HELO nm4-vm0.bullet.mail.sp2.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752159Ab1EGGYs convert rfc822-to-8bit (ORCPT ); Sat, 7 May 2011 02:24:48 -0400 Message-ID: <834642.72983.qm@web111707.mail.gq1.yahoo.com> References: <781436.95809.qm@web111709.mail.gq1.yahoo.com> <591857.64709.qm@web111726.mail.gq1.yahoo.com> <437877.23899.qm@web111716.mail.gq1.yahoo.com> Date: Fri, 6 May 2011 23:24:47 -0700 (PDT) From: Mahmood Naderan Reply-To: Mahmood Naderan Subject: Re: debugging nfs To: Hiroyuki Sato Cc: nfs In-Reply-To: Content-Type: text/plain; charset=iso-8859-1 Sender: linux-nfs-owner@vger.kernel.org List-ID: MIME-Version: 1.0 ? 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 To: Mahmood Naderan Cc: nfs 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 : > 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 > # > 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 > To: Mahmood Naderan > Cc: Brian R Cowan ; nfs > 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 : >> 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 >> To: Mahmood Naderan >> Cc: nfs ; linux-nfs-owner@vger.kernel.org >> 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 >> To: >> ?nfs , >> Date: >> ?05/05/2011 09:30 AM >> Subject: >> ? ?debugging nfs >> Sent by: >> ? ?linux-nfs-owner@vger.kernel.org >> >> >> >> 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@vger.kernel.org >> 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@vger.kernel.org >> 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@vger.kernel.org More majordomo info at? http://vger.kernel.org/majordomo-info.html