Re: Bitmap does not account for write errors prior to kicking?

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

 



On Wed, Jan 15, 2014 at 04:31:41PM +0100, Ethan Wilson wrote:
[...]
> What do you think about this problem?

Hi Ethan,

I noticed something similar, but I
could not really pin point it.

I've a test RAID-6 made of USB drives.
These drives, being USB, are prone to
leave the array.
So, sometimes, one drive is kicked out.
Having the bitmap active, is no problem
to re-add it back.

Checking the filesystem later, it happens,
sometimes, to find errors.

Now that you point out, it seems a similar
situation. As you wrote is seems the bitmap
is clear before the actual data is written.

Unfortunately, it is difficult (for me) to
reproduce or debug.

bye,

pg

> Thanks
> Ethan
> --
> 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

-- 

piergiorgio
--
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