Bug#618463: mdadm: Mdadm grow of Raid1 destroys metadata
Michael Gebetsroither
michael at mgeb.org
Tue Mar 15 11:45:19 UTC 2011
Package: mdadm
Version: 2.6.7.2-3
Severity: grave
Justification: causes non-serious data loss
Hi,
mdadm --grow /dev/mdX --size=max shreded the second raid1 array here.
Commands where as following:
lvextend -L +10G vda/opt
lvextend -L +10G vdb/opt
mdadm --grow /dev/md2 --size=max
All commands returned without errors, but the array didn't grow in
size.
After that the array was still running but the metadata destroyed.
# mdadm -D /dev/md2
/dev/md2:
Version : 00.90
Creation Time : Tue Jul 14 13:43:19 2009
Raid Level : raid1
Array Size : 10485696 (10.00 GiB 10.74 GB)
Used Dev Size : 10485696 (10.00 GiB 10.74 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Tue Mar 15 12:31:41 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Number Major Minor RaidDevice State
0 253 5 0 active sync /dev/dm-5
1 253 1 1 active sync /dev/dm-1
# mdadm -E /dev/vda/opt
mdadm: No md superblock detected on /dev/vda/opt.
# mdadm -E /dev/vdb/opt
mdadm: No md superblock detected on /dev/vdb/opt.
After mdadm --stop /dev/md2 the array couldn't be reassambled.
To fix this problem i simply recreated the array with:
# mdadm --create --assume-clean /dev/md2 -l1 -n2 /dev/vda/opt /dev/vdb/opt
mdadm: /dev/vda/opt appears to contain an ext2fs file system
size=10485696K mtime=Tue Feb 22 12:28:24 2011
mdadm: /dev/vdb/opt appears to contain an ext2fs file system
size=10485696K mtime=Tue Feb 22 12:28:24 2011
Continue creating array? yes
mdadm: array /dev/md2 started.
michael
-- Package-specific info:
--- mount output
/dev/md0 on / type auto (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
thalys.student.iaik.tugraz.at:/raid/users on /users type nfs (rw,nosuid,nodev,addr=129.27.142.141)
thalys.student.iaik.tugraz.at:/raid/vlsi_soft on /vlsi_soft type nfs (rw,nosuid,nodev,addr=129.27.142.141)
thalys.student.iaik.tugraz.at:/raid/verify on /verify type nfs (rw,nosuid,nodev,addr=129.27.142.141)
nfsd on /proc/fs/nfsd type nfsd (rw)
/dev/md1 on /workstore type ext3 (rw,nosuid,data=writeback)
/dev/mapper/vda-opt_backup on /root/opt_backup type ext3 (rw)
/dev/md2 on /opt type ext3 (rw,nosuid,nodev,noatime,data=writeback)
--- mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md0 level=raid1 num-devices=2 UUID=ee1de88e:0bf13d47:d8b78f65:99226e41
ARRAY /dev/md1 level=raid1 num-devices=2 UUID=459d5e27:904f3c79:d8b78f65:99226e41
ARRAY /dev/md2 level=raid1 num-devices=2 UUID=6751920d:40d22e18:42039ac8:7bde15d5
--- /proc/mdstat:
Personalities : [raid1]
md2 : active raid1 dm-1[1] dm-5[0]
20971456 blocks [2/2] [UU]
md1 : active raid1 dm-2[1] dm-3[0]
209715136 blocks [2/2] [UU]
md0 : active raid1 sda1[0] sdb1[1]
9767424 blocks [2/2] [UU]
unused devices: <none>
--- /proc/partitions:
major minor #blocks name
8 16 244198584 sdb
8 17 9767488 sdb1
8 18 234428512 sdb2
8 0 488386584 sda
8 1 9767488 sda1
8 2 478616512 sda2
9 0 9767424 md0
253 0 1048576 dm-0
253 1 20971520 dm-1
253 2 209715200 dm-2
253 3 209715200 dm-3
253 4 1048576 dm-4
253 5 20971520 dm-5
253 6 115343360 dm-6
9 1 209715136 md1
253 7 10485760 dm-7
9 2 20971456 md2
--- initrd.img-2.6.32-bpo.5-amd64:
52179 blocks
ace747c853669dd199525d56ad4ebb1a ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/raid1.ko
dea61d351c3f9ec3f1a8c4b026dcfedf ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/raid10.ko
a7b2c70bf9476700b53cbaa5f8d2c043 ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/raid0.ko
77b22303d8f465b916e21abcb9bda77a ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/raid456.ko
94d5ddd10144ecbc7cc57559c016e043 ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/raid6_pq.ko
2e0eb562e2d2d0cffadc8646c3500445 ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/dm-region-hash.ko
e7fd3f8896ca2782f48e92ebcf8e31e0 ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/multipath.ko
a09a04c19f7b42bdbd562015cf0ead3a ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/linear.ko
79e8c13d859121168573149bab91917d ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/dm-mirror.ko
6ffe90af7f011592c0d73e70712a218e ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/md-mod.ko
4b3e583dcea14e1505e4ba48c91b5d90 ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/dm-snapshot.ko
5e6064d241f285362a2db8590c902743 ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/dm-log.ko
f9e99c46e33f952d4e4064048520f4d0 ./lib/modules/2.6.32-bpo.5-amd64/kernel/drivers/md/dm-mod.ko
4c1cab931ecd1e4eb677632cf42a800d ./etc/mdadm/mdadm.conf
e1e2d0e985196fecaf41fb42e9968af2 ./scripts/local-top/mdadm
1e3828eef5ebb2b42ba71d08fc4247d4 ./sbin/mdadm
--- /proc/modules:
dm_mirror 10891 0 - Live 0xffffffffa01c8000
dm_region_hash 6648 1 dm_mirror, Live 0xffffffffa01c0000
dm_log 7381 2 dm_mirror,dm_region_hash, Live 0xffffffffa01b8000
dm_snapshot 18417 0 - Live 0xffffffffa01ad000
dm_mod 53530 30 dm_mirror,dm_log,dm_snapshot, Live 0xffffffffa0194000
raid1 18383 3 - Live 0xffffffffa0189000
md_mod 73744 4 raid1, Live 0xffffffffa016c000
--- /var/log/syslog:
--- volume detail:
/dev/sda is not recognised by mdadm.
/dev/sda1:
Magic : a92b4efc
Version : 00.90.00
UUID : ee1de88e:0bf13d47:d8b78f65:99226e41
Creation Time : Wed Aug 27 18:48:07 2008
Raid Level : raid1
Used Dev Size : 9767424 (9.31 GiB 10.00 GB)
Array Size : 9767424 (9.31 GiB 10.00 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Tue Mar 15 12:44:03 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : abee52cb - correct
Events : 524210
Number Major Minor RaidDevice State
this 0 8 1 0 active sync /dev/sda1
0 0 8 1 0 active sync /dev/sda1
1 1 8 17 1 active sync /dev/sdb1
--
/dev/sda2 is not recognised by mdadm.
/dev/sdb is not recognised by mdadm.
/dev/sdb1:
Magic : a92b4efc
Version : 00.90.00
UUID : ee1de88e:0bf13d47:d8b78f65:99226e41
Creation Time : Wed Aug 27 18:48:07 2008
Raid Level : raid1
Used Dev Size : 9767424 (9.31 GiB 10.00 GB)
Array Size : 9767424 (9.31 GiB 10.00 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Update Time : Tue Mar 15 12:44:03 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Checksum : abee52dd - correct
Events : 524210
Number Major Minor RaidDevice State
this 1 8 17 1 active sync /dev/sdb1
0 0 8 1 0 active sync /dev/sda1
1 1 8 17 1 active sync /dev/sdb1
--
/dev/sdb2 is not recognised by mdadm.
/dev/vda is not recognised by mdadm.
/dev/vdb is not recognised by mdadm.
--- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-2.6.32-bpo.5-amd64 root=/dev/md0 ro vga=791
--- grub2:
insmod raid
set root=(md0)
insmod raid
set root=(md0)
linux /boot/vmlinuz-2.6.32-bpo.5-amd64 root=/dev/md0 ro vga=791
insmod raid
set root=(md0)
linux /boot/vmlinuz-2.6.32-bpo.5-amd64 root=/dev/md0 ro single vga=791
insmod raid
set root=(md0)
linux /boot/vmlinuz-2.6.26-2-amd64 root=/dev/md0 ro vga=791
insmod raid
set root=(md0)
linux /boot/vmlinuz-2.6.26-2-amd64 root=/dev/md0 ro single vga=791
--- udev:
ii udev 0.125-7+lenny3 /dev/ and hotplug management daemon
cd6f5683974ea65603f04ec699b3cff2 /etc/udev/rules.d/65_mdadm.vol_id.rules
--- /dev:
brw-rw---- 1 root disk 9, 0 2011-02-22 12:28 /dev/md0
brw-rw---- 1 root disk 9, 1 2011-02-22 13:10 /dev/md1
brw-rw---- 1 root disk 9, 2 2011-03-15 12:41 /dev/md2
/dev/disk/by-id:
total 0
lrwxrwxrwx 1 root root 9 2011-02-22 12:28 ata-Hitachi_HDT725025VLAT80_VF1100R10G4V4K -> ../../sdb
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 ata-Hitachi_HDT725025VLAT80_VF1100R10G4V4K-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 ata-Hitachi_HDT725025VLAT80_VF1100R10G4V4K-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 9 2011-02-22 12:28 ata-ST3500320NS_9QM1RV7M -> ../../sda
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 ata-ST3500320NS_9QM1RV7M-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 ata-ST3500320NS_9QM1RV7M-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-name-vda-opt -> ../../dm-5
lrwxrwxrwx 1 root root 10 2011-03-15 11:37 dm-name-vda-opt_backup -> ../../dm-7
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-name-vda-swap -> ../../dm-4
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-name-vda-workstore -> ../../dm-3
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-name-vda-workstore_backup -> ../../dm-6
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-name-vdb-opt -> ../../dm-1
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-name-vdb-swap -> ../../dm-0
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-name-vdb-workstore -> ../../dm-2
lrwxrwxrwx 1 root root 10 2011-03-15 11:37 dm-uuid-LVM-HpOWLrwp515cgBhtlxVLFOCcRh4kVCyL7ZS2xS6NBbVfXsFTo11v7rtw4iYIiMnu -> ../../dm-7
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-uuid-LVM-HpOWLrwp515cgBhtlxVLFOCcRh4kVCyLb3X5PXTlzQQKZe5kMlGeQQAqzerv9Nsx -> ../../dm-4
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-uuid-LVM-HpOWLrwp515cgBhtlxVLFOCcRh4kVCyLeVPsesUE4TUBgJMJqQCgYQnpmgHseo6q -> ../../dm-6
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-uuid-LVM-HpOWLrwp515cgBhtlxVLFOCcRh4kVCyLvrJzCvQkJvk5LFojeGqIYryrU5U0tWrP -> ../../dm-5
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-uuid-LVM-HpOWLrwp515cgBhtlxVLFOCcRh4kVCyLzXoO2EPJWLIXmZmTorFjEEYz9tFZ2O4k -> ../../dm-3
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-uuid-LVM-PeMHWh9oKaoJqiDUcEfebnVlOsn9QT4Ph9tbCn7HmuHqGXItPdHCw31BZuTgAXkz -> ../../dm-2
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-uuid-LVM-PeMHWh9oKaoJqiDUcEfebnVlOsn9QT4PIIDpnmT477PxPM3hMYNkfjzxGXhDEwLN -> ../../dm-1
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 dm-uuid-LVM-PeMHWh9oKaoJqiDUcEfebnVlOsn9QT4Pl1ZKtZuvuqDeO1PkLAig2VmeBoc9hZUL -> ../../dm-0
lrwxrwxrwx 1 root root 9 2011-02-22 12:38 md-uuid-5d93b49d:d407f8fe:42039ac8:7bde15d5 -> ../../md1
lrwxrwxrwx 1 root root 9 2011-03-15 12:35 md-uuid-9f0f6058:342b7c57:42039ac8:7bde15d5 -> ../../md2
lrwxrwxrwx 1 root root 9 2011-02-22 12:28 md-uuid-ee1de88e:0bf13d47:d8b78f65:99226e41 -> ../../md0
lrwxrwxrwx 1 root root 9 2011-02-22 12:28 scsi-SATA_Hitachi_HDT7250_VF1100R10G4V4K -> ../../sdb
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 scsi-SATA_Hitachi_HDT7250_VF1100R10G4V4K-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 scsi-SATA_Hitachi_HDT7250_VF1100R10G4V4K-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 9 2011-02-22 12:28 scsi-SATA_ST3500320NS_9QM1RV7M -> ../../sda
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 scsi-SATA_ST3500320NS_9QM1RV7M-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 scsi-SATA_ST3500320NS_9QM1RV7M-part2 -> ../../sda2
/dev/disk/by-path:
total 0
lrwxrwxrwx 1 root root 9 2011-02-22 12:28 pci-0000:00:0f.0-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 pci-0000:00:0f.0-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 pci-0000:00:0f.0-scsi-0:0:0:0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 9 2011-02-22 12:28 pci-0000:00:0f.1-scsi-1:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 pci-0000:00:0f.1-scsi-1:0:0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 pci-0000:00:0f.1-scsi-1:0:0:0-part2 -> ../../sdb2
/dev/disk/by-uuid:
total 0
lrwxrwxrwx 1 root root 9 2011-02-22 12:28 4d68e53c-7777-4f58-a159-ff2b93a7841b -> ../../md0
lrwxrwxrwx 1 root root 9 2011-02-22 12:38 4dd0025a-8483-47a4-bdc5-d3fd930fb875 -> ../../md1
lrwxrwxrwx 1 root root 9 2011-03-15 12:35 627696f0-88ae-40fa-97c8-6e93771cd52c -> ../../md2
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 94de9425-463b-41ba-b557-8aea8bc067b1 -> ../../dm-0
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 ab8c0161-e535-4251-8314-3222770eaf78 -> ../../dm-6
lrwxrwxrwx 1 root root 10 2011-02-22 12:28 f2d5b32f-7a4c-42c0-850f-005ffeb3eb08 -> ../../dm-4
/dev/md:
total 0
-- System Information:
Debian Release: 5.0.8
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mdadm depends on:
ii debconf 1.5.24 Debian configuration management sy
ii libc6 2.7-18lenny7 GNU C Library: Shared libraries
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
ii makedev 2.3.1-88 creates device files in /dev
ii udev 0.125-7+lenny3 /dev/ and hotplug management daemo
Versions of packages mdadm recommends:
ii module-init-tools 3.4-1 tools for managing Linux kernel mo
ii postfix [mail-transport-agent 2.5.5-1.1 High-performance mail transport ag
mdadm suggests no packages.
-- debconf information:
mdadm/autostart: true
mdadm/mail_to: root
mdadm/initrdstart_msg_errmd:
* mdadm/initrdstart: all
mdadm/initrdstart_msg_errconf:
mdadm/initrdstart_notinconf: false
mdadm/initrdstart_msg_errexist:
mdadm/initrdstart_msg_intro:
mdadm/autocheck: true
mdadm/initrdstart_msg_errblock:
mdadm/start_daemon: true
More information about the pkg-mdadm-devel
mailing list