All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tor Arne Vestbø" <torarnv@gmail.com>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: Linux RAID autodetect partitions go missing from /dev, but fdisk can see them
Date: Thu, 18 Dec 2008 23:22:30 +0100	[thread overview]
Message-ID: <494ACD26.2040809@gmail.com> (raw)
In-Reply-To: <18759.8246.568849.244513@notabene.brown>

>> On Wednesday December 10, torarnv@gmail.com wrote:
>>> Running 'partprobe -s' successfully finds the two missing partitions
>>> and adds device nodes, and the nodes can be 'file -sL'ed, but when
>>> trying to assemble the array again with these new nodes in the system,
>>> I'm told that sdc1 is not found, and after the --assemble is done, the
>>> device nodes are once again missing (!) see [4]

Neil Brown wrote:
> Can you:
>   strace -o /tmp/str -s 200 mdadm --assemble --scan --verbose /dev/md0

Should I try this after doing partprobe first? In that case /dev/sdb1
and /dev/sdc1 exist, and we might see from the trace what causes them to
disappear?

>> [4] http://pastebin.com/m4475c9ae   partprobe + mdadm --assemble

Tor Arne


  parent reply	other threads:[~2008-12-18 22:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 20:56 Linux RAID autodetect partitions go missing from /dev, but fdisk can see them Tor Arne Vestbø
2008-12-16  3:27 ` Neil Brown
2008-12-18 22:03   ` Tor Arne Vestbø
2008-12-18 22:19     ` Tor Arne Vestbø
     [not found]     ` <18762.53424.819087.495066@notabene.brown>
2009-01-18 17:51       ` Tor Arne Vestbø
2009-01-19 16:18         ` Tor Arne Vestbø
2009-01-31 13:19         ` Tor Arne Vestbø
2009-01-31 18:50           ` Richard Scobie
2008-12-18 22:22   ` Tor Arne Vestbø [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-11  6:41 Tor Arne Vestbø

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=494ACD26.2040809@gmail.com \
    --to=torarnv@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.