From: paul.grabinar@ranbarg.com (Paul Grabinar)
Subject: Partitions and end-to-end protection
Date: Mon, 13 Jul 2015 19:50:41 +0100 [thread overview]
Message-ID: <55A40881.5000108@ranbarg.com> (raw)
Hi All,
I've had a problem reported against the NVMe driver on the v4.1 kernel.
The user has formatted a namespace with 512 byte sectors, separate
buffer 8 byte meta-data and protection type 1.
That should all be okay, and indeed reads and writes work fine.
However, if a partition table is created in the namespace and then the
machine is rebooted, or the driver is unloaded and loaded, the
partitions don't appear again unless they are manually probed.
What seems to be happening is that the driver starts off by setting the
capacity to zero whilst it validates the meta-data configuration and
then sets the real size after this validation. However, setting the
capacity does not seem to be enough to tell the kernel to re-read the
partition table.
Anyone else seeing this?
Thanks,
Paul.
next reply other threads:[~2015-07-13 18:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 18:50 Paul Grabinar [this message]
2015-07-13 19:16 ` Partitions and end-to-end protection Keith Busch
2015-07-13 19:22 ` Paul Grabinar
2015-07-14 18:06 ` Christoph Hellwig
2015-07-14 18:13 ` Dan Williams
2015-07-14 18:15 ` Christoph Hellwig
2015-07-14 18:25 ` Dan Williams
2015-07-14 18:41 ` Martin K. Petersen
2015-07-14 18:43 ` Christoph Hellwig
2015-07-14 18:58 ` Martin K. Petersen
2015-07-14 19:25 ` Keith Busch
2015-07-14 19:38 ` Martin K. Petersen
2015-07-14 19:45 ` Keith Busch
2015-07-14 20:07 ` Martin K. Petersen
2015-07-14 20:14 ` Keith Busch
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=55A40881.5000108@ranbarg.com \
--to=paul.grabinar@ranbarg.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.