Changing Disk Ownership
All current NetApp storage controller systems can assume ownership of any disks it can see regardless of physical cabling through the use of software based ownership. This gives you flexibility in provisioning disks in a clustered environment. Changing ownership used to require fighting with the disk reassign command or downtime to go into maintenance mode. A little known option to the disk assign command will allow you to change ownership without taking downtime.
Examples
controller1> disk assign –s unowned 0a.23 - remove ownership on system that owns the disk (controller1).
controller2> disk show –n - the disk shows up as unowned with the physical address it has on controller2
controller2> disk assign 0b.23 - take ownership of the unowned disk on the partner system
What It Means To You
Before software disk ownership, you had to take downtime to physically move disks from one cluster partner to another to expand a fast growing aggregate or to provide another spare drive. With the –s unowned option you can reassign ownership of a spare disk without taking downtime. This also makes reassignment of disks on a new FAS2050, 3140 and 3170 cluster easier (on power up, these systems which share a single chassis have a tendancy to randomly take possession of internal SAS/SATA disks in a higgledy-piggledy manner ).
All current NetApp storage controller systems can assume ownership of any disks it can see regardless of physical cabling through the use of software based ownership. This gives you flexibility in provisioning disks in a clustered environment. Changing ownership used to require fighting with the disk reassign command or downtime to go into maintenance mode. A little known option to the disk assign command will allow you to change ownership without taking downtime.
Examples
controller1> disk assign –s unowned 0a.23 - remove ownership on system that owns the disk (controller1).
controller2> disk show –n - the disk shows up as unowned with the physical address it has on controller2
controller2> disk assign 0b.23 - take ownership of the unowned disk on the partner system
What It Means To You
Before software disk ownership, you had to take downtime to physically move disks from one cluster partner to another to expand a fast growing aggregate or to provide another spare drive. With the –s unowned option you can reassign ownership of a spare disk without taking downtime. This also makes reassignment of disks on a new FAS2050, 3140 and 3170 cluster easier (on power up, these systems which share a single chassis have a tendancy to randomly take possession of internal SAS/SATA disks in a higgledy-piggledy manner ).
No comments:
Post a Comment