quoted

quoted

quoted

quoted

"Bill" == Bill Davidsen [off-list ref] writes:

quoted

Is there anyway I can interrupt the command I used:

mdadm --grow /dev/md0 --size=#####

which I know now I should have used the --size=max paramter instead,
but it wasn't in the man page or the online help.  Oh well...

I tried removing the bitmap with:

mdadm --grow /dev/md0 --bitmap=none

but of course it won't let me do that.  Would I have to hot-fail one
of my disks to interrupt the re-sync, so I can remove the bitmap, so I
can then grow the RAID1 to the max volume size?

Bill> I think you could interrupt it by echoing 'idle' to the
Bill> sync_action, but I personally wouldn't do that, since there are
Bill> indications of some problem already, and doing another unusual
Bill> thing is not prudent.

Doing an 'echo idle > sync_action' was not a good idea.  The system
was not happy with me.  This I consider to be a bug, since the MD
system should just ignore commands it can't handle at a point.  

So you'd need to do the echo first, then a cat to check the status.  

Bill> I doubt you problems are caused by specifying the size rather
Bill> than using "max," unless you got it wrong, in which case I
Bill> wouldn't guess what is going to happen.

It looks like it's a known issue with bitmaps that Neil hasn't fixed
yet.  Oh well.  Now my problems seem to be bad blocks on the new
disk.  Sigh...  *grin*  

But I'm now running on the new disks ok and enjoying the extra disk
space.


John