Your message dated Wed, 1 Nov 2006 17:33:50 +0100
with message-id <[EMAIL PROTECTED]>
has caused the Debian Bug report #396570,
regarding mdadm: Incorrect error message for insufficient permission
to be marked as having been forwarded to the upstream software
author(s) [EMAIL PROTECTED]
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
severity 396570 wishlist
tags 396570 upstream
thanks
> 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 operation as a normal user, thus did not have
> sufficient permission to do so.
There is no reason why /sbin should be in your $PATH as a normal
user, is there?
Anyway, I am forwarding this to Neil, the upstream author. Neil,
would you be inclined to print an appropriate error message if the
open() call returns EPERM?
> The failure to autostart the array (recovery) after the crash is not
> mdadm's fault; I have RAID 1 built in to the kernel, so it starts
> without mdadm.
md will not automatically add components to an array, so it's
definitely noone's fault or a failure.
Cheers,
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
signature.asc
Description: Digital signature (GPG/PGP)
--- End Message ---
