linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Iustin Pop <iusty@k1024.org>
To: Peter Rabbitson <rabbit@rabbit.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: Customize the error emails of  `mdadm --monitor`
Date: Wed, 6 Jun 2007 14:11:21 +0200	[thread overview]
Message-ID: <20070606121121.GA23486@teal.hq.k1024.org> (raw)
In-Reply-To: <46669B20.6030706@rabbit.us>

On Wed, Jun 06, 2007 at 01:31:44PM +0200, Peter Rabbitson wrote:
> Peter Rabbitson wrote:
> >Hi,
> >
> >Is there a way to list the _number_ in addition to the name of a 
> >problematic component? The kernel trend to move all block devices into 
> >the sdX namespace combined with the dynamic name allocation renders 
> >messages like "/dev/sdc1 has problems" meaningless. It would make remote 
> >server support so much easier, by allowing the administrator to label 
> >drive trays Component0 Component1 Component2... etc, and be sure that 
> >the local tech support person will not pull out the wrong drive from the 
> >system.
> >
> 
> Any takers? Or is it a RTFM question (in which case I certainly 
> overlooked the relevant doc)?

If you use udev, have you looked in /dev/disk? I think it solves the
problem you need by allowing one to see either the disks by id or by
path. Making the reverse map is then trivial (for a reasonable number of
disks).

regards,
iustin

  reply	other threads:[~2007-06-06 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 16:05 Customize the error emails of `mdadm --monitor` Peter Rabbitson
2007-06-06 11:31 ` Peter Rabbitson
2007-06-06 12:11   ` Iustin Pop [this message]
2007-06-06 12:23     ` Peter Rabbitson
2007-06-06 13:26       ` Iustin Pop
2007-06-06 14:10       ` Gabor Gombas
2007-06-06 14:24         ` Peter Rabbitson
2007-06-06 20:49           ` Gabor Gombas
2007-06-06 20:59             ` Peter Rabbitson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070606121121.GA23486@teal.hq.k1024.org \
    --to=iusty@k1024.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=rabbit@rabbit.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).