[email protected]
[Top] [All Lists]

Bug#510641: marked as forwarded (mdadm: checkarray emits messages for au

Subject: Bug#510641: marked as forwarded mdadm: checkarray emits messages for auto-read-only md devices
From: Debian Bug Tracking System
Date: Wed, 04 Feb 2009 11:09:10 +0000
Your message dated Wed, 4 Feb 2009 12:04:02 +0100
with message-id <[email protected]>
has caused the   report #510641,
regarding mdadm: checkarray emits messages for auto-read-only md devices
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
510641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510641
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Subject: checkarray fails on auto-read-only
From: martin f krafft
Date: Wed, 4 Feb 2009 12:04:02 +0100
tags 510641 confirmed upstream
thanks

Neil, do you have a better solution to this problem? (see attached)

Thanks,

-- 
 .''`.   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
 
the english take english for granted.
but if we explore its paradoxes,
we find that quicksand can work slowly.
--- Begin Message ---
Subject: Bug#510641: additional info
From: Andrei Caraman
Date: Tue, 6 Jan 2009 12:53:13 -0500
indeed /usr/share/mdadm/checkarray exits with an error message when it
encounters a redundant MD device in auto-read-only state.  this state is
normal for assembled MD device which haven't yet been written to, such as
the swap area mentioned by Philipp Kern.

any write operation to the respective device would take it out of
auto-read-only (in my case it was a swapoff, mkswap, swapon which did the
trick), but one can't expect checkarray to figure out what sort of
write is safe on the device.  

i think that checkarray should look for and skip any md device it finds in
the auto-read-only state.



hope this helps,
adc





_______________________________________________
pkg-mdadm-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-mdadm-devel


--- End Message ---

--- End Message ---
<Prev in Thread] Current Thread [Next in Thread>
  • Bug#510641: marked as forwarded (mdadm: checkarray emits messages for auto-read-only md devices), Debian Bug Tracking System <=