linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Marti Raudsepp <marti@juffo.org>
Cc: "\"Ing. Daniel Rozsnyó\"" <daniel@rozsnyo.com>,
	linux-kernel@vger.kernel.org, "Neil Brown" <neilb@suse.de>
Subject: Re: bio too big - in nested raid setup
Date: Mon, 25 Jan 2010 19:27:53 +0100	[thread overview]
Message-ID: <4B5DE2A9.4030500@redhat.com> (raw)
In-Reply-To: <5ec358371001250725l40b13060md880001c96be165f@mail.gmail.com>

On 01/25/2010 04:25 PM, Marti Raudsepp wrote:
> 2010/1/24 "Ing. Daniel Rozsnyó" <daniel@rozsnyo.com>:
>> Hello,
>>  I am having troubles with nested RAID - when one array is added to the
>> other, the "bio too big device md0" messages are appearing:
>>
>> bio too big device md0 (144 > 8)
>> bio too big device md0 (248 > 8)
>> bio too big device md0 (32 > 8)
> 
> I *think* this is the same bug that I hit years ago when mixing
> different disks and 'pvmove'
> 
> It's a design flaw in the DM/MD frameworks; see comment #3 from Milan Broz:
> http://bugzilla.kernel.org/show_bug.cgi?id=9401#c3

Hm. I don't think it is the same problem, you are only adding device to md array...
(adding cc: Neil, this seems to me like MD bug).

(original report for reference is here http://lkml.org/lkml/2010/1/24/60 )

Milan
--
mbroz@redhat.com

  reply	other threads:[~2010-01-25 18:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 18:49 bio too big - in nested raid setup "Ing. Daniel Rozsnyó"
2010-01-25 15:25 ` Marti Raudsepp
2010-01-25 18:27   ` Milan Broz [this message]
2010-01-28  2:28     ` Neil Brown
2010-01-28  9:24       ` "Ing. Daniel Rozsnyó"
2010-01-28 10:50         ` Neil Brown
2010-01-28 12:07           ` Boaz Harrosh
2010-01-28 22:14             ` Neil Brown
2010-01-31 15:42               ` Boaz Harrosh

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=4B5DE2A9.4030500@redhat.com \
    --to=mbroz@redhat.com \
    --cc=daniel@rozsnyo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marti@juffo.org \
    --cc=neilb@suse.de \
    /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).