It looks like, from what I can see in the API tools(using ZEDI from the SDK), that the *file-create-directory* ZAPI call is only exposed in the 7-mode and vserver (which appears to only apply to vfilers under 7-mode and not cDOT) APIs and not the cluster mode one, yet per my playing yesterday, the ability *is* exposed in the PowerShell toolkit.
--tmac
*Tim McCarthy, **Principal Consultant*
On Thu, Mar 17, 2016 at 12:36 PM, Parisi, Justin Justin.Parisi@netapp.com wrote:
You can create folders in cDOT with ZAPI calls. ;)
http://community.netapp.com/t5/Data-ONTAP-Discussions/Create-parent-director...
From: tmac tmacmd@gmail.com Date: Thursday, March 17, 2016 at 11:26 AM To: Justin Parisi Justin.Parisi@netapp.com, Sebastian Goetze < spgoetze@gmail.com>
Cc: "Toasters@teaparty.net" Toasters@teaparty.net Subject: Re: 7Mode junction-path style on cDOT
I think the idea is you can easily make the qtree from ONTAP without having to mount the volume first, like in my first post. Not sure, but I think it requires something squirrelly to make a directory from ONTAP without it being a qtree
Sent from Mobile Outlook https://aka.ms/qtex0l
On Thu, Mar 17, 2016 at 9:22 AM -0700, "Parisi, Justin" < Justin.Parisi@netapp.com> wrote:
Doesn’t even need to be a qtree. Can be an empty directory.
From: toasters-bounces@teaparty.net on behalf of tmac <tmacmd@gmail.com
Date: Thursday, March 17, 2016 at 9:22 AM To: Sebastian Goetze spgoetze@gmail.com Cc: "Toasters@teaparty.net" Toasters@teaparty.net Subject: Re: 7Mode junction-path style on cDOT
Very good point....when I was doing this on the older versions of GX and cDOT, qtrees were non-existent.
--tmac
*Tim McCarthy, **Principal Consultant*
On Thu, Mar 17, 2016 at 9:57 AM, Sebastian Goetze spgoetze@gmail.com wrote:
How about, instead of creating an empty volume, you *create a QTree named "vol"...* (in the SVM root volume) Then you can also easily mount with a junction path starting in "/vol/..."
Sebastian
On 3/17/2016 12:59 PM, tmac wrote:
you *could* make that happen easily.
There is the base root volume in cDOT (/) where all junctions usually form. You would have to set the export-policy on the root volume to something that is writeable by a client. Mount the root of the cdot filer and create the EMPTY volume call vol. That is your place holder.
Then, when "mounting" a junction in cdot, do something like:
vol mount -volume share_01 -junction-path /vol/share_01
and it should work. I did this in a past job with hundreds of volumes so I can tell you it works. You just need to make sure your export-policies are set the way you want/need and be sure to limit the root volume export-policy when you are done.
--tmac
*Tim McCarthy, **Principal Consultant*
RHCE6 110-107-141https://www.redhat.com/wapps/training/certification/verify.html?certNumber=110-107-141&isSearch=False&verify=Verify Current until Aug 02, 2016
On Thu, Mar 17, 2016 at 7:05 AM, Momonth momonth@gmail.com wrote:
Hi,
I wonder if it's possible to employ 7Mode mount point behavior on cDOT NFS SVM?
An example:
- I create a volume "share_01" and by default it shows up as
"toaster:/share_01".
- I'd like to access it as "toaset:/vol/share_01"
So, my question is how to add "/vol/" to its junction_path?
Cheers, Vladimir _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing listToasters@teaparty.nethttp://www.teaparty.net/mailman/listinfo/toasters