From: Goswin von Brederlow <goswin-v-b@web.de>
To: mark delfman <markdelfman@googlemail.com>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, linux-raid@vger.kernel.org
Subject: Re: -z not on RAID0 / MPIO hurdle
Date: Mon, 17 Aug 2009 09:32:56 +0200 [thread overview]
Message-ID: <87zl9yvqs7.fsf@frosties.localdomain> (raw)
In-Reply-To: <66781b10908140129t4fc0947ek1e6f211758a2e969@mail.gmail.com> (mark delfman's message of "Fri, 14 Aug 2009 09:29:39 +0100")
mark delfman <markdelfman@googlemail.com> writes:
> Hi Goswin,
>
> I am not sure that this would work well for us... we would have you
> use LVM to create individual block targerts, then use MD to create
> RAIDs and then LVM again to create pools.
Last I tried raid on lvm would mess with the idle I/O
determination. The raid rebuild would cause I/O on the device mapper
and then raid things the user is doing I/O and slows the raid rebuild
down to the minimum speed.
> We would ideally stay to LVM on all our raids (whether 0 / 6 etc). so
> would like to keep it in there...
>
> Does any know if there is a reason -z doesnât work with RAID0 (i mean
> is it designed to not work because of abc reason, or simply its never
> been needed etc)?
>
>
> Thank you for you help
>
>
> Mark D
> On Thu, Aug 13, 2009 at 3:06 AM, Goswin von Brederlow<goswin-v-b@web.de> wrote:
>> mark delfman <markdelfman@googlemail.com> writes:
>>
>>> Hi.... I am hopeful that the group could provide me with some advice
>>> regarding limiting the drive size on a RAID0. Â I know and use the âz
>>> option for other raid levels, but this seems to have no effect on
>>> RAID0.
>>>
>>> I am sure many will ask âwhy botherâ or âuse fdiskâ but the problem is:
>>>
>>> We need to have some preserved information on each drive â can be only
>>> a few MB at the end of the drive for example
>>> In the past we have simply used Fdisk to partition, save our data on
>>> Sdx2 and used Mdadm on Sdx1 Â (which works fine)
>>> But we are looking to move to dual channel SAS drives and use DM MPIO
>>>
>>> DM MPIO works fine also, but not on the partitions, only the whole
>>> drive. Â So when we MDadm DMx it overwrites the SdX2 partition etc.
>>>
>>> The answer was that we used the âz and limited the drive size and
>>> simply used DD to write our data to the end LBAâs....
>>>
>>> But on RAID0 the âz does not seem to function, so I cant think of a
>>> way around this ï Â (other than changing the LBA range in the drive and
>>> this is restricted I think)
>>>
>>>
>>> Does anyone have any ideas? Â I appreciate any help
>>
>> LVM and --setphysicalvolumesize on pvcreate?
>>
>> MfG
>> Â Â Â Â Goswin
>>
MfG
Goswin
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-08-17 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 18:44 -z not on RAID0 / MPIO hurdle mark delfman
2009-08-13 2:06 ` Goswin von Brederlow
2009-08-14 8:29 ` mark delfman
2009-08-17 7:32 ` Goswin von Brederlow [this message]
2009-08-14 15:35 ` Luca Berra
2009-08-15 9:33 ` mark delfman
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=87zl9yvqs7.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=linux-raid@vger.kernel.org \
--cc=markdelfman@googlemail.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