Please update mdadm to version 3.1.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm |
New
|
Undecided
|
Unassigned | ||
mdadm (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mdadm
The version of mdadm in the repositories is quite old:
rune@
mdadm - v2.6.7.1 - 15th October 2008
rune@
mdadm:
Installed: 2.6.7.1-1ubuntu15
Candidate: 2.6.7.1-1ubuntu15
Version table:
*** 2.6.7.1-1ubuntu15 0
500 http://
100 /var/lib/
about 20 months to be exact: http://
Could we get an update of this package in the Ubuntu repositories?
It would - at least - fix the bug which brought me here: http://
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: mdadm 2.6.7.1-1ubuntu15
ProcVersionSign
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
CurrentDmesg:
[ 4.993963] ppdev: user-space parallel port driver
[ 5.751027] hda-intel: IRQ timing workaround is activated for card #2. Suggest a bigger bdl_pos_adj.
[ 14.172030] eth0: no IPv6 routers present
[ 555.014664] EXT4-fs (md1): Magic mismatch, very weird!
Date: Thu Jul 8 13:37:18 2010
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100405)
MDadmExamine.
MDadmExamine.
MDadmExamine.
MDadmExamine.
MDadmExamine.
MDadmExamine.
MDadmExamine.
MDadmExamine.
MDadmExamine.
MachineType: . .
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, no user)
LANG=en_DK.utf8
SHELL=/bin/bash
ProcMDstat:
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sdc[1] sdb1[0]
976759936 blocks [2/2] [UU]
unused devices: <none>
SourcePackage: mdadm
dmi.bios.date: 05/26/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: IP35 Pro XE(Intel P35-ICH9R)
dmi.board.vendor: http://
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: System Enclosure Manufacter
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: .
dmi.product.
dmi.sys.vendor: .
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'
Status changed to 'Confirmed' because the bug affects multiple users.