From: Xiao Ni <xni@redhat.com>
To: linux-raid@vger.kernel.org
Subject: /dev/md0 can't be created
Date: Wed, 25 Mar 2015 02:15:34 -0400 (EDT) [thread overview]
Message-ID: <12135556.2792023.1427264134774.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1215809785.2787621.1427263359309.JavaMail.zimbra@redhat.com>
Hi all
I have encountered so many times, the raid device is created successfully, but the directory
/dev/md0 can't be created. It can't reproduce 100%.
[root@intel-sugarbay-do-01 create_assemble]# cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid10 loop7[7](S) loop6[6] loop5[5] loop4[4] loop3[3] loop2[2] loop1[1] loop0[0]
1788416 blocks super 1.2 512K chunks 2 near-copies [7/7] [UUUUUUU]
bitmap: 0/1 pages [0KB], 65536KB chunk
unused devices: <none>
[root@intel-sugarbay-do-01 create_assemble]# ls /dev/md0
ls: cannot access /dev/md0: No such file or directory
The underline devices are loop devices which are created with big file.
The kernel I used is RHEL7 (3.10.0-234.el7.x86_64.debug, mdadm - v3.3.2 - 21st August 2014)
I'll try to reproduce this with upstream kernel and mdadm. But I think it shouldn't be the problem about kernel.
What do you think I should check for this? And which tool is responsible for creating the directory? Maybe
I can add some log to it to find the reason.
Best Regards
Xiao
next parent reply other threads:[~2015-03-25 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1215809785.2787621.1427263359309.JavaMail.zimbra@redhat.com>
2015-03-25 6:15 ` Xiao Ni [this message]
2015-03-25 6:35 ` /dev/md0 can't be created NeilBrown
2015-03-26 7:36 ` Xiao Ni
2015-03-27 6:06 ` Xiao Ni
2015-04-01 2:53 ` NeilBrown
2015-04-02 2:52 ` Xiao Ni
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=12135556.2792023.1427264134774.JavaMail.zimbra@redhat.com \
--to=xni@redhat.com \
--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.