Re: broken raid level 5 array caused by user error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Phil,

Is it correct to use --data-offset=1024 when I want to set an offset of 2048? At least a mdadm --examine on one of the devices shows the offset is set to 2048 when using --data-offset=1024.

With --data-offset=1024 and both chunk sizes (64 & 512) I have something like a success when using this two orders:

sde sdd sdb sdc
sde sdb sdd sdc

I'm getting:

e2fsck 1.41.12 (17-May-2010)
/dev/md0 has unsupported feature(s): FEATURE_C16 FEATURE_C17 FEATURE_C18 FEATURE_C19 FEATURE_C21 FEATURE_C22 FEATURE_C23 FEATURE_C25 FEATURE_C27 FEATURE_C28 FEATURE_I29 FEATURE_R29
e2fsck: Get a newer version of e2fsck!

So I guess I should try some newer fsck version (I'm back on the old machine with centos 6, the failed reshaping was done with the new machine with centos 7).

Thanks

Mathias

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux