Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-02 Thread David Brown
On 02/05/2011 00:06, Jameson Graef Rollins wrote: On Fri, 29 Apr 2011 05:39:40 +0100, Ben Hutchingsb...@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 -

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-02 Thread Jameson Graef Rollins
On Mon, 02 May 2011 11:11:25 +0200, David Brown da...@westcontrol.com wrote: 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,

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-02 Thread David Brown
On 02/05/11 18:38, Jameson Graef Rollins wrote: On Mon, 02 May 2011 11:11:25 +0200, David Brownda...@westcontrol.com wrote: 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,

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-01 Thread Jameson Graef Rollins
On Fri, 29 Apr 2011 05:39:40 +0100, Ben Hutchings b...@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

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-01 Thread Ben Hutchings
On Sun, 2011-05-01 at 15:06 -0700, Jameson Graef Rollins wrote: On Fri, 29 Apr 2011 05:39:40 +0100, Ben Hutchings b...@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:

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-01 Thread NeilBrown
On Mon, 02 May 2011 01:00:57 +0100 Ben Hutchings b...@decadent.org.uk wrote: On Sun, 2011-05-01 at 15:06 -0700, Jameson Graef Rollins wrote: On Fri, 29 Apr 2011 05:39:40 +0100, Ben Hutchings b...@decadent.org.uk wrote: On Wed, 2011-04-27 at 09:19 -0700, Jameson Graef Rollins wrote: I

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-01 Thread Daniel Kahn Gillmor
On 05/01/2011 08:00 PM, Ben Hutchings wrote: On Sun, 2011-05-01 at 15:06 -0700, Jameson Graef Rollins wrote: Hi, Ben. Can you explain why this is not expected to work? Which part exactly is not expected to work and why? Adding another type of disk controller (USB storage versus whatever

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-01 Thread Ben Hutchings
On Sun, 2011-05-01 at 20:42 -0400, Daniel Kahn Gillmor wrote: On 05/01/2011 08:00 PM, Ben Hutchings wrote: On Sun, 2011-05-01 at 15:06 -0700, Jameson Graef Rollins wrote: Hi, Ben. Can you explain why this is not expected to work? Which part exactly is not expected to work and why?

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-01 Thread Jameson Graef Rollins
On Mon, 02 May 2011 02:04:18 +0100, Ben Hutchings b...@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

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-01 Thread Guy Watkins
#624343: linux-image-2.6.38-2-amd64: frequent message bio } too big device md0 (248 240) in kern.log } } On Mon, 02 May 2011 01:00:57 +0100 Ben Hutchings b...@decadent.org.uk } wrote: } } On Sun, 2011-05-01 at 15:06 -0700, Jameson Graef Rollins wrote: } On Fri, 29 Apr 2011 05:39:40 +0100, Ben

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-05-01 Thread Daniel Kahn Gillmor
On 05/01/2011 08:22 PM, NeilBrown wrote: However if there is another layer in between md and the filesystem - such as dm - then there can be problem. There is no mechanism in the kernl for md to tell dm that things have changed, so dm never changes its configuration to match any change in the

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-04-28 Thread Ben Hutchings
On Wed, 2011-04-27 at 09:19 -0700, Jameson Graef Rollins wrote: Package: linux-2.6 Version: 2.6.38-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As you can see from the kern.log snippet below, I am seeing frequent messages reporting bio too big device md0 (248

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-04-27 Thread Jameson Graef Rollins
Package: linux-2.6 Version: 2.6.38-3 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As you can see from the kern.log snippet below, I am seeing frequent messages reporting bio too big device md0 (248 240). I run what I imagine is a fairly unusual disk setup on my laptop,

Bug#624343: linux-image-2.6.38-2-amd64: frequent message bio too big device md0 (248 240) in kern.log

2011-04-27 Thread Jameson Graef Rollins
I am starting to suspect that these messages are in face associated with data loss on my system. I have witnessed these messages occur during write operations to the disk, and I have also started to see some strange behavior on my system. dhclient started acting weird after these messages