Re: hardware or software based disk ownership?

gah.

Previously I added the aggr to the vm_storage SVM on the CLI and then 
ran vserver show again and only saw the previous aggr listed. Also, if I 
tried to create a new volume on that SVM in the webUI I only was 
presented with one option, the original SVM.

Now when I look in the webUI I can see both aggrs as an option for a new 
volume. Maybe I just needed to wait for the dust to settle.

I'm calling this pair of n00b issues resolved (shared aggregates and 
disk ownership). The painful part is that this n00b has been running 
toasters for about fifteen years now. For the last five years I've been 
branching into other things and clearly my toaster skills are aging.

Thanks all,

Randy


On 7/8/2020 6:34 AM, John Stoffel wrote:
>
> Randy> I think I may just be looking at a limit of the system. If an
> Randy> aggregate is already assigned to one SVM, can it also be
> Randy> assigned to another? That is, can two different SVMs access the
> Randy> same aggregate?
>
> Yes.  All you should need to do is:
>
>    vserver modify -vserver scharp_vm_storage -aggr-list scharpdata,scharp_vm_storage
>    vserver modify -vserver scharpdata -aggr-list scharpdata,scharp_vm_storage
>    vserver modify -vserver scharp_kube -aggr-list scharpdata,scharp_vm_storage
>
> And now all three of your SVMs should be able to create volumes on
> both aggregates.  You can then test with:
>
>    vol create -vserver scharp_vm_storage -aggregate scharpdata -volume \
>      test -size 1g
>
> But if it doesn't, send the full command you used and the output for
> us to look at with you.
>
> John
>
>
> Randy> Output:
>
> Randy> netapp4::> vserver modify -vserver scharp_vm_storage -aggr-list scharpdata,scharp_vm_storage
>
> Randy> netapp4::> vserver show
> Randy>                                Admin      Operational Root
> Randy> Vserver     Type    Subtype    State      State       Volume     Aggregate
> Randy> ----------- ------- ---------- ---------- ----------- ---------- ----------
> Randy> netapp4     admin   -          -          -           -          -
> Randy> netapp4-a   node    -          -          -           -          -
> Randy> netapp4-b   node    -          -          -           -          -
> Randy> scharp_kube data    default    running    running     scharp_    scharpdata
> Randy>                                                       kube_root
> Randy> scharp_vm_storage
> Randy>             data    default    running    running     scharp_vm_ scharp_vm_
> Randy>                                                       storage_   storage
> Randy>                                                       root
> Randy> scharpdata  data    default    running    running     scharpdata scharpdata
> Randy>                                                       _root
> Randy> 6 entries were displayed.
>
> Randy> netapp4::>
>
> Randy> On 7/7/2020 2:06 PM, tmac wrote:
>
> Randy>     Something may be getting lost here. Are you able to send any output?
>     
> Randy>     --tmac
>     
> Randy>     Tim McCarthy, Principal Consultant
>     
> Randy>     Proud Member of the #NetAppATeam
>     
> Randy>     I Blog at TMACsRack
>
> Randy>     On Tue, Jul 7, 2020 at 4:47 PM Rue, Randy <[email protected]> wrote:
>     
> Randy>         I was misremembering from my early days in pre-cluster mode.
>         
> Randy>         Forget any mention of disk ownership :)
>         
> Randy>         Can an aggregate be used by more than one SVM? If so, how? When I try to
> Randy>         add the aggregate to the other SVM, the command returns without error
> Randy>         but vserver show still shows the SVMS and their assigned aggregates
> Randy>         unchanged.
>
> Randy>         On 7/7/2020 12:10 PM, John Stoffel wrote:
>>> Randy,
>>> Check your configuration, you need to assign the aggregates to the
>>> vservers.
>>>
>>>
>>>
>>>
> Randy>         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
> Randy>         _______________________________________________
> Randy>         Toasters mailing list
> Randy>         [email protected]
> Randy>         https://www.teaparty.net/mailman/listinfo/toasters
>
_______________________________________________
Toasters mailing list
[email protected]
https://www.teaparty.net/mailman/listinfo/toasters