| 2009-01-23 20:52:44 |
Stephan Diestelhorst |
bug |
|
|
added bug |
| 2009-01-23 20:53:47 |
Stephan Diestelhorst |
bug |
|
|
added attachment 'uname-a.log' (uname-a.log) |
| 2009-01-23 20:54:25 |
Stephan Diestelhorst |
bug |
|
|
added attachment 'version.log' (version.log) |
| 2009-01-23 20:55:23 |
Stephan Diestelhorst |
bug |
|
|
added attachment 'lspci-vnvn.log' (lspci-vnvn.log) |
| 2009-01-23 20:55:55 |
Stephan Diestelhorst |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2009-01-23 20:58:43 |
Stephan Diestelhorst |
bug |
|
|
added attachment 'fdisk-lu_HDD' (fdisk -lu /dev/sda (the HDD)) |
| 2009-01-23 20:59:38 |
Stephan Diestelhorst |
bug |
|
|
added attachment 'fdisk-lu_SD' (fdisk -lu /dev/sdb (the SD card)) |
| 2009-01-24 15:23:28 |
Stephan Diestelhorst |
title |
Raid1 HDD and SD card -> bio too big device md0 (248 > 200) |
Raid1 HDD and SD card -> data corruption (bio too big device md0 (248 > 200)) |
|
| 2009-06-02 17:41:34 |
Andy Whitcroft |
affects |
linux-meta (Ubuntu) |
linux (Ubuntu) |
|
| 2009-06-02 17:41:34 |
Andy Whitcroft |
linux (Ubuntu): importance |
Undecided |
Critical |
|
| 2009-06-02 17:44:30 |
Leann Ogasawara |
linux (Ubuntu): status |
New |
Triaged |
|
| 2009-07-06 18:15:10 |
Jim Lieb |
linux (Ubuntu): assignee |
|
Jim Lieb (jim-lieb) |
|
| 2009-07-24 20:07:11 |
Jim Lieb |
linux (Ubuntu): status |
Triaged |
Won't Fix |
|
| 2013-01-05 20:36:43 |
ceg |
bug task added |
|
mdadm (Ubuntu) |
|
| 2013-01-05 20:37:28 |
ceg |
bug task added |
|
debian-installer (Ubuntu) |
|
| 2013-01-05 20:39:32 |
ceg |
bug task added |
|
ubiquity (Ubuntu) |
|
| 2013-01-05 20:41:11 |
ceg |
description |
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
Note: Bug is also present when hot-plugging USB, Firewire etc. devices.
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
|
| 2013-01-05 20:43:28 |
ceg |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624343 |
|
| 2013-01-05 20:43:28 |
ceg |
bug task added |
|
linux |
|
| 2013-01-05 20:50:08 |
ceg |
summary |
Raid1 HDD and SD card -> data corruption (bio too big device md0 (248 > 200)) |
hot-add/remove in mixed HDD/USB/SD-card RAIDs -> data corruption (bio too big device md0 (248 > 200)) |
|
| 2013-01-05 20:50:40 |
ceg |
summary |
hot-add/remove in mixed HDD/USB/SD-card RAIDs -> data corruption (bio too big device md0 (248 > 200)) |
hot-add/remove in mixed (HDD/USB/SD-card/...) RAIDs -> data corruption (bio too big device md0 (248 > 200)) |
|
| 2013-01-05 20:51:31 |
ceg |
debian-installer (Ubuntu): status |
New |
Confirmed |
|
| 2013-01-05 21:00:20 |
ceg |
mdadm (Ubuntu): status |
New |
Confirmed |
|
| 2013-01-05 21:13:27 |
ceg |
summary |
hot-add/remove in mixed (HDD/USB/SD-card/...) RAIDs -> data corruption (bio too big device md0 (248 > 200)) |
hot-add/remove in mixed (HDD/USB/SD-card/...) RAIDs with device mapper on top -> data corruption (bio too big device md0 (248 > 200)) |
|
| 2013-01-05 21:23:04 |
Bug Watch Updater |
linux: status |
Unknown |
Confirmed |
|
| 2013-01-06 03:25:47 |
ceg |
description |
Note: Bug is also present when hot-plugging USB, Firewire etc. devices.
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
Note: Bug is also present when hot-plugging USB, Firewire etc. devices.
Also reproducable in much more common usage as originally reported (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices).
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
|
| 2013-01-06 03:28:01 |
ceg |
summary |
hot-add/remove in mixed (HDD/USB/SD-card/...) RAIDs with device mapper on top -> data corruption (bio too big device md0 (248 > 200)) |
hot-add/remove in mixed (HDD/USB/SD-card/...) RAIDs with device mapper on top => data corruption (bio too big device md0 (248 > 240)) |
|
| 2013-01-06 03:28:53 |
ceg |
summary |
hot-add/remove in mixed (HDD/USB/SD-card/...) RAIDs with device mapper on top => data corruption (bio too big device md0 (248 > 240)) |
hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device mapper on top => data corruption (bio too big device md0 (248 > 240)) |
|
| 2013-01-06 11:11:26 |
ceg |
description |
Note: Bug is also present when hot-plugging USB, Firewire etc. devices.
Also reproducable in much more common usage as originally reported (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices).
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
Problem: md changes max_sector setting of an already running and busy md device, when a (hotplugable) device is added or removed. However, the a device mapper and filesystem layer on top of the raid can not (always?) cope with that.
Observations:
* "bio too big device mdX (248 > 240)" messages in the syslog
* read/write errors (some dropped silently, no noticable errors reported during operation, until things like dhcpclient looses its IP etc.)
Expected:
Adding and removing members to running raids (hotplugging) does not change the raid device characteristics. If the new member supports only smaller max_sector values, buffer and split the data steam, until the raid device can be set up from a clean state with a more appropriate max_sector value. To avoid buffering and splitting in the future, md could save the smallest max_sector value of the known members in the superblock, and use that when setting up the raid even if that member is not present.
Note: This is reproducible in much more common scenarios as the original reporter had (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices).
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
|
| 2013-01-06 11:11:50 |
ceg |
description |
Problem: md changes max_sector setting of an already running and busy md device, when a (hotplugable) device is added or removed. However, the a device mapper and filesystem layer on top of the raid can not (always?) cope with that.
Observations:
* "bio too big device mdX (248 > 240)" messages in the syslog
* read/write errors (some dropped silently, no noticable errors reported during operation, until things like dhcpclient looses its IP etc.)
Expected:
Adding and removing members to running raids (hotplugging) does not change the raid device characteristics. If the new member supports only smaller max_sector values, buffer and split the data steam, until the raid device can be set up from a clean state with a more appropriate max_sector value. To avoid buffering and splitting in the future, md could save the smallest max_sector value of the known members in the superblock, and use that when setting up the raid even if that member is not present.
Note: This is reproducible in much more common scenarios as the original reporter had (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices).
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
Problem: md changes max_sector setting of an already running and busy md device, when a (hotplugable) device is added or removed. However, the device mapper and filesystem layer on top of the raid can not (always?) cope with that.
Observations:
* "bio too big device mdX (248 > 240)" messages in the syslog
* read/write errors (some dropped silently, no noticable errors reported during operation, until things like dhcpclient looses its IP etc.)
Expected:
Adding and removing members to running raids (hotplugging) does not change the raid device characteristics. If the new member supports only smaller max_sector values, buffer and split the data steam, until the raid device can be set up from a clean state with a more appropriate max_sector value. To avoid buffering and splitting in the future, md could save the smallest max_sector value of the known members in the superblock, and use that when setting up the raid even if that member is not present.
Note: This is reproducible in much more common scenarios as the original reporter had (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices).
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
|
| 2013-01-06 11:12:16 |
ceg |
description |
Problem: md changes max_sector setting of an already running and busy md device, when a (hotplugable) device is added or removed. However, the device mapper and filesystem layer on top of the raid can not (always?) cope with that.
Observations:
* "bio too big device mdX (248 > 240)" messages in the syslog
* read/write errors (some dropped silently, no noticable errors reported during operation, until things like dhcpclient looses its IP etc.)
Expected:
Adding and removing members to running raids (hotplugging) does not change the raid device characteristics. If the new member supports only smaller max_sector values, buffer and split the data steam, until the raid device can be set up from a clean state with a more appropriate max_sector value. To avoid buffering and splitting in the future, md could save the smallest max_sector value of the known members in the superblock, and use that when setting up the raid even if that member is not present.
Note: This is reproducible in much more common scenarios as the original reporter had (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices).
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
Problem: md changes max_sector setting of an already running and busy md device, when a (hotplugable) device is added or removed. However, the device mapper and filesystem layer on top of the raid can not (always?) cope with that.
Observations:
* "bio too big device mdX (248 > 240)" messages in the syslog
* read/write errors (some dropped silently, no noticable errors reported during operation, until things like dhcpclient looses its IP etc.)
Expected:
Adding and removing members to running raids (hotplugging) should not change the raid device characteristics. If the new member supports only smaller max_sector values, buffer and split the data steam, until the raid device can be set up from a clean state with a more appropriate max_sector value. To avoid buffering and splitting in the future, md could save the smallest max_sector value of the known members in the superblock, and use that when setting up the raid even if that member is not present.
Note: This is reproducible in much more common scenarios as the original reporter had (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices).
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
|
| 2013-01-06 11:22:50 |
ceg |
bug task added |
|
mdadm |
|
| 2013-01-06 11:23:04 |
ceg |
mdadm: status |
New |
Confirmed |
|
| 2013-02-11 00:48:25 |
Dimitri John Ledkov |
debian-installer (Ubuntu): status |
Confirmed |
Invalid |
|
| 2013-02-11 00:48:36 |
Dimitri John Ledkov |
ubiquity (Ubuntu): status |
New |
Invalid |
|
| 2013-04-07 09:13:34 |
ceg |
description |
Problem: md changes max_sector setting of an already running and busy md device, when a (hotplugable) device is added or removed. However, the device mapper and filesystem layer on top of the raid can not (always?) cope with that.
Observations:
* "bio too big device mdX (248 > 240)" messages in the syslog
* read/write errors (some dropped silently, no noticable errors reported during operation, until things like dhcpclient looses its IP etc.)
Expected:
Adding and removing members to running raids (hotplugging) should not change the raid device characteristics. If the new member supports only smaller max_sector values, buffer and split the data steam, until the raid device can be set up from a clean state with a more appropriate max_sector value. To avoid buffering and splitting in the future, md could save the smallest max_sector value of the known members in the superblock, and use that when setting up the raid even if that member is not present.
Note: This is reproducible in much more common scenarios as the original reporter had (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices).
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
Problem: md changes max_sector setting of an already running and busy md device, when a (hotplugable) device is added or removed. However, the device mapper and filesystem layer on top of the raid can not (always?) cope with that.
Observations:
* "bio too big device mdX (248 > 240)" messages in the syslog
* read/write errors (some dropped silently, no noticable errors reported during operation, until things like dhcpclient looses its IP etc.)
Expected:
Adding and removing members to running raids (hotplugging) should not change the raid device characteristics. If the new member supports only smaller max_sector values, buffer and split the data steam, until the raid device can be set up from a clean state with a more appropriate max_sector value. To avoid buffering and splitting in the future, md could save the smallest max_sector value of the known members in the superblock, and use that when setting up the raid even if that member is not present.
Note: This is reproducible in much more common scenarios as the original reporter had (e.g. --add a USB (3.0 these days) drive to an already running SATA raid1 and grow the number of devices).
Fix:
Upsteam has no formal bug tracking, but a mailing list. The response was that finally this needs to be "fixed [outside of mdadm] by cleaning up the bio path so that big bios are split by the device that needs the split, not be the fs sending the bio."
However, in the meantime mdadm needs to saveguard against the date corruption:
> > [The mdadm] fix is to reject the added device [if] its limits are
> > too low.
>
> Good Idea to avoid the data corruption. MD could save the
> max_sectors default limit for arrays. If the array is modified and the new
> limit gets smaller, postpone the sync until the next assembe/restart.
>
> And of course print a message if postponing, that explains when --force would be save.
> What ever that would be: no block device abstraction layer (device mapper, lvm, luks,...)
> between an unmounted? ext, fat?, ...? filesystem and md?
As upsteam does not do public bug tracking, the status and rememberence of this need remains unsure though.
---
This is on a MSI Wind U100 and I've got the following stack running:
HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser
Whenever I remove the HDD from the Raid1
> mdadm /dev/md0 --fail /dev/sda2
> mdadm /dev/md0 --remove /dev/sda2)
for powersaving reasons, I cannot run any apt related tools.
> sudo apt-get update
[...]
Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
Reading package lists... Error!
E: Read error - read (5 Input/output error)
E: The package lists or status file could not be parsed or opened.
Taking a look at the kernel log shows (and many more above):
> dmesg|tail
[ 9479.330550] bio too big device md0 (248 > 240)
[ 9479.331375] bio too big device md0 (248 > 240)
[ 9479.332182] bio too big device md0 (248 > 240)
[ 9611.980294] bio too big device md0 (248 > 240)
[ 9742.929761] bio too big device md0 (248 > 240)
[ 9852.932001] bio too big device md0 (248 > 240)
[ 9852.935395] bio too big device md0 (248 > 240)
[ 9852.938064] bio too big device md0 (248 > 240)
[ 9853.081046] bio too big device md0 (248 > 240)
[ 9853.081688] bio too big device md0 (248 > 240)
$ sudo mdadm --detail /dev/md0
/dev/md0:
Version : 00.90
Creation Time : Tue Jan 13 11:25:57 2009
Raid Level : raid1
Array Size : 3871552 (3.69 GiB 3.96 GB)
Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Fri Jan 23 21:47:35 2009
State : active, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
Events : 0.8767
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 17 1 active sync writemostly /dev/sdb1
$ sudo ubuntu-bug -p linux-meta
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
dpkg-query: failed in buffer_read(fd): copy info file `/var/lib/dpkg/status': Input/output error
[...]
Will provide separate attachements. |
|
| 2013-07-15 19:29:31 |
Bug Watch Updater |
linux: status |
Confirmed |
Fix Released |
|
| 2014-09-04 06:39:14 |
Bug Watch Updater |
linux: status |
Fix Released |
Confirmed |
|
| 2015-02-05 05:26:24 |
xor |
bug |
|
|
added subscriber xor |
| 2015-02-23 05:17:15 |
Jim Paris |
bug |
|
|
added subscriber Jim Paris |
| 2016-01-20 17:11:12 |
Bug Watch Updater |
linux: status |
Confirmed |
Fix Released |
|
