Re: [PATCH 1/3] Create: Allow to create two volumes of different sizes within one container

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

 



[ reviving old thread given the recent patch from Adam [1]]

On Tue, Sep 20, 2011 at 11:55 PM, NeilBrown <neilb@xxxxxxx> wrote:
>> Yeah, the changelog is backwards, and this breaks tests/08imsm-overlap
>> because it does not honor IMSM_NO_PLATFORM.  How about the attached?
>
> Better (though text/plain attachments are preferred over
> application/octet-stream....)

Yeah, gmail picked that unfortunately... need to get my evolution
setup going again.

> However there still seems to be confusion over num_disks versus num_members.
>
> You compare num_disks to raiddisks but my understanding is that num_disks can
> include spares while raiddisks definitely doesn't.  Am I confused or are you?

Unfortunately the metadata has no knowledge of how many spares there
should be.  num_disks is always the current container membership as
and spare disks have a metadata record with num_disks == 1.

[1]: http://marc.info/?l=linux-raid&m=132387896006974&w=2
--
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