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?)
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?)
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
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.commailto: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.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net] On Behalf Of Edward Rolison Sent: Thursday, June 11, 2015 1:09 PM To: toasters@teaparty.netmailto: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.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Thanks. I don't pay too much attention to auto-assign anymore. I usually split disks anyway (even disks to node 2, odd disks to node 1)
--tmac
*Tim McCarthy* *Principal Consultant*
On Thu, Jun 11, 2015 at 7:06 AM, Borzenkov, Andrei < andrei.borzenkov@ts.fujitsu.com> wrote:
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
Well, I must confess - that's my plan B. It's not to hard to run a cron job to do `disk show -n` occasionally :)
On 11 June 2015 at 12:07, tmac tmacmd@gmail.com wrote:
Thanks. I don't pay too much attention to auto-assign anymore. I usually split disks anyway (even disks to node 2, odd disks to node 1)
--tmac
*Tim McCarthy* *Principal Consultant*
On Thu, Jun 11, 2015 at 7:06 AM, Borzenkov, Andrei < andrei.borzenkov@ts.fujitsu.com> wrote:
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
Sorry, should have said - also did this with the spares. I can see no drives on 'head1' sysconfig -r that are 'wrong' and likewise on 'head2'.
Checked this with grepping 'partner' and ensuring they're all the right pair of controllers. (On both sides)
On 11 June 2015 at 11:56, 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?)
Are you sure new disks are unowned? It is not uncommon to get repurposed hardware.
From: Edward Rolison [mailto:ed.rolison@gmail.com] Sent: Thursday, June 11, 2015 2:09 PM To: Borzenkov, Andrei Cc: toasters@teaparty.net Subject: Re: Disk auto assign
Sorry, should have said - also did this with the spares. I can see no drives on 'head1' sysconfig -r that are 'wrong' and likewise on 'head2'.
Checked this with grepping 'partner' and ensuring they're all the right pair of controllers. (On both sides)
On 11 June 2015 at 11:56, Borzenkov, Andrei <andrei.borzenkov@ts.fujitsu.commailto: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.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net] On Behalf Of Edward Rolison Sent: Thursday, June 11, 2015 1:09 PM To: toasters@teaparty.netmailto: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?)
New disks are all listed in 'disk show -n'. I think that means they're not assigned. (And a disk I've deliberately unassigned is also not being reassigned).
On 11 June 2015 at 12:12, Borzenkov, Andrei <andrei.borzenkov@ts.fujitsu.com
wrote:
Are you sure new disks are unowned? It is not uncommon to get repurposed hardware.
*From:* Edward Rolison [mailto:ed.rolison@gmail.com] *Sent:* Thursday, June 11, 2015 2:09 PM *To:* Borzenkov, Andrei *Cc:* toasters@teaparty.net *Subject:* Re: Disk auto assign
Sorry, should have said - also did this with the spares. I can see no drives on 'head1' sysconfig -r that are 'wrong' and likewise on 'head2'.
Checked this with grepping 'partner' and ensuring they're all the right pair of controllers. (On both sides)
On 11 June 2015 at 11:56, 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?)
Well, https://kb.netapp.com/support/index?page=content&id=3012152&locale=e... suggests as one more reason mismatched pools; if everything listed in this article is OK, I give up - call NetApp support ☺
From: Edward Rolison [mailto:ed.rolison@gmail.com] Sent: Thursday, June 11, 2015 2:26 PM To: Borzenkov, Andrei Cc: toasters@teaparty.net Subject: Re: Disk auto assign
New disks are all listed in 'disk show -n'. I think that means they're not assigned. (And a disk I've deliberately unassigned is also not being reassigned).
On 11 June 2015 at 12:12, Borzenkov, Andrei <andrei.borzenkov@ts.fujitsu.commailto:andrei.borzenkov@ts.fujitsu.com> wrote: Are you sure new disks are unowned? It is not uncommon to get repurposed hardware.
From: Edward Rolison [mailto:ed.rolison@gmail.commailto:ed.rolison@gmail.com] Sent: Thursday, June 11, 2015 2:09 PM To: Borzenkov, Andrei Cc: toasters@teaparty.netmailto:toasters@teaparty.net Subject: Re: Disk auto assign
Sorry, should have said - also did this with the spares. I can see no drives on 'head1' sysconfig -r that are 'wrong' and likewise on 'head2'.
Checked this with grepping 'partner' and ensuring they're all the right pair of controllers. (On both sides)
On 11 June 2015 at 11:56, Borzenkov, Andrei <andrei.borzenkov@ts.fujitsu.commailto: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.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net] On Behalf Of Edward Rolison Sent: Thursday, June 11, 2015 1:09 PM To: toasters@teaparty.netmailto: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?)
-
Borzenkov, Andrei -
Edward Rolison -
tmac