From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Re: [PATCH] dm-striped device sizes must be multiple of chunk-size
Date: Tue, 28 Mar 2006 14:15:54 +0200 [thread overview]
Message-ID: <20060328121554.GC3218@redhat.com> (raw)
In-Reply-To: <e3538fbd0603222128o525b4608h84b4004fc4ca0a61@mail.gmail.com>
Joseph,
can you send me the tar-archive of your metadata
dmraid -rD
tar jcvf isw-Joseph_Yasi-raid0.tar.bz2 *.{dat,size,offset)
for reference, please.
Heinz
On Wed, Mar 22, 2006 at 11:28:22PM -0600, Joseph Yasi wrote:
> Hello,
>
> I am using the dmraid utility to detect and configure my Intel
> Software Raid RAID0 array. When upgrading to 2.6.16 from 2.6.15, the
> system failed to boot because the device-mapper array was not built.
> I have traced the problem to this patch that limits dm-stripe to
> targets that are multiples of the chunk size. I don't know whether to
> consider this a problem with device-mapper or with the Intel Software
> Raid BIOS that built the array. Dmraid is giving me a target of
> 980460038 blocks with a chunk size of 256 blocks. Is this a problem
> with device-mapper, the dmraid utility or the raid bios? Should
> device-mapper handle striped targets that are not multiples of the
> chunk size?
>
> Thank You,
> Joe Yasi
>
> dmesg gives these pertinent lines:
> device-mapper: dm-stripe: Target length not divisible by chunk size.
> device-mapper: error adding target to table.
>
> dmsetup status
> isw_caejhbcidd_Volume03: 0 976173660 linear
> isw_caejhbcidd_Volume02: 0 4209030 linear
> isw_caejhbcidd_Volume01: 0 64197 linear
> isw_caejhbcidd_Volume0: 0 980460038 striped
>
> dmraid -s
> *** Group superset isw_caejhbcidd
> --> Active Subset
> name : isw_caejhbcidd_Volume0
> size : 980460038
> stride : 256
> type : stripe
> status : ok
> subsets: 0
> devs : 2
> spares : 0
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat GmbH
Consulting Development Engineer Am Sonnenhang 11
Storage Development 56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com PHONE +49 171 7803392
FAX +49 2626 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2006-03-28 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 5:28 [PATCH] dm-striped device sizes must be multiple of chunk-size Joseph Yasi
2006-03-25 4:46 ` Kevin Corry
2006-03-26 0:01 ` Dwaine Garden
2006-03-28 14:06 ` Heinz Mauelshagen
2006-03-28 12:08 ` Heinz Mauelshagen
2006-03-29 13:48 ` Heinz Mauelshagen
2006-03-28 12:15 ` Heinz Mauelshagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-30 13:14 Peyrotau Yannick
2006-06-01 10:18 ` Dwaine Garden
2006-05-31 16:17 Peyrotau Yannick
2006-05-31 23:28 ` 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=20060328121554.GC3218@redhat.com \
--to=mauelshagen@redhat.com \
--cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.