From: Hao Wang <pkuwangh@gmail.com>
To: Linux-nvme@lists.infradead.org
Subject: Data corruption when using multiple devices with NVMEoF TCP
Date: Tue, 22 Dec 2020 10:09:43 -0800 [thread overview]
Message-ID: <CAJS6EdjsTVgs3JK3q2DePjEz1A0s9RJTOwqo=Ka7kinNMECtJw@mail.gmail.com> (raw)
I'm using kernel 5.2.9 with following related configs enabled:
CONFIG_NVME_CORE=y
CONFIG_BLK_DEV_NVME=y
CONFIG_NVME_MULTIPATH=y
CONFIG_NVME_FABRICS=m
# CONFIG_NVME_FC is not set
CONFIG_NVME_TCP=m
CONFIG_NVME_TARGET=m
CONFIG_NVME_TARGET_LOOP=m
# CONFIG_NVME_TARGET_FC is not set
CONFIG_NVME_TARGET_TCP=m
CONFIG_RTC_NVMEM=y
CONFIG_NVMEM=y
CONFIG_NVMEM_SYSFS=y
On target side, I exported 2 NVMe devices using tcp/ipv6:
[root@rtptest34337.prn2 ~/ext_nvme]# ll
/sys/kernel/config/nvmet/ports/1/subsystems/
total 0
lrwxrwxrwx 1 root root 0 Dec 19 02:08 nvmet-rtptest34337-1 ->
../../../../nvmet/subsystems/nvmet-rtptest34337-1
lrwxrwxrwx 1 root root 0 Dec 19 02:08 nvmet-rtptest34337-2 ->
../../../../nvmet/subsystems/nvmet-rtptest34337-2
On initiator side, I could successfully connect the 2 nvme devices,
nvme1n1 & nvme2n1;
[root@rtptest34206.prn2 /]# nvme list
Node SN Model
Namespace Usage Format FW Rev
---------------- --------------------
---------------------------------------- ---------
-------------------------- ---------------- --------
/dev/nvme0n1 *********** INTEL ******* 1
256.06 GB / 256.06 GB 512 B + 0 B PSF119D
/dev/nvme1n1 *********** Linux 1
900.19 GB / 900.19 GB 4 KiB + 0 B 5.2.9-0_
/dev/nvme2n1 *********** Linux 1
900.19 GB / 900.19 GB 4 KiB + 0 B 5.2.9-0_
Then for each of nvme1n1 & nvme2n1, I created a partition using fdisk;
type is "linux raid autodetect";
Next I created a RAID-0 volume using, created a filesystem on it, and
mounted itL
# mdadm --create /dev/md5 --level=0 --raid-devices=2 --chunk=128
/dev/nvme1n1p1 /dev/nvme2n1p1
# mkfs.xfs -f /dev/md5
# mkdir /flash
# mount -o rw,noatime,discard /dev/md5 /flash/
Now, when I copy a large directory into /flash/, a lot of files under
/flash/ are corrupted.
Specifically, that large directory has a lot of .gz files, and unzip
will fail on many of them;
also diff with original files does show they are different, although
the file size is exactly the same.
Also I found that if I don't create a RAID-0 array, instead just make
a filesystem on either /dev/nvme1n1p1 or /dev/nvme2n1p1, there is no
data corruption.
I'm wondering if there is a known issue, or I'm doing something not
really supported.
Thanks!
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2020-12-22 18:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 18:09 Hao Wang [this message]
2020-12-22 19:29 ` Data corruption when using multiple devices with NVMEoF TCP Sagi Grimberg
2020-12-22 19:58 ` Hao Wang
2020-12-23 8:41 ` Sagi Grimberg
2020-12-23 8:43 ` Christoph Hellwig
2020-12-23 21:23 ` Sagi Grimberg
2020-12-23 22:23 ` Hao Wang
2020-12-24 1:51 ` Hao Wang
2020-12-24 2:57 ` Sagi Grimberg
2020-12-24 10:28 ` Hao Wang
2020-12-24 17:56 ` Sagi Grimberg
2020-12-25 7:49 ` Hao Wang
2020-12-25 9:05 ` Sagi Grimberg
[not found] ` <CAJS6Edgb+yCW5q5dA=MEkL0eYs4MXoopdiz72nhkxpkd5Fe_cA@mail.gmail.com>
2020-12-29 1:25 ` Sagi Grimberg
2021-01-06 1:53 ` Sagi Grimberg
2021-01-06 8:21 ` Hao Wang
2021-01-11 8:56 ` Hao Wang
2021-01-11 10:11 ` Sagi Grimberg
[not found] ` <CAJS6Edi9Es1zR9QC+=kwVjAFAGYrEru4vibW42ffyWoMDutFhQ@mail.gmail.com>
2021-01-12 0:36 ` Sagi Grimberg
2021-01-12 1:29 ` Sagi Grimberg
2021-01-12 2:22 ` Ming Lei
2021-01-12 6:49 ` Sagi Grimberg
2021-01-12 8:55 ` Hao Wang
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='CAJS6EdjsTVgs3JK3q2DePjEz1A0s9RJTOwqo=Ka7kinNMECtJw@mail.gmail.com' \
--to=pkuwangh@gmail.com \
--cc=Linux-nvme@lists.infradead.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.