From: Paul Clements <paul.clements@steeleye.com>
To: Shaya Potter <spotter@yucs.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: accessing windows raid with mdadm?
Date: Sat, 04 Nov 2006 11:53:57 -0500 [thread overview]
Message-ID: <454CC5A5.4030202@steeleye.com> (raw)
In-Reply-To: <1162419372.4743.6.camel@localhost.localdomain>
Shaya Potter wrote:
> [please cc: me on responses]
>
> if one read Documentation/fs/ntfs.txt in the linux kernel, it talks
> about accessing windows raid volumes in Linux
>
> If one is using non raid-5, one can use the device mapper, but if one is
> using raid-5, one has to use the md driver.
>
> However, it seems to be about using raidtools (raidtab and the like).
> Can anyone who understand raidtools and mdadm translate the instructions
> to mdadm, as that would seem to be what most of us use today?
The biggest thing here is that, since Windows stores its RAID
information in this LDM area, which is outside the partitions
themselves, there is no room for an md superblock at the end of each
partition (even if the RAID information was on each partition, it's
doubtful there would be room for an md superblock). So you have to
assemble the array without superblocks, or else the md superblocks will
overwrite data.
There is currently no way to "Build" (i.e., assemble an array without
using superblocks) a raid5 array using mdadm. I don't know if raidtools
would allow that or not. Building arrays without superblocks is
generally risky (since device states and roles are not persistently
tracked) for anything other than simple non-RAID arrays, or read-only
access to your data.
--
Paul
prev parent reply other threads:[~2006-11-04 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 22:16 accessing windows raid with mdadm? Shaya Potter
2006-11-04 16:53 ` Paul Clements [this message]
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=454CC5A5.4030202@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=linux-raid@vger.kernel.org \
--cc=spotter@yucs.org \
/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;
as well as URLs for NNTP newsgroup(s).