On Fri, 29 Jan 2010 15:44:27 -0700
Rob Sims wrote:
> Still not fixed:
> $ mdadm --remove /dev/md0 /dev/sdd1
> mdadm: /dev/md0 does not appear to be an md device
> $ mdadm --version
> mdadm - v3.1.1 - 19th November 2009
Thanks.
I have committed the following fix upstream which should resolve th
On Sat, Jan 30, 2010 at 10:59:34AM +1300, martin f krafft wrote:
> notfixed 396570 3.0
> found 396570 3.0.3-2
> fixed 396570 3.1.1-1
> thanks
>
> It's fixed in 3.1.1:
>
> mdadm-lab:~# su nobody -c '/sbin/mdadm --remove /dev/md0 /dev/hda1'
> mdadm: error opening /dev/md0: Permission denied
> mdadm
notfixed 396570 3.0
found 396570 3.0.3-2
fixed 396570 3.1.1-1
thanks
It's fixed in 3.1.1:
mdadm-lab:~# su nobody -c '/sbin/mdadm --remove /dev/md0 /dev/hda1'
mdadm: error opening /dev/md0: Permission denied
mdadm-lab:~# mdadm --version
mdadm - v3.1.1 - 19th November 2009
--
.''`. martin f. k
Package: mdadm
Version: 2.5.4-1
Severity: normal
Upon boot after a crash due to failing video hardware, one disk in a
raid 1 array was marked failed. The command
mdadm --re-add /dev/md1 /dev/sdb1
failed with the message /dev/md1 is not an md device. The real problem
was that I attempted the oper
4 matches
Mail list logo