Nope, it’s the same for FC and SAS. Older versions of Data ONTAP required full loop/stack ownership, newer Data ONTAP versions relaxed it on per-shelf basis (but I believe it is disabled by default).

From: tmac [mailto:tmacmd@gmail.com]
Sent: Thursday, June 11, 2015 2:04 PM
To: Borzenkov, Andrei
Cc: Edward Rolison; toasters@teaparty.net
Subject: Re: Disk auto assign

For auto-assign to work, all disks on a shelf must belong to only one controller.

Further, if I recall, if you are using SAS, then the whole stack must be owned by one controller.

If you split between controllers, it will not work.

--tmac

Tim McCarthy

Principal Consultant

On Thu, Jun 11, 2015 at 6:56 AM, Borzenkov, Andrei <andrei.borzenkov@ts.fujitsu.com> wrote:

If you just performed “replace” without un-/re-assigning drives that became spare, this is expected. Spares still belong to controller and will block auto assignment.

From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Edward Rolison
Sent: Thursday, June 11, 2015 1:09 PM
To: toasters@teaparty.net
Subject: Disk auto assign

I've just added some new shelves to a (7-mode) filer pair, bring them up to two stacks of 10 shelves.

I'm trying to get 'autoassign' working, and it isn't.

I have:
- swapped drives such that each 'head' has only disks from one 'stack'. 

Head 1 has 0a/5b

Head 2 has 5a/5d

I've had to manually trigger a small number of 'replace' operations. 
And then switched on autoassign in the options.

I _think_ that should be it, but ... there's something I'm missing, because autoassign isn't working. 

Does anyone have suggestions for why this might be, or what else I could check? (I'm wondering if there's a misassigned but 'failed' drive that otherwise isn't showing up?)

_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters