1 |
On Thu, Nov 17, 2011 at 11:47 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
> On Thu, 17 Nov 2011 10:59:06 -0800, Mark Knecht wrote: |
3 |
> |
4 |
>> Yes, resize would be done to /dev/md?. I agree. However I don't |
5 |
>> believe that I'd use Neil's suggestion of fdisk block numbers on |
6 |
>> /dev/md, right? That doesn't make sense to me and I don't beleieve |
7 |
>> Neil was suggesting anything like that. |
8 |
> |
9 |
> Yes I was. /dev/md? is still a block device, and its blocks correspond to |
10 |
> physical blocks on the component drives. |
11 |
> |
12 |
> |
13 |
> -- |
14 |
> Neil Bothwick |
15 |
|
16 |
OK, so returning to your original response, you suggest increasing the |
17 |
size of each physical partition and then resizing each of the physical |
18 |
partitions independently? (/dev/sdwhatever instead of /dev/md6 |
19 |
directly?) |
20 |
|
21 |
Is there a reason or personal experience you have to not to resize the |
22 |
RAID-5 directly? I completely trust you as to date I cannot remember |
23 |
anything you suggested I do that wasn't a good way to do it but doing |
24 |
/dev/sdwhatever seems problematic if it had been an 8-drive RAID-1 |
25 |
becoming a RAID-5, etc. |
26 |
|
27 |
- Mark |
28 |
|
29 |
<quote> |
30 |
Using cfdisk or fdisk, delete the partition and recreate it, USING THE |
31 |
SAME START BLOCK at a larger size. |
32 |
|
33 |
Then "resize2fs /dev/sdwhatever" will resize the filesystem to fill the |
34 |
partition. |
35 |
</quote> |