{"id":616,"date":"2010-04-04T23:22:56","date_gmt":"2010-04-05T03:22:56","guid":{"rendered":"https:\/\/lowtek.ca\/roo\/?p=616"},"modified":"2019-12-07T09:59:09","modified_gmt":"2019-12-07T13:59:09","slug":"how-to-resize-a-mirrored-volume","status":"publish","type":"post","link":"https:\/\/lowtek.ca\/roo\/2010\/how-to-resize-a-mirrored-volume\/","title":{"rendered":"How to: resize a mirrored volume"},"content":{"rendered":"
\"Apple<\/a>
\n\"Creative<\/a> by\u00a0 lindztrom<\/a> <\/a><\/div>\n

Having recently setup mirrored volumes with a pair of 1TB drives<\/a>, I could now migrate data off the pair of 250Gb data drives to allow me to combine those two drives into a single volume. \u00a0Way back when I purchased these drives I had intended to run a mirrored setup, but at the time decided that having more storage was more important. \u00a0I had “cleverly” purchased two 250Gb drives from different manufacturers, in theory to avoid concurrent failures. \u00a0It turns out that not all 250Gb drives are made the same.<\/p>\n

Following the instructions from my previous posting<\/a>, all went well up to where I tried to add the 2nd volume to the mirrored set. \u00a0If you run into a similar problem you’ll likely see one of the two following errors:<\/p>\n

mdadm: add new device failed for \/dev\/hda1 as 2: No space left on device
\nmdadm: add new device failed for \/dev\/hda1 as 2: Invalid argument<\/code><\/p>\n

I found some good hints on how to diagnose the problem<\/a>, it turns out you can check the partition sizes manually<\/p>\n

$ cat \/proc\/partitions<\/strong>
\nmajor minor \u00a0#blocks \u00a0name<\/code><\/p>\n

<\/code><\/p>\n

8 \u00a0 \u00a017 \u00a0244196001 sdb1
\n8 \u00a0 \u00a065 \u00a0244198552 sde1<\/code><\/p>\n

Close, but not quite the same. \u00a0As it was, I had unluckily chosen \/dev\/sdb as the 1st drive in the mirrored set. \u00a0It turns out that fdisk tells an even more interesting story.<\/p>\n

$ sudo fdisk -l \/dev\/sdb<\/strong><\/code><\/p>\n

Disk \/dev\/sdb: 250.0 GB, 250059350016 bytes
\n255 heads, 63 sectors\/track, 30401 cylinders
\nUnits = cylinders of 16065 * 512 = 8225280 bytes
\nDisk identifier: 0x000c0f4f<\/code><\/p>\n

Device Boot Start End Blocks Id System
\n\/dev\/sdb1 1 30401 244196001 83 Linux<\/code><\/p>\n

<\/code><\/p>\n

$ sudo fdisk -l \/dev\/sde<\/strong><\/code><\/p>\n

Disk \/dev\/sde: 250.0 GB, 250059350016 bytes
\n16 heads, 63 sectors\/track, 484521 cylinders
\nUnits = cylinders of 1008 * 512 = 516096 bytes
\nDisk identifier: 0x00000000<\/code><\/p>\n

<\/code><\/p>\n

Device Boot Start End Blocks Id System
\n\/dev\/sde1 1 484521 244198552+ 83 Linux<\/code><\/p>\n

Yuck, looks messy. At this point I’ve got some of my live data sitting on one half of the mirrored set, and no suitable 2nd drive to act as the mirror. \u00a0Somewhat predictably there is a solution<\/a> that minimizes downtime and avoids copying all of the data to a new location.<\/p>\n

First you unmount the volume and run resize2fs on it. \u00a0We don’t need to know the correct size, just any size smaller than the 2nd volume – so I used 200Gb.<\/p>\n

$ sudo umount \/media\/data\/<\/strong>
\n $ sudo e2fsck -f \/dev\/md2<\/strong>
\ne2fsck 1.40.8 (13-Mar-2008)
\nPass 1: Checking inodes, blocks, and sizes
\nPass 2: Checking directory structure
\nPass 3: Checking directory connectivity
\nPass 4: Checking reference counts
\nPass 5: Checking group summary information
\n\/dev\/md2: 1890279\/15269888 files (0.2% non-contiguous), 32742192\/61049616 blocks
\n $ sudo resize2fs \/dev\/md2 200G<\/strong>
\nresize2fs 1.40.8 (13-Mar-2008)
\nResizing the filesystem on \/dev\/md2 to 52428800 (4k) blocks.
\nThe filesystem on \/dev\/md2 is now 52428800 blocks long.<\/code><\/p>\n

Now we need to calculate what the correct size of the mirrored partition should be. I looked at two bits of data: the size the mdadm -D reported for the partition I wanted to resize, and the size that was in \/proc\/partitions for the same. These differed by 88 blocks, so I used the value 88 as a fudge factor<\/a> – it may not be required but it worked for me. I then also ensured that I supplied a value that was an even multiple of 64 (blocks).<\/p>\n

So starting with\u00a0244196001 from \/proc\/partitions:<\/p>\n

(244196001 - 88) \/ 64 = 3815561.14
\n<\/code>
\nDrop the decimal places and multiply by 64 to get the number of blocks.<\/p>\n

3815561 * 64 =\u00a0244195904<\/code><\/p>\n

Now we feed this new size into mdadm and specify the –grow flag (which can also be used to shrink if you specify a block size smaller than the current which is what we are doing in this case). \u00a0We then re-run resize2fs without a specified size, which will cause it to expand the filesystem to fill the partition.<\/p>\n

$ sudo mdadm --grow \/dev\/md2 --size=244195904<\/strong>
\n $ sudo resize2fs \/dev\/md2<\/strong>
\nresize2fs 1.40.8 (13-Mar-2008)
\nResizing the filesystem on \/dev\/md2 to 61048976 (4k) blocks.
\nThe filesystem on \/dev\/md2 is now 61048976 blocks long.<\/code><\/p>\n

Now all that is left is to run a filesystem check, and remount it.<\/p>\n

$sudo e2fsck -f \/dev\/md2<\/strong>
\ne2fsck 1.40.8 (13-Mar-2008)
\nPass 1: Checking inodes, blocks, and sizes
\nPass 2: Checking directory structure
\nPass 3: Checking directory connectivity
\nPass 4: Checking reference counts
\nPass 5: Checking group summary information
\n\/dev\/md2: 1890279\/15269888 files (0.2% non-contiguous), 32742192\/61048976 blocks
\n $ sudo mount -a<\/strong><\/code><\/p>\n

Now when you attempt to add the 2nd volume, it will be a matching size and the mirror will work. \u00a0In the future, I intend to be a little more careful when I plan to setup mirrored drives and pick the smaller volume as the starting point.<\/p>\n","protected":false},"excerpt":{"rendered":"

by\u00a0 lindztrom Having recently setup mirrored volumes with a pair of 1TB drives, I could now migrate data off the pair of 250Gb data drives to allow me to combine those two drives into a single volume. \u00a0Way back when I purchased these drives I had intended to run a mirrored setup, but at the … Continue reading “How to: resize a mirrored volume”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,12],"tags":[],"class_list":["post-616","post","type-post","status-publish","format-standard","hentry","category-computing","category-how-to"],"_links":{"self":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/616","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/comments?post=616"}],"version-history":[{"count":4,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/616\/revisions"}],"predecessor-version":[{"id":1656,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/posts\/616\/revisions\/1656"}],"wp:attachment":[{"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/media?parent=616"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/categories?post=616"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lowtek.ca\/roo\/wp-json\/wp\/v2\/tags?post=616"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}