From: jim@thebergstens.com (James R. Bergsten)
Subject: [PATCH v2] nvme-user: Minor enhancement and fixes
Date: Fri, 5 Dec 2014 08:48:50 -0800 [thread overview]
Message-ID: <35e501d010ab$5c5068d0$14f13a70$@thebergstens.com> (raw)
In-Reply-To: <37D709DA9AEECD448AE8DD01BDD193F7ED8E2D@NTXBOIMBX02.micron.com>
Were it me, I'd start over. Power cycle, use the VS tool, then use whatever
Linux-dist-standard GUI thingy you have to do a FILESYSTEM format and then a
mount on /dev/nvme0n1. That ought to work.
Good luck.
Jim B.
-----Original Message-----
From: Linux-nvme [mailto:linux-nvme-bounces@lists.infradead.org] On Behalf
Of Zakaria Abushima (zabushima)
Sent: Friday, December 5, 2014 8:41 AM
To: Keith Busch; Swati C
Cc: linux-nvme at lists.infradead.org
Subject: RE: [PATCH v2] nvme-user: Minor enhancement and fixes
Hi Keith and Swati,
I have used my vendor specific tool to create namespace and managed to
create it,
It doesn't appear in GUI as a file system where I can save things in but in
/dev/ it lists nvme0 and nvme0n1
So I thought I might need to format it ? then I have used your tool
nvme-format-ns and formatted the namespace ?
Nothing success and says icotl interrupted.
and then I thought that I might need to mount it ? I used linux built-in
mount function as following:- mount /dev/nvme0n1
Since then the nvme0 and nvme0n1 disappeared and when I call lspci -v I
noticed slight change, which is the " module driver in use nvme0" line has
disappeared ? when it use to appear ?
Any idear or help
Thanks a in advance.
Zakaria.
-----Original Message-----
From: Linux-nvme [mailto:linux-nvme-bounces@lists.infradead.org] On Behalf
Of Keith Busch
Sent: 01 December 2014 15:46
To: Swati C
Cc: linux-nvme at lists.infradead.org
Subject: Re: [PATCH v2] nvme-user: Minor enhancement and fixes
On Fri, 28 Nov 2014, Swati C wrote:
> Addressing comments from -
> [PATCH] nvme-user: Minor enhancement and fixes
> (http://lists.infradead.org/pipermail/linux-nvme/2014-November/001214.
> html)
>
> Minor enhancements to nvme_format_ns.c
> - Make Metadata Settings a user settable value.
> - Support for Secure Erase Settings.
>
> Signed-off-by: Swati C <s.chawdhary at samsung.com>
Thanks, applied.
On a side note, some people asked if I could take the example programs here
and turn it into something more useful with just one program to run all nvme
instead of a bunch of stand-alone programs. I took a stab at it:
http://git.infradead.org/users/kbusch/linux-nvme-cli.git
It's still a work in progress, but just linking here in case others have
ideas or find it useful too.
_______________________________________________
Linux-nvme mailing list
Linux-nvme at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
_______________________________________________
Linux-nvme mailing list
Linux-nvme at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2014-12-05 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 13:50 [PATCH v2] nvme-user: Minor enhancement and fixes Swati C
2014-12-01 15:45 ` Keith Busch
2014-12-02 19:10 ` Linda Knippers
2014-12-02 19:32 ` Keith Busch
2014-12-05 16:40 ` Zakaria Abushima (zabushima)
2014-12-05 16:48 ` James R. Bergsten [this message]
2014-12-05 16:58 ` Keith Busch
2014-12-08 14:36 ` Zakaria Abushima (zabushima)
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='35e501d010ab$5c5068d0$14f13a70$@thebergstens.com' \
--to=jim@thebergstens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).