1 |
On Thu, Nov 17, 2011 at 1:59 PM, Mark Knecht <markknecht@×××××.com> wrote: |
2 |
> On Thu, Nov 17, 2011 at 10:43 AM, Michael Mol <mikemol@×××××.com> wrote: |
3 |
>> On Thu, Nov 17, 2011 at 1:29 PM, Mark Knecht <markknecht@×××××.com> wrote: |
4 |
> <SNIP> |
5 |
>>> At this point I was told: |
6 |
>>> |
7 |
>>> "Now, resize your filesystem to use the additional space." |
8 |
>>> |
9 |
>>> So, if at this point the end-block of sda6 isn't 976768064 but, let's |
10 |
>>> say, 700000000 because mdadm set it to something new, then using your |
11 |
>>> suggestion I guess I'd set it back to 976768064? I'm not comfortable |
12 |
>>> however that if I do that that whatever is out there beyond 700000000 |
13 |
>>> is really formatted as ext3 and 'empty' as I don't know what the mdadm |
14 |
>>> conversion has done to it. |
15 |
>> |
16 |
>> Your resize would be applied not to /dev/sd?, but to /dev/md?. You |
17 |
>> don't need to worry about what that means on /dev/sd*; the filesystem |
18 |
>> you want to poke is on /dev/md*. |
19 |
>> |
20 |
>> file -s /dev/sd* /dev/md* |
21 |
>> |
22 |
>> -- |
23 |
>> :wq |
24 |
> |
25 |
> Yes, resize would be done to /dev/md?. I agree. However I don't |
26 |
> believe that I'd use Neil's suggestion of fdisk block numbers on |
27 |
> /dev/md, right? That doesn't make sense to me and I don't beleieve |
28 |
> Neil was suggesting anything like that. |
29 |
> |
30 |
> I'm thinking that possibly the mdadm way to change the _size_ of a |
31 |
> RAID is to once again use the grow option: |
32 |
> |
33 |
> <quote> |
34 |
> -G, --grow |
35 |
> Change the size or shape of an active array. |
36 |
> <quote> |
37 |
> |
38 |
> I've not yet found any instructions that I trust to do it though, and |
39 |
> being that the instructions above came from, among others, Neil Brown |
40 |
> who manages mdadm I'm hesitant to go in my own direction. I'm just |
41 |
> looking before I leap. |
42 |
> |
43 |
> And fortunately, if I decided to just blow away all three disks and |
44 |
> start from scratch I have very little at risk that way, and very |
45 |
> little risk as I will do backups of the RAID-1 onto an external USB |
46 |
> drive before I start this process anyway. |
47 |
|
48 |
Ok, I thought you had it clear how you were going to resize the raid, |
49 |
and needed help resizing the filesystem that already existed on top of |
50 |
the RAID. I interpreted Mark's instructions as operating under that |
51 |
impression, too. |
52 |
|
53 |
Are you saying you don't already have a partition table sitting on top |
54 |
of /dev/md? ? |
55 |
|
56 |
|
57 |
-- |
58 |
:wq |