RE: create metadata from DMRAID

>> 2. A metadata handler needs build metadata based on several data such
as
>> raid set name, raid level, size, etc. Can they be carried into as a
>> string argument or a field in "struct lib_context"? It's possible to
>> build disk sets, raid device sets, and raid set sets too.
>
>No, a create_set() function needs adding to the library, which can
>be called with a struct holding the respective parameters and lists of
>devices involved.
>
>That function will derive properties of raid_dev arguments
>for the metadata format handler .create method.
>
>commands.[ch] need the respective extensions to support
>the "-C/--create" command line option.
>
>> 3. Can I design my own option format to create metadata by DMRAID
such
>> as:"dmraid -ms isw_xxxxxx_raidSet1" (d and D have been used.) to
delete
>> a raid set and "dmraid -f isw -w "isw_xxxx_raidNewSet device-mapper
>> format" where device-mapper format is "0 1028160 striped 2 256
/dev/sdb
>> 0 /dev/sdc 0". But I have trouble for nested raid setup and try to
use
>> raid10 or raid51 to identify it.
>
>To create a RAID set:
>dmraid -C isw_xxxxxx_raidSet1 [--layout LAYOUT] [--size X[kmgt]]
>[DevicePath...]

Re: create metadata from DMRAID

On Sun, Jul 01, 2007 at 11:41:34PM -0700, Fang, Ying wrote:
> >> 2. A metadata handler needs build metadata based on several data such
> as
> >> raid set name, raid level, size, etc. Can they be carried into as a
> >> string argument or a field in "struct lib_context"? It's possible to
> >> build disk sets, raid device sets, and raid set sets too.
> >
> >No, a create_set() function needs adding to the library, which can
> >be called with a struct holding the respective parameters and lists of
> >devices involved.
> >
> >That function will derive properties of raid_dev arguments
> >for the metadata format handler .create method.
> >
> >commands.[ch] need the respective extensions to support
> >the "-C/--create" command line option.
> >
> >> 3. Can I design my own option format to create metadata by DMRAID
> such
> >> as:"dmraid -ms isw_xxxxxx_raidSet1" (d and D have been used.) to
> delete
> >> a raid set and "dmraid -f isw -w "isw_xxxx_raidNewSet device-mapper
> >> format" where device-mapper format is "0 1028160 striped 2 256
> /dev/sdb
> >> 0 /dev/sdc 0". But I have trouble for nested raid setup and try to
> use
> >> raid10 or raid51 to identify it.
> >
> >To create a RAID set:
> >dmraid -C isw_xxxxxx_raidSet1 [--layout LAYOUT] [--size X[kmgt]]

RE: create metadata from DMRAID

Is .write being used by any format handlers currently ? If .write is
used to write the complete metadata, then it can be used to create the
metadata also, right ? 

Also, instead of 'dmraid -C isw_xxxxxx_raidSet1 .....'
How about  'dmraid -C VolumeName ...'
And then isw can prepend isw_xxxxxx to the volume name to make
isw_xxxxx_VolumeName
This way, different format handlers can make up their own string and one
need not give isw specific string from the command line (since isw_xxxxx
is generated internally by isw anyway).

-----Original Message-----
From: ataraid-list-bounces <at> redhat.com
[mailto:ataraid-list-bounces <at> redhat.com] On Behalf Of Heinz Mauelshagen
Sent: Monday, July 02, 2007 3:45 AM
To: Fang, Ying
Cc: ATARAID (eg, Promise Fasttrak, Highpoint 370) related discussions
Subject: Re: create metadata from DMRAID

On Sun, Jul 01, 2007 at 11:41:34PM -0700, Fang, Ying wrote:
> >> 2. A metadata handler needs build metadata based on several data
such
> as
> >> raid set name, raid level, size, etc. Can they be carried into as a
> >> string argument or a field in "struct lib_context"? It's possible
to
> >> build disk sets, raid device sets, and raid set sets too.
> >
> >No, a create_set() function needs adding to the library, which can

Re: create metadata from DMRAID

On Mon, Jul 02, 2007 at 11:23:08AM -0700, Kulkarni, Sunil A wrote:
> Is .write being used by any format handlers currently ? If .write is
> used to write the complete metadata, then it can be used to create the
> metadata also, right ? 

Last time I looked, the asr handler uses .write when reconfiguring
RAID1 sets.

And no, create should be in its own function because writing and
creating are orthogonal operations--create happens once; write happens
any time you reconfigure the array.

> Also, instead of 'dmraid -C isw_xxxxxx_raidSet1 .....'
> How about  'dmraid -C VolumeName ...'
> And then isw can prepend isw_xxxxxx to the volume name to make
> isw_xxxxx_VolumeName
> This way, different format handlers can make up their own string and one
> need not give isw specific string from the command line (since isw_xxxxx
> is generated internally by isw anyway).

How do you specify which handler format you want?  Separate switch, or
embedded in the volume name?  Also, some raids let you specify a
volumename; others only provide for a bunch of hex numbers.

--D

_______________________________________________
Ataraid-list mailing list
Ataraid-list <at> redhat.com

RE: create metadata from DMRAID

There is already a switch -f for format handler. Also, user cannot give
xxxxx of isw_xxxxx.  

-----Original Message-----
From: ataraid-list-bounces <at> redhat.com
[mailto:ataraid-list-bounces <at> redhat.com] On Behalf Of Darrick J. Wong
Sent: Monday, July 02, 2007 12:19 PM
To: ATARAID (eg, Promise Fasttrak, Highpoint 370) related discussions
Subject: Re: create metadata from DMRAID

On Mon, Jul 02, 2007 at 11:23:08AM -0700, Kulkarni, Sunil A wrote:
> Is .write being used by any format handlers currently ? If .write is
> used to write the complete metadata, then it can be used to create the
> metadata also, right ? 

Last time I looked, the asr handler uses .write when reconfiguring
RAID1 sets.

And no, create should be in its own function because writing and
creating are orthogonal operations--create happens once; write happens
any time you reconfigure the array.

> Also, instead of 'dmraid -C isw_xxxxxx_raidSet1 .....'
> How about  'dmraid -C VolumeName ...'
> And then isw can prepend isw_xxxxxx to the volume name to make
> isw_xxxxx_VolumeName
> This way, different format handlers can make up their own string and
one
> need not give isw specific string from the command line (since
isw_xxxxx

RE: create metadata from DMRAID

>
>The data structure already exist: raid_set and raid_dev.
>For one-level sets, a raid_set structure with multiple raid_dev
>structures hanging off.
>For 2-level sets (eg. RAID10), a top-level raid_set structure, multiple
>bottom level raid_set structures hanging off it and multiple raid_dev
>structures hanging off the bottom level ones.
>
>You got to check, if the properties (ie. the structure mebers) are
>sufficient or if we need to add some.
>
>> Then it calls .create of an
>> appropriate handler to build and write metadata to each hard device
of
>> the raid set.
>
>It calls a) .create and of that succeeds it'll call b) .write
>in a followup step.

You mean the metadata creation procedure is the reverse path of building
a raidset from metadata:
1. create a raid set (struct raid_set) and its subsets
2. create a list of raid devices for all subsets
3. call .create for each raid device to generate a complete metadata
attached to the device (struct raid_dev)
4. call .write to write metadata to each hard drive.

>>
>> How about manual and auto rebuilding? Should updating metadata status
be

FC6 Raid Mirror Problem

Hello Heinz,

Ignace on the keyboard. I'm experiencing a strange thing.
I have :
motherboards : Asrock AM2NF6G-VSTA
Processor : AMD2
Chipset : NVIDIA® GeForce 6100 / nForce 405 Chipset
DD : 2 * MAXTOR 6V080E0 SATA Disk
Array : RAID Mirroring

and i install FC6 on the mirror without problem. Go restarting it and :
ACPI [OK]
RedHat Nash starting
and unable to access resume device (LABEL=SWAP-nvidia_gee)
so mounting /dev failed
setuproot error mounting /proc /sys
so kernel panic.

And my server don't go anywhere else.
Somebody can help, or the FC7 solve the problem??

Thanks in regards Ignace

Re: FC6 Raid Mirror Problem

On Tue, Jul 03, 2007 at 03:29:33AM -0400, Ignace BIENVILLE wrote:
> Hello Heinz,
> 
> Ignace on the keyboard. I'm experiencing a strange thing.
> I have :
> motherboards : Asrock AM2NF6G-VSTA
> Processor : AMD2
> Chipset : NVIDIA® GeForce 6100 / nForce 405 Chipset
> DD : 2 * MAXTOR 6V080E0 SATA Disk
> Array : RAID Mirroring
> 
> and i install FC6 on the mirror without problem. Go restarting it and :
> ACPI [OK]
> RedHat Nash starting
> and unable to access resume device (LABEL=SWAP-nvidia_gee)
> so mounting /dev failed
> setuproot error mounting /proc /sys
> so kernel panic.
> 
> And my server don't go anywhere else.
> Somebody can help, or the FC7 solve the problem??

Yes, I think so. Please try.

Regards,
Heinz

> 
> Thanks in regards Ignace

Re: create metadata from DMRAID

On Mon, Jul 02, 2007 at 04:51:24PM -0700, Fang, Ying wrote:
> >
> >The data structure already exist: raid_set and raid_dev.
> >For one-level sets, a raid_set structure with multiple raid_dev
> >structures hanging off.
> >For 2-level sets (eg. RAID10), a top-level raid_set structure, multiple
> >bottom level raid_set structures hanging off it and multiple raid_dev
> >structures hanging off the bottom level ones.
> >
> >You got to check, if the properties (ie. the structure mebers) are
> >sufficient or if we need to add some.
> >
> >> Then it calls .create of an
> >> appropriate handler to build and write metadata to each hard device
> of
> >> the raid set.
> >
> >It calls a) .create and of that succeeds it'll call b) .write
> >in a followup step.
> 
> You mean the metadata creation procedure is the reverse path of building
> a raidset from metadata:
> 1. create a raid set (struct raid_set) and its subsets
> 2. create a list of raid devices for all subsets

Yes, a list of raid devices for each lowest level subset.

> 3. call .create for each raid device to generate a complete metadata
> attached to the device (struct raid_dev)

Re: create metadata from DMRAID

On Mon, Jul 02, 2007 at 12:18:46PM -0700, Darrick J. Wong wrote:
> On Mon, Jul 02, 2007 at 11:23:08AM -0700, Kulkarni, Sunil A wrote:
> > Is .write being used by any format handlers currently ? If .write is
> > used to write the complete metadata, then it can be used to create the
> > metadata also, right ? 
> 
> Last time I looked, the asr handler uses .write when reconfiguring
> RAID1 sets.
> 
> And no, create should be in its own function because writing and
> creating are orthogonal operations--create happens once; write happens
> any time you reconfigure the array.

Exactly.

> 
> > Also, instead of 'dmraid -C isw_xxxxxx_raidSet1 .....'
> > How about  'dmraid -C VolumeName ...'
> > And then isw can prepend isw_xxxxxx to the volume name to make
> > isw_xxxxx_VolumeName
> > This way, different format handlers can make up their own string and one
> > need not give isw specific string from the command line (since isw_xxxxx
> > is generated internally by isw anyway).
> 
> How do you specify which handler format you want?  Separate switch, or
> embedded in the volume name?  Also, some raids let you specify a
> volumename; others only provide for a bunch of hex numbers.

-f option.