Adding to my earlier reply... see end of message -----Original Message----- From: fedora-list-bounces@xxxxxxxxxx on behalf of Ian Chapman Sent: Mon 10/30/2006 12:56 PM To: For users of Fedora Core releases Cc: Subject: Re: FC6 client fails to NFS mount from Solaris 8 server Miner, Jonathan W (CSC) (US SSA) wrote: > Hi - > > Long time Linux user, just upgraded from FC5 to FC6 and now can longer mount drives from my Solaris 8 (Sun Cluster 2.1) server. I can sucessfully mount filesystems from RedHat Enterprise Linux 4ES (Update 4) servers. > > 1) SELinux and IPtables are both disabled. > 2) I can "ping" and "telnet" to the Solaris server, and "showmount -e" lists all the exported filesystems > 3) tcpdump shows network traffic between the client and server > 4) mount -t nfs server:/path /mnt commands time out with "Server not responding" messages > > Any ideas? Just for the record, FC6 works fine when mounting an export from a Solaris 10 (sparc) box here. Just a stab in the dark, but maybe it's related to NFS version conflicts? Have you done a sanity check to make sure other machines can mount the solaris export? You could try editing /etc/default/nfs on the solaris box, setting the min and max NFS versions to 3 and on your linux box mounting with the option -o vers=3 That's assuming you don't explicitly need NFS V2 or V4. -------------------------------- Yes, the Solaris cluster is working properly. It's the backbone of my infrastructure so I'd have much bigger problems if it failed! :) The workstation could mount from the cluster when running FC5, but after installing FC6 fails (with and without vers=3 option); however, I ran another test this morning, and FC6 will mount from a non-clustered Solaris 8 machine. Here is the output from the showmount and mount commands. # uname -a Linux ac523421 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686 i686 i386 GNU/Linux # showmount -e superfly Export list for superfly: /superfly/vol01 (everyone) /superfly/vol02 (everyone) /superfly/vol03 (everyone) /superfly/vol04 (everyone) /superfly/vol05 (everyone) /superfly/vol06 (everyone) /superfly/vol07 (everyone) /superfly/vol08 (everyone) # mount superfly:/superfly/vol01 /mnt mount: mount to NFS server 'superfly' failed: timed out (retrying). mount: mount to NFS server 'superfly' failed: timed out (retrying). mount: mount to NFS server 'superfly' failed: timed out (retrying). mount: mount to NFS server 'superfly' failed: timed out (retrying). mount: mount to NFS server 'superfly' failed: timed out (giving up). # mount -o vers=3 superfly:/superfly/vol01 /mnt mount: mount to NFS server 'superfly' failed: timed out (retrying). mount: mount to NFS server 'superfly' failed: timed out (retrying). mount: mount to NFS server 'superfly' failed: timed out (retrying). mount: mount to NFS server 'superfly' failed: timed out (retrying). mount: mount to NFS server 'superfly' failed: timed out (giving up). I can generate a packet capture if that would be of interest. Thanks After further testing, I've discovered that I can mount the filesystem from one of the cluster members. (The cluster is made of two nodes; fly_a and fly_b; the NFS service is known as "superfly" and its own IP address. Only one node is active at a time... currently fly_a is the active node) # showmount -e fly_a Export list for fly_a: /superfly/vol01 (everyone) /superfly/vol02 (everyone) /superfly/vol03 (everyone) /superfly/vol04 (everyone) /superfly/vol05 (everyone) /superfly/vol06 (everyone) /superfly/vol07 (everyone) /superfly/vol08 (everyone) # mount fly_a:/superfly/vol01 /mnt Works!
<<winmail.dat>>
