On Mon, Dec 22, 2014 at 4:42 PM, Iluhes <iluhes@yahoo.com> wrote:
vol show -field policy -vserver ocna06c-nfs 
  (volume show)
vserver     volume            policy     
----------- ----------------- ---------- 
test-nfs       test1              testvm 
.....


  (network interface show)
            Logical    Status     Network            Current       Current Is
Vserver     Interface  Admin/Oper Address/Mask       Node          Port    Home
----------- ---------- ---------- ------------------ ------------- ------- ----
test-nfs
            test-nfs_nfs_lif1 
                         up/up    10.9.9.9/24     testA       a0a-670 true


                     Vserver Name: test-nfs
           Logical Interface Name: test-nfs_nfs_lif1
                             Role: data
                    Data Protocol: nfs
                        Home Node: testA
                        Home Port: a0a-670
                     Current Node: testA
                     Current Port: a0a-670
               Operational Status: up
                  Extended Status: -
                       Numeric ID: 1039
                          Is Home: true
                  Network Address: 10.9.9.9
                          Netmask: 255.255.255.0
              Bits in the Netmask: 24
                  IPv4 Link Local: -
               Routing Group Name: d10.9.9.0/24
            Administrative Status: up
                  Failover Policy: nextavail
                  Firewall Policy: mgmt
                      Auto Revert: false
                      Sticky Flag: false
    Fully Qualified DNS Zone Name: none
          DNS Query Listen Enable: false
   Load Balancing Migrate Allowed: false
             Load Balanced Weight: load
              Failover Group Name: system-defined
                         FCP WWPN: -
                   Address family: ipv4
                          Comment: -

eth0      Link encap:Ethernet  HWaddr 00:50:56:B4:7D:A9  
          inet addr:10.9.9.3  Bcast:10.9.9.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1871372 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2047231 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:605262141 (577.2 MiB)  TX bytes:286957218 (273.6 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:47212 errors:0 dropped:0 overruns:0 frame:0
          TX packets:47212 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:10208922 (9.7 MiB)  TX bytes:10208922 (9.7 MiB)

[root@/]# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
10.9.9.0       0.0.0.0         255.255.255.0   U         0 0          0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U         0 0          0 eth0
0.0.0.0         10.9.9.1       0.0.0.0         UG        0 0          0 eth0

The NFS vserver only has visiabilty to DATA interface...how can route would go somewhere else?



On Monday, December 22, 2014 3:10 PM, tmac <tmacmd@gmail.com> wrote:


So, got this data so far:

appears to be using a0a (single mode e0b/e0d, e0b active, e0d not so much with IP distribution)
10.9.9.9:/test1 on /mnt1 type nfs (rw,bg,hard,intr,rsize=32768,wsize=32768,vers=3,tcp,timeo=600,addr=10.9.9.9)
 --> tried both intr and nointr
Confirmed v3 is ENABLED and all v4+ are disabled on the NFS vserver
TCP & UDP are both enabled on vserver

No Jumbo frames

No blatant errors showing via netstat -i on the client or netapp side

Flow control appears off from cdot point of view.

have the export-policy rule data

Waiting for this data:

vol show -field policy

Wondering if it might be related.

--> Iluhes

Please send:
vol show -field policy
net int show -vserver test-nfs -instance
(would like to see all the network interface details)

Also send the client-side "ifconfig -a" for all interfaces, including netstat -rn

maybe there is a bad route someplace.

--tmac

Tim McCarthy
Principal Consultant


On Mon, Dec 22, 2014 at 3:50 PM, Parisi, Justin <Justin.Parisi@netapp.com> wrote:
Are you specifying NFSv3 in the mount? Or using NFSv4?
 
I’d suggest getting the info tmac mentioned. Like others have said, impossible to solve with such limited info.
 
From: Iluhes [mailto:iluhes@yahoo.com]
Sent: Monday, December 22, 2014 3:49 PM
To: Parisi, Justin; Alexander Griesser
Cc: Toasters
Subject: Re: new cdot NFS vserver. NFS mount point hang on I/O
 
New clients. RHEL 6.6
 
On Monday, December 22, 2014 2:43 PM, "Parisi, Justin" <Justin.Parisi@netapp.com> wrote:
 
How old are your clients?
 
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Iluhes
Sent: Monday, December 22, 2014 3:42 PM
To: Alexander Griesser
Cc: Toasters
Subject: Re: new cdot NFS vserver. NFS mount point hang on I/O
 
Thanks.
I can get unmounted and remounted, but I cannot overcome the issue of copy any files into filesystem, or writing anything to it. Nothing besides mkdir and touch works..
Something is wrong with the setup...
 
On Monday, December 22, 2014 2:37 PM, Alexander Griesser <ag@anexia.at> wrote:
 
umount -l /mountpoint
 
should at least get you going on the box again.
When the filesystem had bren mounted on linux, can you post the output of the 'mount' command so we can see the mount options in use?
 
best,
Alexander Griesser
Head of Systems Operations
 
ANEXIA Internetdienstleistungs GmbH
 
E-Mail: ag@anexia.at
 
Anschrift Hauptsitz Klagenfurt:Feldkirchnerstraße 140, 9020 Klagenfurt
Geschäftsführer: Alexander Windbichler
Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601

Am 22.12.2014 um 21:16 schrieb Iluhes <iluhes@yahoo.com>:
Yes Jordan, have to do fuser -km actually...but even that works 50% of the time. It will hang the box 
 
On Monday, December 22, 2014 1:51 PM, Jordan Slingerland <Jordan.Slingerland@independenthealth.com> wrote:
 
Does not solve the root of your problem, but can you umount –f ?
 
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Iluhes
Sent: Monday, December 22, 2014 2:42 PM
To: Toasters
Subject: new cdot NFS vserver. NFS mount point hang on I/O
 
Hi Folks,
New cdot isntall, new NFS vserver. NFS shares can be mounted OK on linnux and solaris clients.
I can mkdir and touch files. Copy or move or DD or any I/O operation completly hangs the mount point, the process cannot be Control-C, and kill -9 does not even help
 
 
_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters
 
 

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters