Re: Does "--write-behind=" have to be done at create time?

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

 



On Thu, 2007-06-28 at 23:22 +0930, Ian Dall wrote:
> I was wanting to try out the "--write-behind" option. I have a raid1
> with bitmaps and write-mostly enabled, which are all the pre-requisites,
> I think.
> 
> It would be nice if you could tweak this parameter on a live array, but
> failing that, it is hard to see why it couldn't be done at assemble
> time. mdadm wont let me though.
> 
> Is this a fundamental limitation?

Looking through the mdadm source code it seems like


		case O(BUILD, WriteBehind):
		case O(CREATE, WriteBehind): /* write-behind mode */

could be changed to 

		case O(GROW, WriteBehind):
		case O(BUILD, WriteBehind):
		case O(CREATE, WriteBehind): /* write-behind mode */

and everything would be OK. I am completely new to this code though, so
I am I missing something?

If you already had a bitmap you would need to remove it first
(--bitmap=none) and then grow it back with writebehind set.

Ian

-- 
Ian Dall <ian@xxxxxxxxxxxxxxxxxxxxx>
-
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