The transition to NetApp MS Azure AD B2C is complete. If you missed the pre-registration, you will be invited to register at next log in.
Please note that access to your NetApp data may take up to 1 hour.
To learn more, read the FAQ and watch the video.
Need assistance? Complete this form and select “Registration Issue” as the Feedback Category.

ONTAP Discussions

cDot volume names do not align with node local commands

DARREN_REED

Looking at a cluster running 8.2.1P1, I notice that sometimes volume names as reported by the "qtree status" from the 7-Mode shell do not align with the volume names reported in the cDot CLI (or anywhere else for that matter.)

 

e.g. (names changed to protect the guilty)

 

cluster01:: > node run -node local qtree status testvol0(1)

Volume Tree Style Oplocks Status
-------- -------- ----- -------- ---------
testvol0(1) unix enabled normal
testvol0(1) database_undo001 unix enabled normal

cluster01:: > node run -node local vol status testvol0(1)

Volume State Status Options
testvol0(1) online raid_dp, flex create_ucode=on, convert_ucode=on,
cluster schedsnapname=create_time, guarantee=none,
sis fractional_reserve=0
64-bit
Containing aggregate: 'cluster01c01_aggr2'

cluster01:: > volume show -volume testvol0(1)
There are no entries matching your query.

cluster01:: > volume show -volume testvol0
Vserver Volume Aggregate State Type Size Available Used%
--------- ------------ ------------ ---------- ---- ---------- ---------- -----
cluster01 testvol0 cluster01_aggr2
online RW 320GB 320.0GB 0%



cluster01:: > node run -node local qtree status testvol02

Volume Tree Style Oplocks Status
-------- -------- ----- -------- ---------
testvol02 unix enabled normal
testvol02 qtreename01 unix enabled normal

cluster01:: > node run -node local vol status testvol02

Volume State Status Options
testvol02 online raid_dp, flex nvfail=on, create_ucode=on, convert_ucode=on,
cluster schedsnapname=create_time, guarantee=none,
sis fractional_reserve=0
64-bit
hybrid
Containing aggregate: 'cluster01c01_aggr1'

cluster01:: > volume show -volume testvol02
Vserver Volume Aggregate State Type Size Available Used%
--------- ------------ ------------ ---------- ---- ---------- ---------- -----
cluster01svm
testvol02 cluster01c01_aggr1
online RW 42.50GB 42.50GB 0%

 

Why does this variation exist?

Why isn't there a 1:1 correlation between volume names between all parts of cDot?

2 REPLIES 2

AdvUniMD

In cDOT is it possible to have volumes in different vServers that have the same name. This must somehow be mapped to the underlying D-Blade (nodeshell). So the first volume you create for any vServer with a certain name usually gets this name 1:1 mapped to the D-Blade, but as soon as you create another volume with the same name (but in a different vServer) the system has to rename that second volume.

 

But generally you really really shouldn't look at the volume names on the D-Blade (and NEVER EVER change anything volume- or aggregate-related on the nodeshell!) as the cluster makes certain it does everything correctly. Eventually the possibility to see volumes on the nodeshell will go away anyway since it is not really needed anymore

rwelshman

You are using () in the volume name? trying using quotes around it in the cdot command - might be interpreting the () as regex.

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public