From: "Matt Heaton" Subject: Question about mounting.... Date: Fri, 31 Jan 2003 09:56:38 -0700 Sender: nfs-admin@lists.sourceforge.net Message-ID: <013001c2c949$b8a0d9a0$6601a8c0@userl3x55qxqed> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_012D_01C2C90F.0C174820" Return-path: Received: from rwcrmhc51.attbi.com ([204.127.198.38]) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 18eeT6-0008IG-00 for ; Fri, 31 Jan 2003 08:56:44 -0800 To: Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: This is a multi-part message in MIME format. ------=_NextPart_000_012D_01C2C90F.0C174820 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I am using this mount command on all my NFS clients mount -o ro,vers=3D3,noatime,rsize=3D8192,intr 192.168.100.xxx:/dir /dir = -t nfs Which works very well, but the server is using the XFS filesystem. = When/if the server has a problem or goes down normally the=20 mount point is just fine until the server comes back up and then keeps = going (It does this on our servers that use EXT3), but on our NFS servers that use XFS filesystem they don't? The client loses the = mount (Still shows up in a df, but shows 0 bytes for the size of the = nfs mount). I then have to unmount and then remount EVERY CLIENT = everytime there is a problem with our NFS servers?!?! =20 Is there a problem with XFS and nfs mount points or am I dumb and = missing some obvious mount option. It is weird because it works great = on all my EXT3 NFS servers. Thanks, Matt ------=_NextPart_000_012D_01C2C90F.0C174820 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I am using this mount command on all my = NFS=20 clients

mount -o = ro,vers=3D3,noatime,rsize=3D8192,intr=20 192.168.100.xxx:/dir /dir -t nfs

Which works very well, but the server = is using the=20 XFS filesystem. When/if the server has a problem or goes down = normally the=20

mount point is just fine until the = server comes=20 back up and then keeps going (It does this on our servers that use = EXT3), but on=20 our

NFS servers that use XFS filesystem = they=20 don't? The client loses the mount (Still shows up in a df, = but shows=20 0 bytes for the size of the nfs mount). I then have to unmount and = then=20 remount EVERY CLIENT everytime there is a problem with our NFS = servers?!?! =20

Is there a problem with XFS and nfs = mount points or=20 am I dumb and missing some obvious mount option. It is weird = because it=20 works great on all my EXT3 NFS servers.

Thanks,
Matt

------=_NextPart_000_012D_01C2C90F.0C174820-- ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs