Martchus
/
mdadm
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Grow: Allow for component_size not being set for RAID0 arrays. 

When an RAID0 is started using SET_ARRAY_INFO ioctl the
component_size will be zero.
This confused the code for reshaping a RAID0 via RAID4.

So if that seems to be the case, fake a believable component_size

Signed-off-by: NeilBrown <neilb@suse.de>
This commit is contained in:
NeilBrown 2011-03-10 15:00:38 +11:00
parent d424212ed9
commit 9468aeac57
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
Grow.c
View File

@ -1649,6 +1649,18 @@ static int reshape_array(char *container, int fd, char *devname,
int done;
struct mdinfo *sra = NULL;
/* when reshaping a RAID0, the component_size might be zero.
* So try to fix that up.
*/
if (ioctl(fd, GET_ARRAY_INFO, &array) != 0) {
dprintf("Cannot get array information.\n");
goto release;
}
if (array.level == 0 && info->component_size == 0) {
get_dev_size(fd, NULL, &array_size);
info->component_size = array_size / array.raid_disks;
}
if (info->reshape_active) {
int new_level = info->new_level;
info->new_level = UnSet;
@ -1671,10 +1683,6 @@ static int reshape_array(char *container, int fd, char *devname,
" cannot continue.\n");
goto release;
}
if (ioctl(fd, GET_ARRAY_INFO, &array) != 0) {
dprintf("Cannot get array information.\n");
goto release;
}
if (restart) {
/* reshape already started. just skip to monitoring the reshape */