All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Interesting mdadm quirk ...
Date: Sat, 7 Jan 2017 13:21:03 +0000	[thread overview]
Message-ID: <5870EB3F.2060206@youngman.org.uk> (raw)

Just been doing some raid testing, and this happened ...

linux-lfqf:/dev # mdadm md/parity
md/parity: 31.97GiB raid5 3 devices, 0 spares. Use mdadm --detail for
more detail.
linux-lfqf:/dev # mdadm --stop md/parity
mdadm: Cannot open md/parity
linux-lfqf:/dev # mdadm --stop /dev/md/parity
mdadm: stopped /dev/md/parity

Weird - why can it successfully stop it when passed an absolute path,
but not when passed a relative path? When I did the first variant, I
used tab completion, and then when I edited it I really did edit it, not
retype it, so I can't see any way the two arguments could refer to
different objects.

Oh - and

mdadm --version
mdadm - v3.4 - 28th January 2016

ie stock SuSE leap 42.2

Cheers,
Wol

             reply	other threads:[~2017-01-07 13:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-07 13:21 Wols Lists [this message]
2017-01-08 22:44 ` Interesting mdadm quirk NeilBrown
2017-01-09  6:59   ` Wols Lists
2017-01-10 22:07     ` NeilBrown

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=5870EB3F.2060206@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.