From: artur.paszkiewicz@intel.com (Artur Paszkiewicz)
Subject: RAID0 mdadm Question
Date: Tue, 31 May 2016 15:54:24 +0200 [thread overview]
Message-ID: <574D9790.1080106@intel.com> (raw)
In-Reply-To: <CA+Tq-RoTOSwAbJJFBgkDEC8LV-CiFOHKvbC3i3tkUUoxu03ziQ@mail.gmail.com>
On 05/31/2016 11:41 AM, Hiroyuki Sato wrote:
> Hello
>
> NVMe Newbie question.
>
> I have two P3600 PCIe NVMe Cards.
> And I created RAID0 volume with mdadm command.
> It works fine. But after reboot, I can't mount file system it.
> It seems lost partition table.
> (No partition information)
>
> Environment
> - NVMe: Intel P3600 cards * 2
> - Linux: 4.4.0
> - OS: CentOS7
>
> Question
>
> 1, Do I need re-create file system on each Boot time?
>
> 2, If not What step is missing?
>
> generate mdadm.conf?
>
> Best regards.
>
> NVMe RAID step
>
> Basically I followed this doc
> https://communities.intel.com/community/itpeernetwork/blog/2015/10/01/how-to-use-and-benchmark-nvme-ssd-create-a-software-raid-and-analyze-performance-the-answers-are-here
>
> Step1: create container
>
> mdadm -C /dev/md/imsm0 /dev/nvme0n1 /dev/nvme1n1 -n 2 -e imsm -f
> mdadm: /dev/nvme0n1 appears to be part of a raid array:
> level=raid0 devices=0 ctime=Thu Jan 1 09:00:00 1970
> Continue creating array? y
> mdadm: container /dev/md/imsm0 prepared.
>
> Step2, create md device
> mdadm -C /dev/md0 /dev/md/imsm0 -n 2 -l 0 -c 128 -f
> mdadm: array /dev/md0 started.
>
> Step3: Create Partition
> parted /dev/md0
>
> (parted) mkpart
> Partition name? []?
> File system type? [ext2]? xfs
> Start? 0%
> End? -1
>
> (parted) p
> Model: Linux Software RAID Array (md)
> Disk /dev/md0: 800GB
> Sector size (logical/physical): 512B/512B
> Partition Table: gpt
> Disk Flags:
>
> Number Start End Size File system Name Flags
> 1 1049kB 800GB 800GB
>
> (parted) quit
> Information: You may need to update /etc/fstab.
>
> Step4: Newfs
>
> /sbin/mkfs.xfs -K /dev/md0p1 -f
>
> Step5: mount
>
> mount -o noatime,nodiratime,nobarrier /dev/md0p1 /mnt/nvme1
>
Maybe the array has not assembled automatically after reboot. Check
/proc/mdstat. Also, the device you created in step 2 could have
assembled under a different name, like /dev/md126.
Artur
next prev parent reply other threads:[~2016-05-31 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 9:41 RAID0 mdadm Question Hiroyuki Sato
2016-05-31 13:54 ` Artur Paszkiewicz [this message]
2016-06-01 2:08 ` Hiroyuki Sato
2016-06-01 8:23 ` Artur Paszkiewicz
2016-06-02 7:26 ` Hiroyuki Sato
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=574D9790.1080106@intel.com \
--to=artur.paszkiewicz@intel.com \
/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.