RE: Ataraid-list Digest, Vol 42, Issue 15

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

 



>Yes, I know, dmraid just reads the on-disk metadata.
>What I have been talking about is the RAID configuration process in the
>BIOS on the S5000VSA board. As I was told by Eric this should be ISW
and
>not DDF1, I guess it is not possible to let the configurator on
S5000VSA
>board create DDF1 format? So, I am wondering why this RAID is detected
>as DDF1, if it should be ISW. But this will have to answered by the
>reporter (I do not have this hardware so I cannot do tests personally).
>

Metadata has different format and stored on a pre-assigned location of
hard devices. DDF1 and ISW store their metadata on different locations.
That means both of them can work together. (It's messy somehow.) It
requires a tool to create a kind of metadata and write it to the
corresponding hard devices. Intel OROM has the ability to do that and
I'm sure different venders provide its own way to facilitate it too.
(That won't happen automatically and requires user involvement.)
Therefore, an Intel board doesn't mean the hard disks have the ISW
format. The output from "dmraid -s -ccc" tells me that the reporter has
the DDF1 format on his/her disks. The DDF1 metadata won't go away until
"dmraid -rE " is conducted. 

Also the below dump shows that the name of the t-group raid set is
".ddf1_disks". If you use that name as the command line argument,
"dmraid -s -ccc .ddfa_disks" should work. I'm working on ISW metadata
creation now and will tackle this issue later as ISW format experiences
the same. 

As far as the crash, I have no idea where the bug is and will keep an
eye on it. 

BTW, I wasn't aware the issue until last email I got for the mailing
list. Could you point me to the original one?

Thanks,
Ying

>> I guess that you have a metadata in ddf format. Could you send
>> me the dumps of "dmraid -n" and "dmraid -s -ccc"?
>
>Currently I have the output of dmraid -s -ccc available:
>
>DEBUG: _find_set: searching .ddf1_disks
>DEBUG: _find_set: not found .ddf1_disks
>DEBUG: _find_set: searching
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: searching
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: not found
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: not found
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: searching .ddf1_disks
>DEBUG: _find_set: found .ddf1_disks
>DEBUG: _find_set: searching
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: searching
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: found
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: found
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: searching .ddf1_disks
>DEBUG: _find_set: found .ddf1_disks
>DEBUG: _find_set: searching
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: searching
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: found
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: found
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: searching .ddf1_disks
>DEBUG: _find_set: found .ddf1_disks
>DEBUG: _find_set: searching
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: searching
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: found
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: _find_set: found
>ddf1_4c534920202020201000005500000000330d9ac500000a28
>DEBUG: checking ddf1 device "/dev/sda"
>DEBUG: checking ddf1 device "/dev/sdc"
>DEBUG: checking ddf1 device "/dev/sdb"
>DEBUG: checking ddf1 device "/dev/sdd"
>DEBUG: set status of set
>"ddf1_4c534920202020201000005500000000330d9ac500000a28" to 16
>DEBUG: set status of set ".ddf1_disks" to 16
>ddf1_4c534920202020201000005500000000330d9ac500000a28:974608384:128:mir
ror:
>ok:0:4:0
>/dev/sda:ddf1:ddf1_4c534920202020201000005500000000330d9ac500000a28:mir
ror:
>ok:974608384:0
>/dev/sdc:ddf1:ddf1_4c534920202020201000005500000000330d9ac500000a28:mir
ror:
>ok:974608384:0
>/dev/sdb:ddf1:ddf1_4c534920202020201000005500000000330d9ac500000a28:mir
ror:
>ok:974608384:0
>/dev/sdd:ddf1:ddf1_4c534920202020201000005500000000330d9ac500000a28:mir
ror:
>ok:974608384:0
>DEBUG: freeing devices of RAID set
>"ddf1_4c534920202020201000005500000000330d9ac500000a28"
>DEBUG: freeing device
>"ddf1_4c534920202020201000005500000000330d9ac500000a28", path
"/dev/sda"
>DEBUG: freeing device
>"ddf1_4c534920202020201000005500000000330d9ac500000a28", path
"/dev/sdc"
>DEBUG: freeing device
>"ddf1_4c534920202020201000005500000000330d9ac500000a28", path
"/dev/sdb"
>DEBUG: freeing device
>"ddf1_4c534920202020201000005500000000330d9ac500000a28", path
"/dev/sdd"
>DEBUG: freeing devices of RAID set ".ddf1_disks"
>DEBUG: freeing device ".ddf1_disks", path "/dev/sda"
>DEBUG: freeing device ".ddf1_disks", path "/dev/sdb"
>DEBUG: freeing device ".ddf1_disks", path "/dev/sdc"
>DEBUG: freeing device ".ddf1_disks", path "/dev/sdd"
>
>

_______________________________________________
Ataraid-list mailing list
Ataraid-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/ataraid-list

[Index of Archives]     [Linux RAID]     [Linux Device Mapper]     [Linux IDE]     [Linux SCSI]     [Kernel]     [Linux Books]     [Linux Admin]     [GFS]     [RPM]     [Yosemite Campgrounds]     [AMD 64]

  Powered by Linux