From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"soccerl@microsoft.com" <soccerl@microsoft.com>
Subject: Re: FAIL: dax-errors.sh failures on 4.14.0-rc4+
Date: Fri, 13 Oct 2017 19:28:15 +0000 [thread overview]
Message-ID: <1507922771.23025.99.camel@intel.com> (raw)
In-Reply-To: <MWHPR21MB01433B4F14C4D5EA3A1215E2A6750@MWHPR21MB0143.namprd21.prod.outlook.com>
On Tue, 2017-10-10 at 03:04 +0000, Cheng-mean Liu (SOCCER) wrote:
> Hi:
>
> I am hitting the following ndctl test failure, all code from
> ndctl/Linux upstream kernel.
>
> Is this a know issue?
>
> FAIL: dax-errors.sh
> SKIP: daxdev-errors.sh
>
> FAIL: dax-errors.sh
> ===================
>
> + DEV=
> + NDCTL=../ndctl/ndctl
> + BUS='-b nfit_test.0'
> + BUS1='-b nfit_test.1'
> + MNT=test_dax_mnt
> + FILE=image
> + json2var='s/[{}",]//g; s/:/=/g'
> + rc=77
> + check_min_kver 4.7
> + local ver=4.7
> ++ uname -r
> + : 4.14.0-rc4+
> + '[' -n 4.7 ']'
> ++ echo -e '4.7\n4.14.0-rc4+'
> ++ sort -V
> ++ head -1
> + [[ 4.7 == \4\.\7 ]]
> + set -e
> + mkdir -p test_dax_mnt
> + trap 'err $LINENO' ERR
> + modprobe nfit_test
> + ../ndctl/ndctl disable-region -b nfit_test.0 all
> disabled 6 regions
> + ../ndctl/ndctl zero-labels -b nfit_test.0 all
> zeroed 4 nmems
> + ../ndctl/ndctl enable-region -b nfit_test.0 all
> enabled 6 regions
> + rc=1
> + dev=x
> ++ ../ndctl/ndctl create-namespace -b nfit_test.0 -t pmem -m raw
> + json='{
> "dev":"namespace5.0",
> "mode":"raw",
> "size":67108864,
> "uuid":"8ce610c5-f7ca-4df8-84f4-d27adcb19ceb",
> "blockdev":"pmem5",
> "badblock_count":8
> }'
> ++ echo '{' '"dev":"namespace5.0",' '"mode":"raw",' '"size":67108864,'
> '"uuid":"8ce610c5-f7ca-4df8-84f4-d27adcb19ceb",' '"blockdev":"pmem5",'
> '"badblock_count":8' '}'
> ++ sed -e 's/[{}",]//g; s/:/=/g'
> + eval dev=namespace5.0 mode=raw size=67108864 uuid=8ce610c5-f7ca-
> 4df8-84f4-d27adcb19ceb blockdev=pmem5 badblock_count=8
> ++ dev=namespace5.0
> ++ mode=raw
> ++ size=67108864
> ++ uuid=8ce610c5-f7ca-4df8-84f4-d27adcb19ceb
> ++ blockdev=pmem5
> ++ badblock_count=8
> + '[' namespace5.0 = x ']'
> + '[' raw '!=' raw ']'
> + read sector len
> + '[' 131072 -ne 131072 ']'
> + dd if=/dev/pmem5 of=/dev/null iflag=direct bs=512 skip=65536 count=8
> dd: error reading '/dev/pmem5': Input/output error
> 0+0 records in
> 0+0 records out
> 0 bytes copied, 0.0003475 s, 0.0 kB/s
> + dd of=/dev/pmem5 if=/dev/zero oflag=direct bs=512 seek=65536 count=8
> 8+0 records in
> 8+0 records out
> 4096 bytes (4.1 kB, 4.0 KiB) copied, 0.0003608 s, 11.4 MB/s
> + read sector len
> + mkfs.ext4 /dev/pmem5 -b 4096
> mke2fs 1.43.4 (31-Jan-2017)
> Creating filesystem with 16384 4k blocks and 16384 inodes
>
> Allocating group tables: 0/1^H^H^H ^H^H^Hdone
> Writing inode tables: 0/1^H^H^H ^H^H^Hdone
> Creating journal (1024 blocks): done
> Writing superblocks and filesystem accounting information:
> 0/1^H^H^H ^H^H^Hdone
>
> + mount /dev/pmem5 test_dax_mnt -o dax
> mount: wrong fs type, bad option, bad superblock on /dev/pmem5,
> missing codepage or helper program, or other error
>
> In some cases useful info is found in syslog - try
> dmesg | tail or so.
I'm unable to reproduce this with the 4.14-rc4 tag and latest ndctl
(pending branch - v58.2-10-gb95aa54). Are you able to reproduce this?
Are you able to create a raw pmem namespace manually, and mount it with
dax?
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2017-10-13 19:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 3:04 FAIL: dax-errors.sh failures on 4.14.0-rc4+ Cheng-mean Liu (SOCCER)
2017-10-13 19:28 ` Verma, Vishal L [this message]
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=1507922771.23025.99.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=linux-nvdimm@lists.01.org \
--cc=soccerl@microsoft.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.