Re: hardware or software based disk ownership?

"Rue, Randy" <[email protected]>
Newsgroups gmane.comp.hardware.netapp
Message-ID <[email protected]>
I always cringe when I see a timid newcomer get spanked and I appreciate 
the tact and diplomacy of your gentle RTFM :)

In this case I'd read the docs on managing aggrs and was confused by the 
system not behaving like I'd expect. Admittedly whatever was going wrong 
was likely carbon-based.

All is well...


On 7/7/2020 3:28 PM, Heino Walther wrote:
>
> Yes aggregates can of cause be shared between multiple SVMs…. (erhm… I 
> think a little polite rtfm is in order here?) 😉
>
> And before you ask, you cannot use the two aggr0 root aggregates for 
> any data volumes…
>
> /Heino
>
> *Fra: *Toasters <[email protected]> på vegne af "Rue, 
> Randy" <[email protected]>
> *Dato: *onsdag den 8. juli 2020 kl. 00.23
> *Til: *tmac <[email protected]>
> *Cc: *Toasters <[email protected]>
> *Emne: *Re: hardware or software based disk ownership?
>
> I think I may just be looking at a limit of the system. If an 
> aggregate is already assigned to one SVM, can it also be assigned to 
> another? That is, can two different SVMs access the same aggregate?
>
> Output:
>
> netapp4::> vserver modify -vserver scharp_vm_storage -aggr-list 
> scharpdata,scharp_vm_storage
>
> netapp4::> vserver show
>                                Admin      Operational Root
> Vserver     Type    Subtype    State      State Volume     Aggregate
> ----------- ------- ---------- ---------- ----------- ---------- 
> ----------
> netapp4     admin   -          -          - -          -
> netapp4-a   node    -          -          - -          -
> netapp4-b   node    -          -          - -          -
> scharp_kube data    default    running    running scharp_    scharpdata
> kube_root
> scharp_vm_storage
>             data    default    running    running scharp_vm_ scharp_vm_
> storage_   storage
>                                                       root
> scharpdata  data    default    running    running scharpdata scharpdata
>                                                       _root
> 6 entries were displayed.
>
> netapp4::>
>
> On 7/7/2020 2:06 PM, tmac wrote:
>
>     Something may be getting lost here. Are you able to send any output?
>
>
>     --tmac
>
>     *Tim McCarthy, */Principal Consultant/
>
>     *Proud Member of the #NetAppATeam <https://twitter.com/NetAppATeam>*
>
>     *I Blog at **TMACsRack <https://tmacsrack.wordpress.com/>*
>
>     On Tue, Jul 7, 2020 at 4:47 PM Rue, Randy <[email protected]
>     <mailto:[email protected]>> wrote:
>
>         I was misremembering from my early days in pre-cluster mode.
>
>         Forget any mention of disk ownership :)
>
>         Can an aggregate be used by more than one SVM? If so, how?
>         When I try to
>         add the aggregate to the other SVM, the command returns
>         without error
>         but vserver show still shows the SVMS and their assigned
>         aggregates
>         unchanged.
>
>
>         On 7/7/2020 12:10 PM, John Stoffel wrote:
>         > Randy,
>         > Check your configuration, you need to assign the aggregates
>         to the
>         > vservers.
>         >
>         >
>         >
>         >
>         https://library.netapp.com/ecmdocs/ECMP1196912/html/GUID-5255E7D8-F420-4BD3-AEFB-7EF65488C65C.html
>         >
>         > shows you the steps to take.
>         >
>         >        vserver show -fields aggr-list
>         >
>         >        vserver modify -vserver <vserver> -aggr-list
>         <aggr1>,<aggr2>[,aggrN]
>         >
>         > John
>         _______________________________________________
>         Toasters mailing list
>         [email protected] <mailto:[email protected]>
>         https://www.teaparty.net/mailman/listinfo/toasters
>

_______________________________________________
Toasters mailing list
[email protected]
https://www.teaparty.net/mailman/listinfo/toasters
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.