From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Ben Hutchings <ben@decadent.org.uk>,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: 624343@bugs.debian.org, NeilBrown <neilb@suse.de>,
linux-raid@vger.kernel.org
Subject: Re: Bug#624343: linux-image-2.6.38-2-amd64: frequent message "bio too big device md0 (248 > 240)" in kern.log
Date: Sun, 01 May 2011 18:17:06 -0700 [thread overview]
Message-ID: <87pqo1ewa5.fsf@servo.factory.finestructure.net> (raw)
In-Reply-To: <1304298258.2833.125.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
On Mon, 02 May 2011 02:04:18 +0100, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Sun, 2011-05-01 at 20:42 -0400, Daniel Kahn Gillmor wrote:
> So far as I'm aware, the RAID may stop working, but without loss of data
> that's already on disk.
What exactly does "RAID may stop working mean"? Do you mean that this
bug will be triggered? The raid will refuse to do further syncs? Or do
you mean something else?
> > How is an admin to know which I/O capabilities to check before adding a
> > device to a RAID array? When is it acceptable to mix I/O capabilities?
> > Can a RAID array which is not currently being used as a backing store
> > for a filesystem be assembled of unlike disks? What if it is then
> > (later) used as a backing store for a filesystem?
> [...]
>
> I think the answers are:
> - Not easily
> - When the RAID does not have another device on top
This is very upsetting to me, if it's true. It completely undermines
all of my assumptions about how software raid works.
Are you really saying that md with mixed disks is not possible/supported
when the md device has *any* other device on top of it? This is a in
fact a *very* common setup. *ALL* of my raid devices have other devices
on top of them (lvm at least). In fact, the debian installer supports
putting dm and/or lvm on top of md on mixed disks. If what you're
saying is true then the debian installer is in big trouble.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-05-02 1:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110427161901.27049.31001.reportbug@servo.factory.finestructure.net>
2011-04-29 4:39 ` Bug#624343: linux-image-2.6.38-2-amd64: frequent message "bio too big device md0 (248 > 240)" in kern.log Ben Hutchings
2011-05-01 22:06 ` Jameson Graef Rollins
2011-05-02 0:00 ` Ben Hutchings
2011-05-02 0:22 ` NeilBrown
2011-05-02 2:47 ` Guy Watkins
2011-05-02 5:07 ` Daniel Kahn Gillmor
2011-05-02 9:08 ` David Brown
2011-05-02 10:00 ` NeilBrown
2011-05-02 10:32 ` David Brown
2011-05-02 14:56 ` David Brown
2011-05-02 0:42 ` Daniel Kahn Gillmor
2011-05-02 1:04 ` Ben Hutchings
2011-05-02 1:17 ` Jameson Graef Rollins [this message]
2011-05-02 9:05 ` David Brown
2011-05-02 9:11 ` David Brown
2011-05-02 16:38 ` Jameson Graef Rollins
2011-05-02 18:54 ` David Brown
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=87pqo1ewa5.fsf@servo.factory.finestructure.net \
--to=jrollins@finestructure.net \
--cc=624343@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=dkg@fifthhorseman.net \
--cc=linux-raid@vger.kernel.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 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.