Linux Device Mapper development
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: "ATARAID (eg, Promise Fasttrak,
	 Highpoint 370) related discussions" <ataraid-list@redhat.com>
Cc: dm-devel@redhat.com, Chris McDermott <lcm@us.ibm.com>
Subject: Re: [PATCH] Add metadata writing and hot spare processing to hostraid driver in dmraid
Date: Sat, 4 Mar 2006 10:10:49 +0100	[thread overview]
Message-ID: <20060304091049.GC2966@redhat.com> (raw)
In-Reply-To: <4408E5F0.50208@us.ibm.com>

On Fri, Mar 03, 2006 at 04:57:20PM -0800, Darrick J. Wong wrote:
> Hi all,

Hi Darrick.

> 
> Now that dmraid supports Adaptec HostRAID, I've turned my attention to 
> enabling support for writing metadata back to the disks, and 
> implementing rudimentary spare handling in RAID1 configurations.
> 
> The attached patch (which is admittedly very rough) does two key things. 

Will look into it on Mon.

>  First, it implements asr_write in a more meaningful manner than what's 
> in rc10 right now; with that part of the patch, dmraid gains the ability 
> to reconfigure an array while the system is running and save the changes 
> out to disk.  To do this, I had to change a struct to a pointer to a 
> struct in asr_reservedblock to to get write_metadata to work properly. 
> Also, it turns out that a few more things in asr_write had to happen 
> (and in the correct order) for writes to succeed.  If we fail to write 
> the metadata correctly, the HostRAID BIOS wipes the entire sector during 
> the next reboot.
> 
> The second part of the patch stores spare devices in a dummy .asr_spares 
> array.  When an I/O error is noticed (via event_io), a suitable spare 
> drive is pulled from the spare pool and inserted into the failing array.
> I haven't had a chance to test this code rigorously yet, because the 
> dmeventd portions of dmraid aren't implemented yet.
> 
> So, there are two things that I'd like to see added: online 
> reconfiguration support in dmraid (which I can now test via asr_write) 
> and online spare handling.  Heinz, are you working on either of these 
> features, or should I start writing them?

I am into device-mapper core work right now so please, go ahead :)

Heinz

> 
> --D


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

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Red Hat GmbH
Consulting Development Engineer                   Am Sonnenhang 11
Cluster and Storage Development                   56242 Marienrachdorf
                                                  Germany
Mauelshagen@RedHat.com                            +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2006-03-04  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-04  0:57 [PATCH] Add metadata writing and hot spare processing to hostraid driver in dmraid Darrick J. Wong
2006-03-04  9:10 ` Heinz Mauelshagen [this message]
2006-03-04  9:14 ` Heinz Mauelshagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060304091049.GC2966@redhat.com \
    --to=mauelshagen@redhat.com \
    --cc=ataraid-list@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=lcm@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox