Bug 163469 - "bio too big device md1" vith data corruption
"bio too big device md1" vith data corruption
Status: CLOSED DUPLICATE of bug 163470
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
4
All Linux
medium Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-17 15:33 EDT by Frode Tennebø
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-17 15:38:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Frode Tennebø 2005-07-17 15:33:11 EDT
Description of problem:

I have the following setup I want to realise:

/dev/md1 (raid1) ---|-- /dev/sdd1 (36.7G)
                    |-- /dev/md0 (raid0) --|-- /dev/sda1 (18.3G)
                                           |-- /dev/sdc1 (18.3G)

On top of md1 I have LVM. I hot added /dev/md0 and during the process I got:

Jul 17 00:38:07 leia kernel: md: bind<md0>
Jul 17 00:38:07 leia kernel: RAID1 conf printout:
Jul 17 00:38:07 leia kernel:  --- wd:1 rd:2
Jul 17 00:38:07 leia kernel:  disk 0, wo:0, o:1, dev:sdd1
Jul 17 00:38:07 leia kernel:  disk 1, wo:1, o:1, dev:md0
Jul 17 00:38:07 leia kernel: ..<6>md: syncing RAID array md1
Jul 17 00:38:07 leia kernel: md: minimum _guaranteed_ reconstruction speed: 1000 
KB/sec/disc.
Jul 17 00:38:07 leia kernel: md: using maximum available idle IO bandwith (but 
not more than 200000 KB/sec) for reconstruction.
Jul 17 00:38:07 leia kernel: md: using 128k window, over a total of 35842944 
blocks.
Jul 17 00:41:56 leia kernel: bio too big device md1 (56 > 8)
Jul 17 00:41:56 leia kernel: bio too big device md1 (32 > 8)
Jul 17 00:41:56 leia kernel: bio too big device md1 (136 > 8)
Jul 17 00:41:56 leia kernel: bio too big device md1 (64 > 8)
Jul 17 00:41:56 leia kernel: bio too big device md1 (224 > 8)
Jul 17 00:41:56 leia kernel: bio too big device md1 (216 > 8)
Jul 17 00:41:56 leia kernel: bio too big device md1 (144 > 8)
Jul 17 00:41:56 leia kernel: bio too big device md1 (32 > 8)
Jul 17 00:41:56 leia kernel: bio too big device md1 (96 > 8)
Jul 17 00:45:00 leia kernel: bio too big device md1 (64 > 8)
Jul 17 00:45:00 leia kernel: bio too big device md1 (184 > 8)
:
:
Jul 17 02:30:36 leia kernel: bio too big device md1 (56 > 8)
Jul 17 02:31:11 leia kernel: bio too big device md1 (48 > 8)
Jul 17 02:35:00 leia kernel: bio too big device md1 (16 > 8)
Jul 17 02:36:21 leia kernel: bio too big device md1 (32 > 8)
Jul 17 02:38:27 leia kernel: md: md1: sync done.
Jul 17 02:38:27 leia kernel: RAID1 conf printout:
Jul 17 02:38:27 leia kernel:  --- wd:2 rd:2
Jul 17 02:38:27 leia kernel:  disk 0, wo:0, o:1, dev:sdd1
Jul 17 02:38:27 leia kernel:  disk 1, wo:0, o:1, dev:md0
Jul 17 02:39:08 leia kernel: bio too big device md1 (64 > 8)
Jul 17 02:39:08 leia kernel: bio too big device md1 (16 > 8)
Jul 17 02:39:08 leia kernel: bio too big device md1 (144 > 8)
Jul 17 02:39:08 leia kernel: bio too big device md1 (16 > 8)
:
:

Now, if I install new software to the drive I also get:

Jul 17 18:27:54 leia kernel: bio too big device md1 (64 > 8)
Jul 17 18:27:54 leia kernel: bio too big device md1 (32 > 8)
Jul 17 18:27:54 leia kernel: bio too big device md1 (96 > 8)
Jul 17 18:27:54 leia kernel: bio too big device md1 (248 > 8)
Jul 17 18:27:57 leia last message repeated 30 times
:

This files appear normal:

[ft@leia bin]$ date
Sun Jul 17 18:29:13 CEST 2005
[ft@leia bin]$ ls -l opera
-rwxr-xr-x  1 ft ft 5143 Jul 17 18:28 opera
[ft@leia bin]$ file opera
opera: Bourne shell script text executable
[ft@leia bin]$ head -4 opera
#!/bin/sh

# Location of the Opera binaries
OPERA_BINARYDIR=/opt/opera/8.02p1/lib/opera/8.02-20050705.1


However, after some time:

[ft@leia bin]$ date
Sun Jul 17 21:29:27 CEST 2005
[ft@leia bin]$ ls -l opera
-rwxr-xr-x  1 ft ft 5143 Jul 17 19:43 opera
[ft@leia bin]$ file opera
opera: data
[ft@leia bin]$ head -4 opera
@charset "UTF-8";
/*
Name: Disable tables
Version: 1.01


Version-Release number of selected component (if applicable):

[root@leia iptables]# mdadm -V
mdadm - v1.11.0 - 11 April 2005

[root@leia iptables]# uname -a
Linux leia 2.6.12-prep #1 Sat Jul 16 07:35:19 CEST 2005 i686 i686 i386 GNU/Linux
(It's kernel-2.6.12-1.1398_FC4, but I had to add the EATA driver which is 
missing)

[root@leia iptables]# lvm.static version
  LVM version:     2.01.08 (2005-03-22)
  Library version: 1.01.01 (2005-03-29)
  Driver version:  4.4.0


How reproducible:
This has happened all three times I have tried hot adding /dev/md0. The first 
two times were with kernel-2.6.10-1.760_FC3 (but with the EATA driver enabled). 

Steps to Reproduce:
(from memory)
1. fdisk /dev/sdd .....
2. mdadm --create /dev/md1 --level=1 --raid-devices=2 /dev/sdd1 missing
3. pvcreate /dev/md1
4. vgcreate vg1 /dev/md1
5. lvcreate -L9G -nopt vg1
6. mount /dev/vg1/opt /opt
7. rsync -a /mnt/tmp /opt #(a backup is kept here)
8. umount /mnt/tmp
9. fdisk /dev/sd[ac] ....
10. mdadm --create /dev/md0 --level=0 --radi-device=2 /dev/sda1 /dev/sdc1
11. mdadm /dev/md1 -a /dev/md0

At this point it appears that te raid itself, ie. that data already residing on 
md1 before hot-adding md0, is intact, ie. no data corruption on the existing 
data even though I get tons of "bio too big").

12. install a tar-file or eg. 
    dd if=/dev/zero of=./test bs=65536 count=1000

produces an equal amount of "bio too big".


Actual results:

Expected results:

Additional info:

[root@leia iptables]# cat /proc/mdstat
Personalities : [raid0] [raid1]
md1 : active raid1 md0[1] sdd1[0]
      35842944 blocks [2/2] [UU]

md0 : active raid0 sdc1[1] sda1[0]
      35872896 blocks 8k chunks

unused devices: <none>

[root@leia iptables]# more /etc/mdadm.conf
DEVICE /dev/sd[acd]1
ARRAY /dev/md0 level=0 devices=/dev/sda1,/dev/sdc1

DEVICE /dev/md0
ARRAY /dev/md1 level=1 devices=/dev/sdd1,/dev/md0

MAILADDR ft
PROGRAM 96 bytes

[root@leia linux]# fdisk -l /dev/sd[acd] /dev/md[01]

Disk /dev/sda: 18.3 GB, 18373205504 bytes
255 heads, 63 sectors/track, 2233 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        2233    17936541   fd  Linux raid autodetect

Disk /dev/sdc: 18.3 GB, 18373205504 bytes
255 heads, 63 sectors/track, 2233 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1        2233    17936541   fd  Linux raid autodetect

Disk /dev/sdd: 36.7 GB, 36703933952 bytes
64 heads, 32 sectors/track, 35003 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1       35003    35843056   fd  Linux raid autodetect

Disk /dev/md0: 36.7 GB, 36733845504 bytes
2 heads, 4 sectors/track, 8968224 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md1: 36.7 GB, 36703174656 bytes
2 heads, 4 sectors/track, 8960736 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md1 doesn't contain a valid partition table
Comment 1 Frode Tennebø 2005-07-17 15:38:52 EDT

*** This bug has been marked as a duplicate of 163470 ***

Note You need to log in before you can comment on or make changes to this bug.