Re: [PATCH] md: forbid a RAID5 from having both a bitmap and a journal.

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

 



On 10/17/2017 17:03, NeilBrown wrote:
> On Tue, Oct 17 2017, John Stoffel wrote:
> 
>>>>>>> "NeilBrown" == NeilBrown  <neilb@xxxxxxxx> writes:
>>
>> NeilBrown> Having both a bitmap and a journal is pointless.
>> NeilBrown> Attempting to do so can corrupt the bitmap if the journal
>> NeilBrown> replay happens before the bitmap is initialized.
>> NeilBrown> Rather than try to avoid this corruption, simply
>> NeilBrown> refuse to allow arrays with both a bitmap and a journal.
>> NeilBrown> So:
>> NeilBrown>  - if raid5_run sees both are present, fail.
>>
>> So what happens if there's someone out there with an array setup with
>> both already?  Should the journal or the bitmap be removed at this
>> time?  
> 
> If someone has an array like that they can assemble it with
>   --update=no-bitmap

IMHO, this should probably get documented in the Linux RAID Wiki once it goes
through.


> I'd rather not automatically disable things.
> 
> Thanks,
> NeilBrown

-- 
Joshua Kinard
Gentoo/MIPS
kumba@xxxxxxxxxx
6144R/F5C6C943 2015-04-27
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943

"The past tempts us, the present confuses us, the future frightens us.  And our
lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic
--
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