NeilBrown 25f7fd470b md: fix bug in handling of new_data_offset
commit c6563a8c38fde3c1c7fc925a10bde3ca20799301
    md: add possibility to change data-offset for devices.

introduced a 'new_data_offset' attribute which should normally
be the same as 'data_offset', but can be explicitly set to a different
value to allow a reshape operation to move the data.

Unfortunately when the 'data_offset' is explicitly set through
sysfs, the new_data_offset is not also set, so the two would become
out-of-sync incorrectly.

One result of this is that trying to set the 'size' after the
'data_offset' would fail because it is not permitted to set the size
when the 'data_offset' and 'new_data_offset' are different - as that
can be confusing.
Consequently when mdadm tried to do this while assembling an IMSM
array it would fail.

This bug was introduced in 3.5-rc1.

Reported-by: Brian Downing <bdowning@lavos.net>
Bisected-by: Brian Downing <bdowning@lavos.net>
Tested-by: Brian Downing <bdowning@lavos.net>
Signed-off-by: NeilBrown <neilb@suse.de>
2012-07-19 15:59:18 +10:00
..
2012-03-28 18:41:29 +01:00
2012-03-28 18:41:29 +01:00
2012-03-07 19:09:37 +00:00
2011-03-31 11:26:23 -03:00
2007-10-20 02:01:26 +01:00
2012-03-28 18:43:38 +01:00
2010-08-12 04:14:12 +01:00
2012-03-28 18:41:25 +01:00
2011-10-31 20:19:04 +00:00
2012-03-19 12:46:39 +11:00
2012-03-28 18:43:38 +01:00
2012-03-28 18:43:38 +01:00
2012-07-03 17:45:31 +10:00
2012-05-22 13:55:05 +10:00
2012-07-04 09:35:35 +10:00
2012-05-22 13:53:47 +10:00