mdadm source rpm build error + command-line parsing error + resync reporting problem
Quoted 7 lines · Neil Brown
Quoted 3 lines
The man page indicates that if I don't set the size, it will grow to fill the smallest device in the array. It's definitely not doing that...
Could you please point me to the part of the man page that says that? I will try to fix it.
I see what you mean now - I got confused because there are two paragraphs in the size option description, one indicates that you don't need to set it, then the second paragraph discusses the "grow" context and indicates you can use 'max'.
The first paragraph doesn't indicate a specific context, so I took it to cover all possible contexts where 'size' was applicable, and it seems like it isn't
I did successfully grow my md arrays though, which was nice, but then ext2online didn't do what I asked it to do, and now I'm back to just doing the more typical dump/restore thing anyway.
Not really on-topic, but has anyone else gotten ext2online to work? I get this "Dec 8 21:27:02 istanbul kernel: JBD: ext2online wants too many credits (2050 > 2048)" after letting it attempt to extend the FS to cover the entire device.
-Mike
Quoted 5 lines · On Thursday December 8, [email protected] wrote:
Not really on-topic, but has anyone else gotten ext2online to work? I get this "Dec 8 21:27:02 istanbul kernel: JBD: ext2online wants too many credits (2050 > 2048)" after letting it attempt to extend the FS to cover the entire device.
I haven't used ext2online myself, but I believe that there are some aspects of the filesystem that it is not able to resize, and you have to have created your filesystem with the understanding that you might want to grow it later.
From the mkfs.ext3 man page:
-E extended-options
...
resize=max-online-resize
Reserve enough space so that the block group
descriptor table can grow to support a filesystem that has max-online-resize blocks.
Not a very desirable situation, but just part of the legacy that ext2/3 brings with it.
So this time when you mkfs your new arrays, plan for growth :-)
NeilBrown
Quoted 22 lines · Neil Brown
Quoted 4 lines · On Thursday December 8, [email protected] wrote:
Not really on-topic, but has anyone else gotten ext2online to work? I get this "Dec 8 21:27:02 istanbul kernel: JBD: ext2online wants too many credits (2050 > 2048)" after letting it attempt to extend the FS to cover the entire device.
I haven't used ext2online myself, but I believe that there are some aspects of the filesystem that it is not able to resize, and you have to have created your filesystem with the understanding that you might want to grow it later.
From the mkfs.ext3 man page:-E extended-options
...
resize=max-online-resize
Reserve enough space so that the block group
descriptor table can grow to support a filesystem that has max-online-resize blocks.
Quoted 6 lines
Not a very desirable situation, but just part of the legacy that ext2/3 brings with it.
So this time when you mkfs your new arrays, plan for growth :-)
NeilBrown
I was able to boot off the redhat install CD, use the 'linux rescue' mode to get a shell, and then use resize2fs to do what I wanted.
Basically, if you didn't plan ahead with the right max-online-resize option, you can still grow the filesystem, just not while it's mounted and running.
So at this point, I've got twice the disk space on both the systems I was working on. If only I had more to do, now that I know what I'm doing...
-Mike