About rwelshman

rwelshman · ‎2015-06-23

Have you looked in the snapmirror log on both the source and destination filers? they tend to report different things. Also, the messages file could have some extra info that may point to the cause of the issue.

rwelshman · ‎2015-06-12

You can stop dedupe activity from happening. But that won't un-dedupe. You would have to go into advanced or diag mode to do so. But perhaps stopping it from happening might be sufficient. You would keep any dedupe savings you currently have.

rwelshman · ‎2015-06-10

You can mount a directory that has been created within the volume - as long as you are in the export policy for the volume itself.

rwelshman · ‎2015-06-09

How do you know it is a qtree and not just a directory?

rwelshman · ‎2015-06-05

try exportfs -p rw=<server ip>,root=<server ip> /vol/DEST_NFS

rwelshman · ‎2015-06-05

If you power down the shelves, any data volumes located on those shelves would not be available. So you would need an outage for those volumes, unless you can clear off the aggregates prior to the move. Are you running 7-mode or C-mode?

rwelshman · ‎2015-06-03

In most cases, it is better to create a specific failover group to ensure the interfaces that will be used as failover are appropriate (speed / vlans).

rwelshman · ‎2015-05-28

The HA stands for Host Adapter. The "88" is just wrap around from the line above, it is part of the disk size.

rwelshman · ‎2015-05-27

Could you be more specific? What are you trying to figure out? Those are two 600 GB 15K SAS disks - both parity, on shelf 1 attached to adapter 2a, bay 12 and 11.

rwelshman · ‎2015-05-27

Do you have OnCommand installed? I wonder if it is part of a dataset somewhere that should be removed as well.

rwelshman · ‎2015-05-26

Do you have access to http://mysupport.netapp.com? The software can be downloaded from there.

rwelshman · ‎2015-05-22

I am getting the following message in the messages file on one filer every hour: "Network lock manager version 4 (for UDP) not registered with portmapper daemon on the client <client ip>" There doesn't seem to be any issue with the client using the volumes it has mounted, so this doesn't seem to be a serious issue, however, I would like to stop it spamming the messages file. I've tried restarting the lock manager service on the client as well as port mapper (rpcbind) and even gave it a reboot. But the error message is still being generated. NFSv4 is enabled on the filer, but the client is mounting using NFSv3. It looks like the process has registered ok from the cilent side: rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 25086 status 100024 1 tcp 35999 status 100021 1 udp 51494 nlockmgr 100021 3 udp 51494 nlockmgr 100021 4 udp 51494 nlockmgr 100021 1 tcp 52961 nlockmgr 100021 3 tcp 52961 nlockmgr 100021 4 tcp 52961 nlockmgr Anyone seen this before? Any suggestions? Thanks! I am getting the following messages in the messages file on one filer every hour: Network lock manager version 4 (for UDP) not registered with portmapper daemon on the client <client ip> There doesn't seem to be any issues with the client using the volume it has mounted, so this doesn't seem to be a serious issue, however, I would like to stop it spamming the messgaes file. I've tried restarting the lock manager service on the client as well as port mapper (rpcbind) and even gave it a reboot. But the error message is still being generated. NFSv4 is enabled on the filer, but the client is mounting using NFSv3.

rwelshman · ‎2015-05-22

You can look in the snapmirror log file on both the source and the destination filers, that may give you some more details as to the cause.

rwelshman · ‎2015-05-19

If there is a snapshot on the volume with the lun, it is likely the cause of the usage you are seeing.

rwelshman · ‎2015-05-14

You have to purchase a NetApp disk - either from NetApp directly or through a third-party. No other type of disk will work in the filer. If you don't have support, you will have to pay the full price.

rwelshman · ‎2015-05-12

Ok, well it definitely doesn't recognize the disk. Either try to reseat the disk - take it out, wait 30 seconds or so, and replace it. But if the disk isn't a refrusbished or new NetApp disk it won't accept it and could cause issues. It has to have a NetApp part number on the label somewhere to be compatible.

rwelshman · ‎2015-05-12

The cluster interconnects don't really failover, you have two connections and they are independent but provide redundancy. The default config for cluster interconnect is to use the system-defined failover group.

rwelshman · ‎2015-05-12

What type of disks will they be? SAS / SATA, etc. If you have two raid gropus, there will be four parity disks. If you want a true 21 + 2, then you should set the raid group size to be 23 disks total, and have one raid group. But that would be a large raid group for large sized disks - since the rebuild time will be so long.

rwelshman · ‎2015-05-12

Can you give the output of a sysconfig -a -> just the disk information on adapter 3d would be good. This will list the type of disk.

rwelshman · ‎2015-05-12

Do these interfaces have the cluster role?

rwelshman · ‎2015-05-12

can you check for open files on that share on the filer - maybe someone has that folder open so it won't delete? i'm just making guesses here myself - not sure what could be the cause really.

rwelshman · ‎2015-05-12

can you provide the sysconfig information for that disk? as noted, if the disk doesn't have a netapp label, it won't be recognized or used in the filer.

rwelshman · ‎2015-05-12

have you tried setting the sftp.dir_override option to /vol/vol0/etc?

rwelshman · ‎2015-05-12

do you have multiple interfaces on the same network?

rwelshman · ‎2015-05-11

There are no shares created within that tesvol other than at the root level? can you look at the permissions on the vol folder?

Re: QSM Error - cannot connect to source filer - but only for one relationship!

Re: Disable Storage Efficiency?

Re: Could not find the qtree on cDOT cluster but mounted on a host

Re: Could not find the qtree on cDOT cluster but mounted on a host

Re: NFS Export Permission for Unix

Re: Moving Shelves from one rack to another: can I just faill over the controller?

Re: Network Default Failover Policy

Re: sysconfig -r

Re: sysconfig -r

Re: Unable to delete volume

Re: NetApp Software Download Information

Network Lock Manager not registered with portmapper error in messages log

Re: Snapvault (transfer aborted because of network error) after changing to vif

Re: Empty thin provisioned lun still using space on volume

Re: Replace faulty/broken disk in NetApp

Re: Replace faulty/broken disk in NetApp

Re: Add Failover targets

Re: Create Aggregate with 23 disks and one hot spare?

Re: Replace faulty/broken disk in NetApp

Re: Add Failover targets

Re: Can't delete subfolder "Vol" from CIFS Share?

Re: Replace faulty/broken disk in NetApp

Re: Issue with sftp accessed by a local user in /etc/passwd

Re: Configuring Persistent static route - Interface option - 7-mode

Re: Can't delete subfolder "Vol" from CIFS Share?