From: David Brown <david@westcontrol.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
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: Mon, 02 May 2011 11:11:25 +0200 [thread overview]
Message-ID: <4DBE753D.20709@westcontrol.com> (raw)
In-Reply-To: <8739kyf53e.fsf@servo.factory.finestructure.net>
On 02/05/2011 00:06, Jameson Graef Rollins wrote:
> On Fri, 29 Apr 2011 05:39:40 +0100, Ben Hutchings<ben@decadent.org.uk> wrote:
>> On Wed, 2011-04-27 at 09:19 -0700, Jameson Graef Rollins wrote:
>>> I run what I imagine is a fairly unusual disk setup on my laptop,
>>> consisting of:
>>>
>>> ssd -> raid1 -> dm-crypt -> lvm -> ext4
>>>
>>> I use the raid1 as a backup. The raid1 operates normally in degraded
>>> mode. For backups I then hot-add a usb hdd, let the raid1 sync, and
>>> then fail/remove the external hdd.
This is not directly related to your issues here, but it is possible to
make a 1-disk raid1 set so that you are not normally degraded. When you
want to do the backup, you can grow the raid1 set with the usb disk,
want for the resync, then fail it and remove it, then "grow" the raid1
back to 1 disk. That way you don't feel you are always living in a
degraded state.
next prev parent reply other threads:[~2011-05-02 9:11 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
2011-05-02 9:05 ` David Brown
2011-05-02 9:11 ` David Brown [this message]
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=4DBE753D.20709@westcontrol.com \
--to=david@westcontrol.com \
--cc=624343@bugs.debian.org \
--cc=ben@decadent.org.uk \
--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 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).