From: Keith Busch <kbusch@kernel.org>
To: "J. Hart" <jfhart085@gmail.com>
Cc: linux-nvme@lists.infradead.org, axboe@fb.com, hch@lst.de,
sagi@grimberg.me
Subject: Re: nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed
Date: Tue, 20 Dec 2022 11:10:42 -0700 [thread overview]
Message-ID: <Y6H6ogCyyWGHcbZ0@kbusch-mbp> (raw)
In-Reply-To: <f2b6305b-ffd5-51cf-74bd-de39d50c67dc@gmail.com>
On Tue, Dec 20, 2022 at 08:40:58AM +0900, J. Hart wrote:
> My apologies on that last, it was a typo. I should have said /dev/nvme0n1p2.
>
> There are two ext4 partitions on the nvme drive.
> One is /dev/nvme0n1p2, which is a 64 MB partition.
> The other is /dev/nvme0n1p3, which is the remainder of that 500GB drive.
And what about nvme0n1p1? What are the offsets and total sizes of these?
What is the logical block format size of your nvme namespace? I'm asking
because some drives are known to behave badly if access is not aligned
to its NAND page size. NVMe doesn't actually provide a way to know what
that size is, but if all partitions are aligned to a power of 2 at least
16k, then partition setup is probably fine.
next prev parent reply other threads:[~2022-12-20 18:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 12:08 nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed J. Hart
2022-12-19 14:45 ` Keith Busch
2022-12-19 23:40 ` J. Hart
2022-12-20 18:10 ` Keith Busch [this message]
2022-12-20 14:04 ` J. Hart
-- strict thread matches above, loose matches on Subject: below --
2022-12-18 6:20 J. Hart
2022-12-17 21:57 J. Hart
2022-12-17 16:14 J. Hart
2022-12-17 15:07 J. Hart
2022-12-17 12:07 J. Hart
2022-12-15 1:38 J. Hart
2022-12-15 8:23 ` Christoph Hellwig
2022-12-15 9:07 ` J. Hart
2022-12-15 9:09 ` Christoph Hellwig
2022-12-15 9:15 ` J. Hart
2022-12-15 13:33 ` J. Hart
2022-12-15 17:34 ` Keith Busch
2022-12-15 22:30 ` J. Hart
2022-12-16 6:39 ` Christoph Hellwig
2022-12-16 19:08 ` Keith Busch
2023-01-18 10:27 ` Mark Ruijter
2022-12-16 23:16 ` Keith Busch
2022-12-17 1:28 ` J. Hart
2022-12-19 14:41 ` Keith Busch
2022-12-20 1:10 ` J. Hart
2022-12-20 16:56 ` Keith Busch
2022-12-21 7:50 ` Christoph Hellwig
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=Y6H6ogCyyWGHcbZ0@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=jfhart085@gmail.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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