Re: Hello,Re: GPT Table broken on a Raid1

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

 



On Sep 26, 2012, at 6:17 AM, Günther J. Niederwimmer wrote:
>> 
>> dirty state.
> 
> OK, I run the Intel Tool in windows two times with the last Tool I found.
> 
> The Tool don't found any Problem (?) and don't repair, but mdadm….

I'm going to trim this down:

> 
> /dev/sda:
> [Volume0]:
>           UUID : ec120401:b6ed52e6:3814fac4:48fcf4fc
>       Map State : normal
>    Dirty State : clean
> 
> 
> /dev/sdb:
> [Volume0]:
>           UUID : ec120401:b6ed52e6:3814fac4:48fcf4fc
>      Map State : normal
>    Dirty State : dirty
>                 °°°°°°°

I don't understand this UI. Are there two Volume0's? 

I can see how the dirty state would apply independently among physical devices /dev/sda and /dev/sdb. But the virtual device, the array volume, "Volume0" seems like it would have only one instance. So I don't understand how it can be clean in one case and dirty in another.



Chris Murphy

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