codesuf.blogg.se

The backup-file should be saved on a filesystem not part of the array you are going to grow.

mdadm -grow /dev/md0 -level=raid6 -raid-devices=6 -backup-file=/root/mdadm5-6_backup_md0 Make use of the -backup-file option, so in case of power loss you can continue to grow the device after a reboot and ensure no data loss. In my experience with doing raid level migrations on hardware RAID controllers, it's been quicker to create the new array from scratch and recover your backup to it. I have no idea how quick this will be though. $ sudo mdadm -grow /dev/md/md0 -raid-devices 4 -level 6 The -raid-devices 4 tells you how many drives you have in total in the new array. Then convert into a RAID6 array and make it rebuild to a clean state. RAID5, as well as adding or removing a write-intent bitmap.ĮG, add a new hotspare device, /dev/sdg, to the RAID5 array first: $ sudo mdadm -manage /dev/md/md0 -add /dev/sdg Currently supported growth options including changing the active size of component devices andĬhanging the number of active devices in RAID levels 1/4/5/6, changing the RAID level between 1, 5, and 6, changing the chunk size and layout for RAID5 and You'll need a recent mdadm to do this: mdadm-2.6.9 (eg, centos 5.x) doesn't seem to support it, but mdadm-3.1.4 (eg ubuntu 11.10) does: Grow Grow (or shrink) an array, or otherwise reshape it in some way. I haven't done it, but the procedure looks like you should add the new drive as a hotspare to the existing array, then use mdadm to update the raid level and the number of raid devices. The terminology you are looking for is a "RAID level migration".Īccording to this, it's possible.