Your message dated Wed, 26 May 2010 09:35:52 +0200
with message-id <[email protected]>
and subject line closing due to inactivity
has caused the Debian Bug report #559390,
regarding mdadm: issues with degraded array
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
559390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559390
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mdadm
Version: 2.6.7.2-3
Severity: normal
The misbehavior occurred on a system different from the one being used
to file this report. The actual system had a 2.6.30-2-amd64 kernel
(stock debian).
md1 looked like this:
/dev/md1:
Version : 00.90
Creation Time : Mon Dec 15 06:50:18 2008
Raid Level : raid1
Array Size : 730523648 (696.68 GiB 748.06 GB)
Used Dev Size : 730523648 (696.68 GiB 748.06 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Thu Dec 3 16:12:41 2009
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : b77027df:d6aa474a:2a09e10c:740d4ffc
Events : 0.30940
Number Major Minor RaidDevice State
0 0 0 0 removed
1 8 19 1 active sync /dev/sdb3
checkarray, or rather its log output, did not indicate there was any
problem with md1.
Expected result: a log message like "md1 is degraded".
I also expected that the system would automatically recover the
missing device. I don't know if that is the intended behavior.
The reasons the device got separated are murky, but there appears to
have been a hardware problem. Also, the removal of the missing part
happened during an usuccessful reboot; because the root device
changed, the root partition was never mounted.
Details of the setup.
8 core system with 2 identical SATA disks.
md0 is made from sda1 and sdb1.
md1 is made from sda3 and sdb3.
sda3 is the part that got kicked out.
I am currently running
mdadm /dev/md1 --re-add /dev/sda3
which appears to be recovering the lost partition.
-- System Information:
Debian Release: 5.0.3
APT prefers stable
APT policy: (500, 'stable'), (50, 'unstable'), (40, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
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-18 GNU C Library: Shared libraries
ii makedev 2.3.1-88 creates device files in /dev
mdadm recommends no packages.
mdadm suggests no packages.
--- End Message ---
--- Begin Message ---
I am closing these bug reports because of lack of activity. If the
problem persists, please provide the requested information, and/or
anything additional to help me diagnose and fix this, and reopen the
report.
--
.''`. martin f. krafft <[email protected]> Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduck http://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
--- End Message ---
