[Bug 651846] Re: raid10 fails - "lost page write due to I/O error on md4" and " raid10_make_request bug: can't convert block across chunks or bigger than 128k 1623343324 20" - write fails, remote nfs mount of filesystem becomes unusable
Andrew Hately
651846 at bugs.launchpad.net
Fri Oct 1 14:03:21 UTC 2010
Thanks for the follow up - as I mentioned in the follow up, I have made the
problem go away by using the default chunk size for raid10.
As this is my main file server I don't really want to recreate the problem.
If I get a spare afternoon I'll perhaps try to recreate the bug on a less
critical machine. (I now have a pile of 400GB discs that came out for the
file server)
regards
Andrew
On Fri, Oct 1, 2010 at 12:31 PM, Jeremy Foshee
<651846 at bugs.launchpad.net>wrote:
> Hi Andrew,
>
> If you could also please test the latest upstream kernel available that
> would be great. It will allow additional upstream developers to examine the
> issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once
> you've tested the upstream kernel, please remove the
> 'needs-upstream-testing' tag. This can be done by clicking on the yellow
> pencil icon next to the tag located at the bottom of the bug description and
> deleting the 'needs-upstream-testing' text. Please let us know your
> results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> raid10 fails - "lost page write due to I/O error on md4" and "
> raid10_make_request bug: can't convert block across chunks or bigger than
> 128k 1623343324 20" - write fails, remote nfs mount of filesystem becomes
> unusable
> https://bugs.launchpad.net/bugs/651846
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: linux-image-2.6.32-25-preempt
>
> Asus p5q premium intel motherboard has 6 identical discs on the ICH10
> controller, configured mostly as a raid10 array, with an xfs filesystem
> mounted on /home and exported via nfs.
> Errors are consistently seen writing large files (e.g. iso images) onto the
> exported filesystem. Errors are logged on the remote machine as write
> failures. On the server there are a very large number of messages of the
> form
> Sep 28 15:55:58 wibert kernel: [ 2351.356243] lost page write due to I/O
> error on md4
> Sep 28 15:55:58 wibert kernel: [ 2351.356409] lost page write due to I/O
> error on md4
> Sep 28 15:55:58 wibert kernel: [ 2351.356536] lost page write due to I/O
> error on md4
> Sep 28 15:55:58 wibert kernel: [ 2351.358103] raid10_make_request bug:
> can't convert block across chunks or bigger than 128k 1623343324 20
> Sep 28 15:55:58 wibert kernel: [ 2351.358148] raid10_make_request bug:
> can't convert block across chunks or bigger than 128k 1803715220 56
> Sep 28 15:55:58 wibert kernel: [ 2351.359568] raid10_make_request bug:
> can't convert block across chunks or bigger than 128k 3427057892 16
>
> key facts from nfs client machine:
> # mount | grep home
> wibert:/home on /home type nfs
> (rw,hard,rsize=1048576,wsize=1048576,nfsvers=3,retrans=5,addr=192.168.2.5)
> # uname -a
> Linux hudson 2.6.32-24-preempt #43-Ubuntu SMP PREEMPT Thu Sep 16 17:13:25
> UTC 2010 x86_64 GNU/Linux
>
> more important stuff from fileserver:
> # uname -a
> Linux wibert 2.6.32-25-preempt #44-Ubuntu SMP PREEMPT Fri Sep 17 22:21:55
> UTC 2010 x86_64 GNU/Linux
>
> # cat /proc/mdstat
> Personalities : [linear] [multipath] [raid1] [raid0] [raid6] [raid5]
> [raid4] [raid10]
> md5 : active raid5 sdh1[0] sdg1[1] sdi1[3]
> 3907022848 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3]
> [UUU]
> bitmap: 2/466 pages [8KB], 2048KB chunk
>
> md1 : active raid1 sdf1[1] sde1[0]
> 14651136 blocks [2/2] [UU]
>
> md3 : active raid1 sde2[1] sdj2[3](S) sdf2[2] sdd2[0]
> 128448 blocks [3/3] [UUU]
>
> md2 : active raid1 sdd1[1] sdc1[0]
> 14651136 blocks [2/2] [UU]
>
> md4 : active raid10 sdf3[5] sdj3[6](S) sde3[4] sdc3[2] sdd3[3] sdb3[1]
> sda3[0]
> 2885940480 blocks 128K chunks 2 far-copies [6/6] [UUUUUU]
>
> md0 : active raid1 sdb1[1] sda1[0]
> 14647232 blocks [2/2] [UU]
>
> unused devices: <none>
>
>
> # mdadm --detail /dev/md4
> /dev/md4:
> Version : 00.90
> Creation Time : Tue Sep 28 14:34:19 2010
> Raid Level : raid10
> Array Size : 2885940480 (2752.25 GiB 2955.20 GB)
> Used Dev Size : 961980160 (917.42 GiB 985.07 GB)
> Raid Devices : 6
> Total Devices : 7
> Preferred Minor : 4
> Persistence : Superblock is persistent
>
> Update Time : Thu Sep 30 09:35:57 2010
> State : clean
> Active Devices : 6
> Working Devices : 7
> Failed Devices : 0
> Spare Devices : 1
>
> Layout : near=1, far=2
> Chunk Size : 128K
>
> UUID : e71d7eb2:102854c4:fcc517c0:fe041f9d (local to host wibert)
> Events : 0.858
>
> Number Major Minor RaidDevice State
> 0 8 3 0 active sync /dev/sda3
> 1 8 19 1 active sync /dev/sdb3
> 2 8 35 2 active sync /dev/sdc3
> 3 8 51 3 active sync /dev/sdd3
> 4 8 67 4 active sync /dev/sde3
> 5 8 83 5 active sync /dev/sdf3
>
> 6 8 147 - spare /dev/sdj3
>
>
>
> when the /home filesystem was made, this command was used:
> # mkfs.xfs -f -b size=2048 -d su=131072,sw=6 -l logdev=/dev/md3,sunit=4 -L
> home /dev/md4
> meta-data=/dev/md4 isize=256 agcount=32, agsize=45092864
> blks
> = sectsz=512 attr=2
> data = bsize=2048 blocks=1442970240, imaxpct=5
> = sunit=64 swidth=384 blks
> naming =version 2 bsize=4096 ascii-ci=0
> log =/dev/md3 bsize=2048 blocks=64224, version=2
> = sectsz=512 sunit=1 blks, lazy-count=1
> realtime =none extsz=4096 blocks=0, rtextents=0
>
>
>
> fyi, md3 is like this and the discs are partitioned as follows:
> # mdadm --detail /dev/md3
> /dev/md3:
> Version : 00.90
> Creation Time : Tue Sep 28 14:11:29 2010
> Raid Level : raid1
> Array Size : 128448 (125.46 MiB 131.53 MB)
> Used Dev Size : 128448 (125.46 MiB 131.53 MB)
> Raid Devices : 3
> Total Devices : 4
> Preferred Minor : 3
> Persistence : Superblock is persistent
>
> Update Time : Thu Sep 30 09:38:14 2010
> State : clean
> Active Devices : 3
> Working Devices : 4
> Failed Devices : 0
> Spare Devices : 1
>
> UUID : 00e0158b:1a9cb809:fcc517c0:fe041f9d (local to host wibert)
> Events : 0.32
>
> Number Major Minor RaidDevice State
> 0 8 50 0 active sync /dev/sdd2
> 1 8 66 1 active sync /dev/sde2
> 2 8 82 2 active sync /dev/sdf2
>
> 3 8 146 - spare /dev/sdj2
>
>
> # fdisk -l
>
> Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000d1143
>
> Device Boot Start End Blocks Id System
> /dev/sda1 1 1824 14647296 fd Linux raid
> autodetect
> /dev/sda2 1824 1840 131480 82 Linux swap /
> Solaris
> /dev/sda3 1841 121601 961980232+ fd Linux raid
> autodetect
>
> Disk /dev/md0: 15.0 GB, 14998765568 bytes
> 2 heads, 4 sectors/track, 3661808 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
>
> Disk /dev/md0 doesn't contain a valid partition table
>
> Disk /dev/md4: 2955.2 GB, 2955203051520 bytes
> 2 heads, 4 sectors/track, 721485120 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 131072 bytes / 786432 bytes
> Disk identifier: 0x00000000
>
> Disk /dev/md4 doesn't contain a valid partition table
>
> Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000ed82e
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 * 1 1824 14647296 fd Linux raid
> autodetect
> /dev/sdb2 1824 1840 131480 82 Linux swap /
> Solaris
> /dev/sdb3 1841 121601 961980232+ fd Linux raid
> autodetect
>
> Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x0002e53b
>
> Device Boot Start End Blocks Id System
> /dev/sdc1 1 1824 14651248+ fd Linux raid
> autodetect
> /dev/sdc2 1825 1840 128520 82 Linux swap /
> Solaris
> /dev/sdc3 1841 121601 961980232+ fd Linux raid
> autodetect
>
> Disk /dev/md2: 15.0 GB, 15002763264 bytes
> 2 heads, 4 sectors/track, 3662784 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
>
> Disk /dev/md2 doesn't contain a valid partition table
>
> Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x0006f1c7
>
> Device Boot Start End Blocks Id System
> /dev/sdd1 1 1824 14651248+ fd Linux raid
> autodetect
> /dev/sdd2 1825 1840 128520 fd Linux raid
> autodetect
> /dev/sdd3 1841 121601 961980232+ fd Linux raid
> autodetect
>
> Disk /dev/md3: 131 MB, 131530752 bytes
> 2 heads, 4 sectors/track, 32112 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x3a243a01
>
> Disk /dev/md3 doesn't contain a valid partition table
>
> Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000afe47
>
> Device Boot Start End Blocks Id System
> /dev/sde1 1 1824 14651248+ fd Linux raid
> autodetect
> /dev/sde2 1825 1840 128520 fd Linux raid
> autodetect
> /dev/sde3 1841 121601 961980232+ fd Linux raid
> autodetect
>
> Disk /dev/md1: 15.0 GB, 15002763264 bytes
> 2 heads, 4 sectors/track, 3662784 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
>
> Disk /dev/md1 doesn't contain a valid partition table
>
> Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes
> 255 heads, 63 sectors/track, 243201 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x0009993b
>
> Device Boot Start End Blocks Id System
> /dev/sdg1 1 243201 1953512001 fd Linux raid
> autodetect
>
> Disk /dev/sdf: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000f0c1e
>
> Device Boot Start End Blocks Id System
> /dev/sdf1 1 1824 14651248+ fd Linux raid
> autodetect
> /dev/sdf2 1825 1840 128520 fd Linux raid
> autodetect
> /dev/sdf3 1841 121601 961980232+ fd Linux raid
> autodetect
>
> Disk /dev/sdh: 2000.4 GB, 2000398934016 bytes
> 255 heads, 63 sectors/track, 243201 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000ca1dd
>
> Device Boot Start End Blocks Id System
> /dev/sdh1 1 243201 1953512001 fd Linux raid
> autodetect
>
> Disk /dev/sdj: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000340b6
>
> Device Boot Start End Blocks Id System
> /dev/sdj1 1 1824 14651248+ fd Linux raid
> autodetect
> /dev/sdj2 1825 1840 128520 fd Linux raid
> autodetect
> /dev/sdj3 1841 121601 961980232+ fd Linux raid
> autodetect
>
> Disk /dev/sdi: 2000.4 GB, 2000398934016 bytes
> 255 heads, 63 sectors/track, 243201 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x000475b4
>
> Device Boot Start End Blocks Id System
> /dev/sdi1 1 243201 1953512001 fd Linux raid
> autodetect
>
> Disk /dev/sdk: 32.0 GB, 31991533568 bytes
> 255 heads, 63 sectors/track, 3889 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x23720cbd
>
> Device Boot Start End Blocks Id System
> /dev/sdk1 1 3889 31238361 7 HPFS/NTFS
>
> Disk /dev/md5: 4000.8 GB, 4000791396352 bytes
> 2 heads, 4 sectors/track, 976755712 cylinders
> Units = cylinders of 8 * 512 = 4096 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
> Disk identifier: 0x00000000
>
> Disk /dev/md5 doesn't contain a valid partition table
>
> some info about the discs:
> # dmesg | grep -i ata
> [ 0.000000] BIOS-e820: 00000000cff70000 - 00000000cff7e000 (ACPI data)
> [ 0.000000] modified: 00000000cff70000 - 00000000cff7e000 (ACPI data)
> [ 0.000000] NODE_DATA [0000000000015000 - 0000000000019fff]
> [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==>
> [0000000000 - 0000001000]
> [ 0.000000] #2 [0001000000 - 0001a46a64] TEXT DATA BSS ==>
> [0001000000 - 0001a46a64]
> [ 0.000000] Memory: 4048256k/4980736k available (5565k kernel code,
> 787472k absent, 145008k reserved, 2980k data, 828k init)
> [ 0.308970] libata version 3.00 loaded.
> [ 0.346643] pata_acpi 0000:03:00.0: PCI INT A -> GSI 16 (level, low) ->
> IRQ 16
> [ 0.346710] pata_acpi 0000:03:00.0: setting latency timer to 64
> [ 0.346721] pata_acpi 0000:03:00.0: PCI INT A disabled
> [ 0.346771] pata_acpi 0000:02:00.1: enabling device (0000 -> 0001)
> [ 0.346818] pata_acpi 0000:02:00.1: PCI INT B -> GSI 18 (level, low) ->
> IRQ 18
> [ 0.346880] pata_acpi 0000:02:00.1: setting latency timer to 64
> [ 0.346889] pata_acpi 0000:02:00.1: PCI INT B disabled
> [ 0.395998] Write protecting the kernel read-only data: 7844k
> [ 0.428971] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps
> 0x3f impl SATA mode
> [ 0.430999] pata_jmicron 0000:02:00.1: PCI INT B -> GSI 18 (level, low)
> -> IRQ 18
> [ 0.431093] pata_jmicron 0000:02:00.1: setting latency timer to 64
> [ 0.437041] scsi0 : pata_jmicron
> [ 0.445409] scsi1 : pata_jmicron
> [ 0.445494] ata1: PATA max UDMA/100 cmd 0x9c00 ctl 0x9880 bmdma 0x9400
> irq 18
> [ 0.445536] ata2: PATA max UDMA/100 cmd 0x9800 ctl 0x9480 bmdma 0x9408
> irq 18
> [ 0.452776] ata3: SATA max UDMA/133 abar m2048 at 0xf9ffe800 port
> 0xf9ffe900 irq 34
> [ 0.452825] ata4: SATA max UDMA/133 abar m2048 at 0xf9ffe800 port
> 0xf9ffe980 irq 34
> [ 0.452874] ata5: SATA max UDMA/133 abar m2048 at 0xf9ffe800 port
> 0xf9ffea00 irq 34
> [ 0.452923] ata6: SATA max UDMA/133 abar m2048 at 0xf9ffe800 port
> 0xf9ffea80 irq 34
> [ 0.452971] ata7: SATA max UDMA/133 abar m2048 at 0xf9ffe800 port
> 0xf9ffeb00 irq 34
> [ 0.453022] ata8: SATA max UDMA/133 abar m2048 at 0xf9ffe800 port
> 0xf9ffeb80 irq 34
> [ 0.453345] ahci 0000:03:00.0: Disabling your PATA port. Use the boot
> option 'ahci.marvell_enable=0' to avoid this.
> [ 0.453973] ata9: SATA max UDMA/133 abar m1024 at 0xfe6ffc00 port
> 0xfe6ffd00 irq 16
> [ 0.454025] ata10: SATA max UDMA/133 abar m1024 at 0xfe6ffc00 port
> 0xfe6ffd80 irq 16
> [ 0.454076] ata11: DUMMY
> [ 0.465505] ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps
> 0x3 impl SATA mode
> [ 0.465958] ata12: SATA max UDMA/133 abar m8192 at 0xfe5fe000 port
> 0xfe5fe100 irq 17
> [ 0.466021] ata13: SATA max UDMA/133 abar m8192 at 0xfe5fe000 port
> 0xfe5fe180 irq 17
> [ 0.604039] ata1.00: ATAPI: HL-DT-ST DVDRAM GSA-H42N, RL00, max UDMA/66
> [ 0.610237] ata1.00: configured for UDMA/66
> [ 0.763424] ata9: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 0.767484] ata9.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133
> [ 0.767526] ata9.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32)
> [ 0.772494] ata9.00: configured for UDMA/133
> [ 0.918532] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 0.924225] ata3.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
> [ 0.924273] ata3.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth
> 31/32), AA
> [ 0.930005] ata3.00: configured for UDMA/133
> [ 0.931169] ata12: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 0.931229] ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 0.934757] ata12.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max
> UDMA/133
> [ 0.934799] ata12.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth
> 31/32), AA
> [ 0.936927] ata13.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
> [ 0.936968] ata13.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth
> 31/32), AA
> [ 0.939343] ata12.00: configured for UDMA/133
> [ 0.941438] scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD103SJ
> 1AJ1 PQ: 0 ANSI: 5
> [ 0.942761] ata13.00: configured for UDMA/133
> [ 1.808091] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 1.813780] ata4.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
> [ 1.813837] ata4.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth
> 31/32), AA
> [ 1.819583] ata4.00: configured for UDMA/133
> [ 1.830145] scsi 3:0:0:0: Direct-Access ATA SAMSUNG HD103SJ
> 1AJ1 PQ: 0 ANSI: 5
> [ 2.706055] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 2.711744] ata5.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
> [ 2.711786] ata5.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth
> 31/32), AA
> [ 2.717550] ata5.00: configured for UDMA/133
> [ 2.728093] scsi 4:0:0:0: Direct-Access ATA SAMSUNG HD103SJ
> 1AJ1 PQ: 0 ANSI: 5
> [ 3.604048] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 3.609741] ata6.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
> [ 3.609785] ata6.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth
> 31/32), AA
> [ 3.615554] ata6.00: configured for UDMA/133
> [ 3.626105] scsi 5:0:0:0: Direct-Access ATA SAMSUNG HD103SJ
> 1AJ1 PQ: 0 ANSI: 5
> [ 4.502033] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 4.507723] ata7.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
> [ 4.508449] ata7.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth
> 31/32), AA
> [ 4.514191] ata7.00: configured for UDMA/133
> [ 4.525100] scsi 6:0:0:0: Direct-Access ATA SAMSUNG HD103SJ
> 1AJ1 PQ: 0 ANSI: 5
> [ 5.402036] ata8: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 5.407737] ata8.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
> [ 5.407781] ata8.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth
> 31/32), AA
> [ 5.413563] ata8.00: configured for UDMA/133
> [ 5.424102] scsi 7:0:0:0: Direct-Access ATA SAMSUNG HD103SJ
> 1AJ1 PQ: 0 ANSI: 5
> [ 5.424463] scsi 8:0:0:0: Direct-Access ATA WDC WD20EARS-00M
> 51.0 PQ: 0 ANSI: 5
> [ 5.729043] ata10: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 5.732326] ata10.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max
> UDMA/133
> [ 5.732369] ata10.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth
> 0/32)
> [ 5.736338] ata10.00: configured for UDMA/133
> [ 5.736457] scsi 9:0:0:0: Direct-Access ATA WDC WD20EARS-00M
> 51.0 PQ: 0 ANSI: 5
> [ 5.736835] scsi 11:0:0:0: Direct-Access ATA WDC WD20EARS-00M
> 50.0 PQ: 0 ANSI: 5
> [ 5.737116] scsi 12:0:0:0: Direct-Access ATA SAMSUNG HD103SJ
> 1AJ1 PQ: 0 ANSI: 5
> [ 5.794695] scsi 13:0:0:0: Direct-Access Kingston DataTraveler 2.0
> 1.00 PQ: 0 ANSI: 2
> [ 6.312516] EXT4-fs (md0): mounted filesystem with ordered data mode
> [ 10.327322] EXT4-fs (md2): mounted filesystem with ordered data mode
> [ 10.422953] EXT4-fs (md1): mounted filesystem with ordered data mode
>
>
> all discs are less than a couple of months old.
>
> The controllers used are:
> sda-sdf on the on board intel controller
> sdg-sdh on the on board marvel running with sata_mv
> sdi-sdj and a pata dvd drive on a pcie jb-micron card
>
> more on the bloody weird (but totally unrelated to this problem) marvell
> controller:
>
> root at wibert:~# cat /etc/modules
> # /etc/modules: kernel modules to load at boot time.
> #
> # This file contains the names of kernel modules that should be loaded
> # at boot time, one per line. Lines beginning with "#" are ignored.
>
> loop
> lp
> rtc
> sata_mv
> #sata_mv here and pata_marvell in /etc/modprobe.d/blacklist.conf
> #see also /etc/default/grub where ahci is enabled
> #
> http://old.nabble.com/How-to-get-a-Marvell-88SE6145-%28and-probably-6121%29-sata-controller%09working-on-new-kernels-td20079927.html
> root at wibert:~# cat /etc/default/grub
> # If you change this file, run 'update-grub' afterwards to update
> # /boot/grub/grub.cfg.
>
> GRUB_DEFAULT=0
> #GRUB_HIDDEN_TIMEOUT=0
> #GRUB_HIDDEN_TIMEOUT_QUIET=true
> GRUB_TIMEOUT=10
> GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
> #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
> GRUB_CMDLINE_LINUX_DEFAULT="ahci.marvell_enable=1"
> GRUB_CMDLINE_LINUX=""
>
> # Uncomment to disable graphical terminal (grub-pc only)
> #GRUB_TERMINAL=console
>
> # The resolution used on graphical terminal
> # note that you can use only modes which your graphic card supports via VBE
> # you can see them in real GRUB with the command `vbeinfo'
> #GRUB_GFXMODE=640x480
>
> # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to
> Linux
> #GRUB_DISABLE_LINUX_UUID=true
>
> # Uncomment to disable generation of recovery mode menu entries
> #GRUB_DISABLE_LINUX_RECOVERY="true"
>
> # Uncomment to get a beep at grub start
> #GRUB_INIT_TUNE="480 440 1"
> root at wibert:~# tail /etc/modprobe.d/blacklist.conf
> blacklist pcspkr
>
> # EDAC driver for amd76x clashes with the agp driver preventing the
> aperture
> # from being initialised (Ubuntu: #297750). Blacklist so that the driver
> # continues to build and is installable for the few cases where its
> # really needed.
> blacklist amd76x_edac
>
> #testing here 5th sept 10
> pata_marvell
>
> - the marvell has 4 sata connectors but only two work.
>
>
> oh, and here are the mounts:
> root at wibert:~# mount
> /dev/md0 on / type ext4 (rw,errors=remount-ro)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> none on /sys type sysfs (rw,noexec,nosuid,nodev)
> none on /sys/fs/fuse/connections type fusectl (rw)
> none on /sys/kernel/debug type debugfs (rw)
> none on /sys/kernel/security type securityfs (rw)
> none on /dev type devtmpfs (rw,mode=0755)
> none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
> none on /dev/shm type tmpfs (rw,nosuid,nodev)
> none on /var/run type tmpfs (rw,nosuid,mode=0755)
> none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
> none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
> rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
> /dev/md2 on /tmp type ext4 (rw,errors=remount-ro)
> /dev/md1 on /media/md1 type ext4 (rw)
> /dev/md5 on /space/big type xfs (rw)
> /dev/md4 on /home type xfs (rw,logdev=/dev/md3)
> nfsd on /proc/fs/nfsd type nfsd (rw)
> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc
> (rw,noexec,nosuid,nodev)
> root at wibert:~# cat /etc/fstab
> # /etc/fstab: static file system information.
> #
> # Use 'blkid -o value -s UUID' to print the universally unique identifier
> # for a device; this may be used with UUID= as a more robust way to name
> # devices that works even if disks are added and removed. See fstab(5).
> #
> # <file system> <mount point> <type> <options> <dump> <pass>
> proc /proc proc nodev,noexec,nosuid 0 0
> # / was on /dev/md0 during installation
> UUID=d941bbb8-c51c-43d6-90a9-07daa5ee54c9 / ext4
> errors=remount-ro 0 1
>
> # /tmp on /dev/md2
> UUID=30ad351e-ee7f-4761-aefe-dae470619373 /tmp ext4
> errors=remount-ro 0 1
>
> # /home on md4 with md3 as log device
> UUID=2cbb2fa7-5594-45e2-b19d-e15e7f17356c /home xfs
> defaults,logdev=/dev/md3 0 2
>
> # /space big on md5
> UUID=ba5fa67c-503d-4eec-81b9-149055297b7d /space/big xfs defaults
> 0 2
>
> # /mdedia/md1 on md1
> UUID=497ff0c4-85ba-40fa-a397-b2519c1b8437 /media/md1 ext4 defaults
> 0 2
>
> # three little swaps on sda2 sdb2 sdc2
> UUID=4f333c83-8c41-46d2-8022-97a89117462d none swap sw
> 0 0
> UUID=a9f5b013-25af-4283-a6b8-778ad1b6b8a7 none swap sw
> 0 0
> UUID=e47ceab5-518a-4884-a55d-790f8de9f5e4 none swap sw
> 0 0
>
>
> is that enough info?
> There was a bunch of guff on the redhat website about this
> "raid10_make_request bug: can't convert block across chunks or bigger than"
> problem but it was a lot of hand waving and deciding not to fix the problem.
> It seems it has been around for ages. What's interesting is I had a smaller
> raid10 setup before with n2, err, parity and never saw an issue. This is my
> first try with f2. But lots of other things have changes too so I can't
> isolate this as the key factor.
> Bon chance.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: linux-image-2.6.32-25-preempt 2.6.32-25.44
> Regression: No
> Reproducible: Yes
> ProcVersionSignature: Ubuntu 2.6.32-25.44-preempt 2.6.32.21+drm33.7
> Uname: Linux 2.6.32-25-preempt x86_64
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
> Architecture: amd64
> AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
> '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0',
> '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c',
> '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2',
> '/dev/sequencer'] failed with exit code 1:
> CRDA: Error: [Errno 2] No such file or directory
> Card0.Amixer.info:
> Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 22'
> Mixer name : 'Analog Devices AD1989B'
> Components : 'HDA:11d4989b,10438311,00100300'
> Controls : 47
> Simple ctrls : 26
> Date: Thu Sep 30 09:20:46 2010
> IwConfig: Error: [Errno 2] No such file or directory
> MachineType: System manufacturer System Product Name
> ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-25-preempt
> root=UUID=d941bbb8-c51c-43d6-90a9-07daa5ee54c9 ro ahci.marvell_enable=1
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> RelatedPackageVersions: linux-firmware 1.34.1
> RfKill: Error: [Errno 2] No such file or directory
> SourcePackage: linux
> dmi.bios.date: 02/25/2009
> dmi.bios.vendor: American Megatrends Inc.
> dmi.bios.version: 2001
> dmi.board.asset.tag: To Be Filled By O.E.M.
> dmi.board.name: P5Q Premium
> dmi.board.vendor: ASUSTeK Computer INC.
> dmi.board.version: Rev 1.xx
> dmi.chassis.asset.tag: Asset-1234567890
> dmi.chassis.type: 3
> dmi.chassis.vendor: Chassis Manufacture
> dmi.chassis.version: Chassis Version
> dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr2001:bd02/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPremium:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
> dmi.product.name: System Product Name
> dmi.product.version: System Version
> dmi.sys.vendor: System manufacturer
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/651846/+subscribe
>
--
raid10 fails - "lost page write due to I/O error on md4" and " raid10_make_request bug: can't convert block across chunks or bigger than 128k 1623343324 20" - write fails, remote nfs mount of filesystem becomes unusable
https://bugs.launchpad.net/bugs/651846
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.
More information about the kernel-bugs
mailing list