make_request bug: can't convert block across chunks or bigger than 512k 2554601336 124

[Brian J. Murrell]

I have a couple of RAID arrays with the following configuration:

/dev/md1:
        Version : 1.2
  Creation Time : Sat Dec 26 19:49:41 2015
     Raid Level : raid0
     Array Size : 1953524736 (1863.03 GiB 2000.41 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

    Update Time : Sat Dec 26 19:49:41 2015
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

     Chunk Size : 512K

           Name : linux.interlinx.bc.ca:1 (local to host linux.interlinx.bc.ca)
           UUID : f27ae74d:e2997e50:9df158ee:c5ed3cbb
         Events : 0

    Number Major Minor RaidDevice State
       0 8 16 0 active sync /dev/sdb
       1 8 32 1 active sync /dev/sdc

/dev/md0:
        Version : 0.90
  Creation Time : Mon Jan 26 19:51:38 2009
     Raid Level : raid1
     Array Size : 1953514496 (1863.02 GiB 2000.40 GB)
  Used Dev Size : 1953514496 (1863.02 GiB 2000.40 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0
    Persistence : Superblock is persistent

    Update Time : Fri Apr 8 00:00:42 2016
          State : active, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0

           UUID : 2f8fc5e0:a0eb646a:2303d005:33f25f21
         Events : 0.5031387

    Number Major Minor RaidDevice State
       0 8 48 0 active sync /dev/sdd
       1 0 0 1 removed

       2 9 1 - faulty spare /dev/md1

This configuration has worked for a number of years but has all of a sudden started breaking with:

[37722.335880] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2554601336 124
[37722.335887] md/raid1:md0: md1: rescheduling sector 2554601336
[37722.376776] md/raid1:md0: redirecting sector 2554601336 to other mirror: md1
[37722.386455] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2554601336 124
[37722.386461] md/raid1:md0: md1: rescheduling sector 2554601336
[37722.412059] md/raid1:md0: redirecting sector 2554601336 to other mirror: sdd
[37722.735049] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2554608496 124
[37722.735056] md/raid1:md0: md1: rescheduling sector 2554608496
[37722.789926] md/raid1:md0: redirecting sector 2554608496 to other mirror: md1
[37722.798689] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2554608496 124
[37722.798696] md/raid1:md0: md1: rescheduling sector 2554608496
[37722.859314] md/raid1:md0: redirecting sector 2554608496 to other mirror: sdd
[37724.819090] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2554606584 12
[37724.819096] md/raid1:md0: md1: rescheduling sector 2554606584
[37727.455279] md/raid1:md0: redirecting sector 2554606584 to other mirror: sdd
[37752.406865] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 1748150224 124
[37752.521219] md/raid1:md0: Disk failure on md1, disabling device.
[37752.521222] md/raid1:md0: Operation continuing on 1 devices.
[37752.580186] RAID1 conf printout:
[37752.580190] --- wd:1 rd:2
[37752.580194] disk 0, wo:0, o:1, dev:sdd
[37752.580197] disk 1, wo:1, o:0, dev:md1
[37752.580199] RAID1 conf printout:
[37752.580201] --- wd:1 rd:2
[37752.580203] disk 0, wo:0, o:1, dev:sdd
[37752.580228] BUG: unable to handle kernel paging request at 000000001dff2107
[37752.584011] IP: [<ffffffffa001909a>] close_write+0x6a/0xa0 [raid1]
[37752.584011] PGD 20f667067 PUD 20f669067 PMD 0
[37752.584011] Oops: 0000 [#1] SMP
[37752.584011] CPU 0
[37752.584011] Modules linked in: iptable_mangle iptable_filter ipt_MASQUERADE xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables autofs4 nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm radeon snd_seq_midi ttm drm_kms_helper snd_rawmidi ftdi_sio snd_seq_midi_event snd_seq snd_timer drm ppdev snd_seq_device pl2303 usbserial serio_raw i2c_algo_bit mac_hid asus_atk0110 snd parport_pc parport soundcore snd_page_alloc edac_core edac_mce_amd i2c_piix4 k8temp shpchp 8021q garp stp pata_atiixp r8169 raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 multipath linear
[37752.584011]
[37752.584011] Pid: 267, comm: md0_raid1 Not tainted 3.2.0-101-generic #141-Ubuntu System manufacturer System Product Name/M2A-VM
[37752.584011] RIP: 0010:[<ffffffffa001909a>] [<ffffffffa001909a>] close_write+0x6a/0xa0 [raid1]
[37752.584011] RSP: 0018:ffff88020def9dc0 EFLAGS: 00010246
[37752.584011] RAX: 000000001dff1dff RBX: ffff88020e380108 RCX: 00000000e8e08784
[37752.584011] RDX: 00000000687249a8 RSI: 0000000000000002 RDI: ffff88020e380108
[37752.584011] RBP: ffff88020def9dd0 R08: 00000000e8e08784 R09: 000000000000036b
[37752.584011] R10: dead000000100100 R11: dead000000200200 R12: ffff88020e36b800
[37752.584011] R13: ffff88020e380100 R14: ffff88020e380130 R15: ffff88020e380108
[37752.584011] FS: 00007f8e0a353740(0000) GS:ffff88021fc00000(0000) knlGS:00000000f75586c0
[37752.584011] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[37752.584011] CR2: 000000001dff2107 CR3: 000000020f61e000 CR4: 00000000000006f0
[37752.584011] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[37752.584011] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[37752.584011] Process md0_raid1 (pid: 267, threadinfo ffff88020def8000, task ffff88020e2eae00)
[37752.584011] Stack:
[37752.584011] ffff88020def9e20 ffff88020e36b800 ffff88020def9e60 ffffffffa001cbe5
[37752.584011] ffff88020e380140 ffff880044dbd800 0000000091827364 ffff88020def9df8
[37752.584011] ffff88020def9df8 ffff88020def9e08 ffff88020def9e08 ffff880200000000
[37752.584011] Call Trace:
[37752.584011] [<ffffffffa001cbe5>] raid1d+0x2a5/0x2b0 [raid1]
[37752.584011] [<ffffffff814f0f9e>] md_thread+0x11e/0x170
[37752.584011] [<ffffffff8108c650>] ? add_wait_queue+0x60/0x60
[37752.584011] [<ffffffff814f0e80>] ? md_rdev_init+0x130/0x130
[37752.584011] [<ffffffff8108bbac>] kthread+0x8c/0xa0
[37752.584011] [<ffffffff816746b4>] kernel_thread_helper+0x4/0x10
[37752.584011] [<ffffffff8108bb20>] ? flush_kthread_worker+0xa0/0xa0
[37752.584011] [<ffffffff816746b0>] ? gs_change+0x13/0x13
[37752.584011] Code: e4 48 8b 53 48 75 de 48 89 d7 e8 e2 cd 14 e1 48 c7 43 48 00 00 00 00 4c 8b 43 18 48 8b 43 20 48 8b 4b 18 48 63 53 10 48 8b 73 08 <48> 8b b8 08 03 00 00 49 c1 e8 03 48 c1 e9 02 41 83 e0 01 83 e1
[37752.584011] RIP [<ffffffffa001909a>] close_write+0x6a/0xa0 [raid1]
[37752.584011] RSP <ffff88020def9dc0>
[37752.584011] CR2: 000000001dff2107
[37752.889674] ---[ end trace 276f024e11aa62ac ]---

This being a broken array now makes this a rather dire and dangerous situation. Please advise ASAP.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-101-generic 3.2.0-101.141
ProcVersionSignature: Ubuntu 3.2.0-101.141-generic 3.2.76
Uname: Linux 3.2.0-101-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.13
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
BootDmesg: (Nothing has been logged yet.)
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Date: Mon Apr 11 08:17:39 2016
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lspci: Error: [Errno 2] No such file or directory
MachineType: System manufacturer System Product Name
MarkForUpload: True
PciMultimedia:

ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-101-generic root=/dev/mapper/rootvol-ubuntu_root ro console=ttyS0,115200 console=tty0
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-101-generic N/A
 linux-backports-modules-3.2.0-101-generic N/A
 linux-firmware 1.79.18
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/28/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 1705
dmi.board.name: M2A-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision1705:bd03/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.13
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
BootDmesg: (Nothing has been logged yet.)
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 12.04
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lspci: Error: [Errno 2] No such file or directory
MachineType: System manufacturer System Product Name
MarkForUpload: True
Package: linux 3.2.0.101.117
PackageArchitecture: amd64
PciMultimedia:

ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-101-generic root=/dev/mapper/rootvol-ubuntu_root ro console=ttyS0,115200 console=tty0
ProcVersionSignature: Ubuntu 3.2.0-101.141-generic 3.2.76
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-101-generic N/A
 linux-backports-modules-3.2.0-101-generic N/A
 linux-firmware 1.79.18
RfKill: Error: [Errno 2] No such file or directory
Tags: precise
Uname: Linux 3.2.0-101-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/28/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 1705
dmi.board.name: M2A-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision1705:bd03/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1568830

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

apport information

[Brian J. Murrell (brian-interlinx)]

FWIW, I did use "ubuntu-bug linux" to create this ticket and the report that was generated did contain all of the same things as the requested "apport-collect 1568830" but they didn't all get attached to this ticket. Seems like ubuntu-bug is a bit broken.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc4-wily/

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

[Brian J. Murrell (brian-interlinx)]

# dpkg -i linux-image-4.6.0-040600rc4-generic_4.6.0-040600rc4.201604172330_amd64.deb
(Reading database ... 84773 files and directories currently installed.)
Unpacking linux-image-4.6.0-040600rc4-generic (from .../linux-image-4.6.0-040600rc4-generic_4.6.0-040600rc4.201604172330_amd64.deb) ...
Done.
dpkg: dependency problems prevent configuration of linux-image-4.6.0-040600rc4-generic:
 linux-image-4.6.0-040600rc4-generic depends on kmod; however:
  Package kmod is not installed.
dpkg: error processing linux-image-4.6.0-040600rc4-generic (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 linux-image-4.6.0-040600rc4-generic
# apt-get install kmod
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package kmod is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

N: Ignoring 'bak' in directory '/etc/apt/sources.list.d/' as it is not a regular file
N: Ignoring 'bak' in directory '/etc/apt/sources.list.d/' as it is not a regular file
N: Ignoring 'bak' in directory '/etc/apt/sources.list.d/' as it is not a regular file
E: Package 'kmod' has no installation candidate

[Brian J. Murrell (brian-interlinx)]

I got past it with --ignore-depends=kmod. Array is rebuilding right now. We'll know in a couple of hours when the backups start whether the kernel complains again or not. I will update then.

[Brian J. Murrell (brian-interlinx)]

So now that I have determined that this problem is fixed in the newer/upstream kernel, what next?

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable 3.2 kernel next? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.80-precise/

[Brian J. Murrell (brian-interlinx)]

Nope.

# uname -r
3.2.80-030280-generic

[18455.876945] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 1102518240 124
[18455.876959] md/raid1:md0: md1: rescheduling sector 1102518240
[18455.935138] md/raid1:md0: redirecting sector 1102518240 to other mirror: md1
[18455.944050] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 1102518240 124
[18455.944063] md/raid1:md0: md1: rescheduling sector 1102518240
[18455.992380] md/raid1:md0: redirecting sector 1102518240 to other mirror: md1
[18456.000256] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 1102518240 124
[18456.000266] md/raid1:md0: md1: rescheduling sector 1102518240
[18456.030911] md/raid1:md0: redirecting sector 1102518240 to other mirror: md1
[18456.044779] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 1102518240 124
[18456.044792] md/raid1:md0: md1: rescheduling sector 1102518240
[18456.101348] md/raid1:md0: redirecting sector 1102518240 to other mirror: md1
[18456.109156] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 1102518240 124
[18456.109166] md/raid1:md0: md1: rescheduling sector 1102518240
[18456.164308] md/raid1:md0: redirecting sector 1102518240 to other mirror: md1
[18456.172701] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 1102518240 124
[18456.172712] md/raid1:md0: md1: rescheduling sector 1102518240
[18456.204711] md/raid1:md0: redirecting sector 1102518240 to other mirror: sdd
[18463.015510] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915353456 124
[18463.015551] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915354448 124
[18463.015664] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915355440 124
[18463.015696] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915356432 124
[18463.015779] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915357672 124
[18463.015813] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915358664 124
[18463.015859] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915337072 124
[18463.015891] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915338064 124
[18463.079725] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915339056 124
[18463.079787] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915340048 124
[18463.079813] md/raid1:md0: Disk failure on md1, disabling device.
[18463.079816] md/raid1:md0: Operation continuing on 1 devices.
[18463.167209] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915341072 124
[18463.167267] md/raid0:md1: make_request bug: can't convert block across chunks or bigger than 512k 2915359720 124
[18463.167344] md/raid0:md1: make_request bug: can't convert block ac...

[Joseph Salisbury (jsalisbury)]

I was hoping the fix was already cc'd to stable, but it appears to not have been from your test results.

We could perform a bisect to identify the commit that caused the regression. However, it's probably better to perform a "Reverse" bisect to identify the commit that fixes the bug. We first need to identify the last kernel version with the bug and the first kernel version without the bug.

Can you also test the following kernels:

4.0: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/
4.2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-wily/
4.4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/
4.6-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/

You don't have to test every kernel, just up until the first kernel that fixes the bug. We can then narrow it down further.

[Brian J. Murrell (brian-interlinx)]

> 4.0: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-vivid/

This kernel works

[Joseph Salisbury (jsalisbury)]

Thanks for testing. We probably need to go back a few more versions to find the last bad version and the first good one. Can you test the following kernels next:

3.4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/
3.8: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-raring/
3.13: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-trusty/

Again, you don't have to test every kernel, just up until the first kernel that fixes the bug. We can then narrow it down further.

[Brian J. Murrell (brian-interlinx)]

> 3.4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-quantal/

This one works.

I've got to say that it's really annoying that every time I reboot my system comes back with a degraded array:

# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active raid0 sdc[1] sdb[0]
      1953524736 blocks super 1.2 512k chunks

md0 : active raid1 sdd[0]
      1953514496 blocks [2/1] [U_]

unused devices: <none>

Before reboot it looked like this:

# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active raid0 sdb[0] sdc[1]
      1953524736 blocks super 1.2 512k chunks

md0 : active raid1 md1[1] sdd[0]
      1953514496 blocks [2/2] [UU]

unused devices: <none>

[Joseph Salisbury (jsalisbury)]

Can you test the v3.3 kernel next? If it does not have the bug, we will have to perform a regular bisect against the 3.2 kernel to find what commit introduced the bug. It may be a commit was introduced to 3.2 stable that was not added to any other kernel versions.

The 3.3 kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/