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

[mauelshagen@redhat.com: Re: [dm-devel] RAID5 support ?]

Hrm, posted to wrong list ;)

----- Forwarded message from Heinz Mauelshagen <mauelshagen redhat com> -----

X-Sieve: CMU Sieve 2.2
Date: Tue, 25 Oct 2005 19:04:44 +0200
From: Heinz Mauelshagen <mauelshagen redhat com>
To: ataraid-list redhat com
Cc: hjm redhat com
Subject: Re: [dm-devel] RAID5 support ?
Reply-To: mauelshagen redhat com
In-Reply-To: <62b0912f0510250812l3a9ab85bo7887fc07b9c5cb44 mail gmail com>
User-Agent: Mutt/1.4.1i
X-Sender: mauelshagen RedHat com

On Tue, Oct 25, 2005 at 05:12:53PM +0200, Molle Bestefich wrote:
> Heinz Mauelshagen wrote:
> > FYI: we keep information about which regions (arbitrary sized segments
> >      of the address space) of the set are dirty with the the
> >      device-mapper dirty-log so that we can resynchonize those at set startup.
> Sounds sort of nasty.
> What happens if the user boots to Windows in the mean time?
> Windows will see corrupted data?


that was a general statement about device-mapper, not how I use
it with dmraid. dmraid relies on the simple ATARAID metadata which
essentially keeps a clean/dirty flag for the whole set.

Sorry for being unclear,

> (I mean, that's the whole point of using a hardware soft-RAID
> solution, isn't it?  BIOS and multiple-OS support for the metadata
> format / RAID arrays?)


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

----- End forwarded message -----

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