Re: Reduce resync time by keeping track of referenced blocks

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

 




Am 08.07.2018 um 20:28 schrieb Weedy:
> On 8 July 2018 at 18:23, Wols Lists <antlists@xxxxxxxxxxxxxxx> wrote:
>> The problem with this is that (a) MD has no idea which bits of the disk
>> are in use and which are not, and (b) just copying the bits that are in
>> use will leave the unused bits in an unsync'd state, which will then
>> moan blue murder on a check.
>>
>> It would make sense to prioritise that used stuff, but you do need to
>> copy everything. If, however, we could get TRIM to actually zero the
>> disk, that might well speed things up. It will need a lot of thinking
>> through, though. It's a lot trickier than it sounds.
> 
> It counts unallocated blocks?!?!?! whyyyyyyyyyy

because it's just a block-layer with no knowledge about the filesystem
on top
--
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