All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: Hadders <dmraid@workingwithit.com>
Cc: device-mapper development <dm-devel@redhat.com>, mauelshagen@redhat.com
Subject: Re: newbie:  Target Length not divisble error
Date: Wed, 20 Dec 2006 11:34:34 +0100	[thread overview]
Message-ID: <20061220103434.GA27708@redhat.com> (raw)
In-Reply-To: <45809C1D.5010201@workingwithit.com>

On Thu, Dec 14, 2006 at 08:34:37AM +0800, Hadders wrote:
> Hi Heinz,
>   Someone in the ata.raid group suggested I manually tweak the stride 
> size and update my mkinitrd as there was a problem with a version in its 
> nash and parted.
> I've done that and it has worked!
> 
> Original:  1250275846
> 1250275846/(2*256) = 2441945.01171875
> They said, make an even multiple so take 2441945*512= 1250275840
> 
> dm create isw_cdgbeijgjh_iaa 0 1250275846 striped 2 256 8:0 8:16 0
> with
> dm create isw_cdgbeijgjh_iaa 0 1250275840 striped 2 256 8:0 8:16 0
> 
> So I did that. It didn't work, but then they said there was the mkinitrd 
> issue. So I updated mkinitrd, rebuilt the initrd, added the raid stuff 
> back in and voila!

Good :)

> 
> Of course, this is still only a work around.  Would this calculation 
> work for any RAID container stride errors like this one?

Yes, I think so.

Heinz

> 
> Regards. Hadders
> 
> 
> Heinz Mauelshagen wrote:
> >Hrm, dmraid-1.0.0.rc11 has the stride size fix in,
> >which *should* prevent that kernel message to occur.
> >
> >Can you send me your metadata created with "dmraid -rD" 
> >for analysis, please ?
> >
> >Pack the *.{dat,size,offset} files into isw-Hadders-raid0.tar.bz2
> >before sending.
> >
> >Regards,
> >Heinz    -- The LVM Guy --
> >
> >On Tue, Dec 12, 2006 at 10:21:11PM +0800, Hadders wrote:
> >  
> >>Hi all,
> >> I'm new to trying to get my Intel SATA RAID 0 container working.  I 
> >>want to use the "hardware" mode as oppossed to software RAID so I can 
> >>share it with my Windows setups.
> >>I've just spent the last three days banging my head against a brick wall.
> >>In short, I'm using FC5 and am looking to get the latest kernel, 
> >>2.6.18-1.2239.fc5smp working with this container.  I don't understand 
> >>why it doesn't, the base FC5 kernel does.
> >>I've just got my SATAII disks and setup the container in the Intel BIOS. 
> >>I've installed FC5 from scratch and used anaconda to setup the partitions.
> >>When I reboot into my new kernel, I get an error when it tries to 
> >>activate the container,  that is
> >>
> >>device-mapper: table: 253:0 striped: Target length not divisble by chunk 
> >>size
> >>
> >>then I get growled at for using parted and not knowing what I'm doing. I 
> >>didn't! honest, I used anaconda.
> >>the lines for setting up the container in the init file of the initrd are
> >>rmparts sdb
> >>rmparts sda
> >>dm create isw_cdgbeijgjh_iaa 0 1250275846 striped 2 256 8:0 8:16 0
> >>dm partadd isw_cdgbeijgjh_iaa
> >>
> >>Here's the details of my setup that I can access under 2.6.15-1.2054 
> >>(base FC5) kernel
> >>
> >>dmraid -V
> >>dmraid version:        1.0.0.rc11 (2006.05.15) debug
> >>dmraid library version:    1.0.0.rc11 (2006.05.15)
> >>device-mapper version:    4.5.0
> >>
> >>dmraid -rD
> >>/dev/sda: isw, "isw_cdgbeijgjh", GROUP, ok, 625142446 sectors, data@ 0
> >>/dev/sdb: isw, "isw_cdgbeijgjh", GROUP, ok, 625142446 sectors, data@ 0
> >>
> >>dmraid -s -g
> >>*** Superset
> >>name   : isw_cdgbeijgjh
> >>size   : 1250284892
> >>stride : 0
> >>type   : GROUP
> >>status : ok
> >>subsets: 1
> >>devs   : 2
> >>spares : 0
> >>--> Active Subset
> >>name   : isw_cdgbeijgjh_iaa
> >>size   : 1250275840
> >>stride : 256
> >>type   : stripe
> >>status : ok
> >>subsets: 0
> >>devs   : 2
> >>spares : 0
> >>
> >>dmsetup status
> >>isw_cdgbeijgjh_iaap6: 0 4498137 linear
> >>isw_cdgbeijgjh_iaap5: 0 204796557 linear
> >>isw_cdgbeijgjh_iaa: 0 1250275846 striped
> >>isw_cdgbeijgjh_iaap4: 0 1044947925 linear
> >>isw_cdgbeijgjh_iaap3: 0 102398310 linear
> >>isw_cdgbeijgjh_iaap2: 0 102398310 linear
> >>isw_cdgbeijgjh_iaap1: 0 530082 linear
> >>
> >>I think the 18-1 kernel uses device-mapper v4.7
> >>
> >>However, I'm lost as to what to do now. Help! Please!
> >>
> >>Thanks in advance. Hadley
> >>
> >>--
> >>dm-devel mailing list
> >>dm-devel@redhat.com
> >>https://www.redhat.com/mailman/listinfo/dm-devel
> >>    
> >
> >*** Software bugs are stupid.
> >    Nevertheless it needs not so stupid people to solve them ***
> >
> >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> >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
> >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> >--
> >dm-devel mailing list
> >dm-devel@redhat.com
> >https://www.redhat.com/mailman/listinfo/dm-devel

      reply	other threads:[~2006-12-20 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 14:21 newbie: Target Length not divisble error Hadders
2006-12-12 13:43 ` Heinz Mauelshagen
2006-12-14  0:34   ` Hadders
2006-12-20 10:34     ` Heinz Mauelshagen [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=20061220103434.GA27708@redhat.com \
    --to=mauelshagen@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=dmraid@workingwithit.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.