This might sound trivial (and in some ways it it) but in 7-mode I was able to do an 'ls /vol/vol1' when in the cli on the filer itself. In C-mode the ls command is there via command shell but I cannot find the volumes. Which isn't that strange as the volumes now live in SVM's.
But I do have situations where it is helpfull to be able to do a listing of a volume from the CLI. I know I can NFS mount the volume and do an ls but that's just always possible/helpfull etc
So the question is "how do I list the content of a volume from the C-Mode cli or the node shell?'
Searched the interwebs but seems or a stupid question or a question no one asks 😉
thanks for you reply! But as I stated, i do know the node shell, I do have ls but no volumes.
nac1::*> node run -node fas14a Type 'exit' or 'Ctrl-D' to return to the CLI fas14a> priv set diag Warning: These diagnostic commands are for use by NetApp personnel only. fas14a*> ls /vol /vol: Can't open directory: No such file or directory fas14a*>
fas14a*> ls / etc home storagelog vserver_fs download fas14a*>
And the thread you are referring to also doesn't see any volumes.
For the record: if I log in to the SVM directly the issue is the same, no difference.
Right, you can't "browse" the list of volumes, but if you know the path to your shared data, you can do it:
cluster01::> node run -node cluster01-01 Type 'exit' or 'Ctrl-D' to return to the CLI cluster01-01> priv set advanced Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.
cluster01-01*> ls /vol/dfs_doc/DOC . .. .DS_Store Acct Agile Development AnalogGroup
In this example the volume name is 'dfs_doc' and the CIFS share under this is 'DOC'
Here's another, this one is used for Unix homedirs"
cluster01-01*> ls /vol/homedirs/home . .. jsmith mdamon bgates
So it sounds like you just need a little more depth to your ls command and it should work.
One last example with ls -l and a volume containing a single LUN:
cluster01-01*> ls -l /vol/netbot d755 64 2 4096 Mon Dec 14 23:24:09 EST 2015 . d755 64 2 4096 Mon Dec 14 23:24:09 EST 2015 .. 10600 96 1 5497629096960 Thu Apr 28 14:26:53 EDT 2016 netbot
If you commonly have the same volume name on different SVMs (for instance a "vol1" on SVM01 and SVM02). The number differentiates at the node level between two different volumes of the same name because at some point both volumes could "live" on the same node and be accessible via the "/vol/..." path. At the Cluster level, cDot translates appropriately based on the SVM the volume is in.
Hope this helps you.
Lead Storage Engineer | Consilio, LLC
NCIE SAN Clustered, Data Protection
Kudos and accepted solutions are always appreciated.