From: "J. Hart" <jfhart085@gmail.com>
To: linux-nvme@lists.infradead.org
Cc: axboe@fb.com, hch@lst.de, sagi@grimberg.me,
Keith Busch <kbusch@kernel.org>
Subject: Re: nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed
Date: Tue, 20 Dec 2022 23:04:57 +0900 [thread overview]
Message-ID: <c8dda53f-8a90-f6ba-7c51-c762bdfd2ef3@gmail.com> (raw)
In-Reply-To: <Y6B49qkgqmOmuLLC@kbusch-mbp.dhcp.thefacebook.com>
As I mentioned in an earlier note, I have updated the util-linux and
e2fsprogs packages to see if that makes any difference. The versions I
was using were rather old. As expected, it unfortunately did not help,
although it was a much needed update.
I am out of things to try.
My apologies for being rather a pest about this, but I was hoping I
wouldn't have to scrap the time and money I put into it. I'll leave you
all undisturbed and make no more requests of you.
With Thanks for your kind attention,
J. Hart
On 12/19/22 11:45 PM, Keith Busch wrote:
> On Sun, Dec 18, 2022 at 09:08:19PM +0900, J. Hart wrote:
>> Here are some consecutive fsck runs done on /dev/nvme0n1p3:
>>
>> -bash-3.2# fsck -f -C /dev/nvme0n1p2
>
> I'm having some trouble following some of this. You mentioned nvme0n1p3
> corruption, but then show nvme0n1p2 instead. Could you possibly relay
> your recreation steps starting from a freshly formatted nvme drive?
> Partition setup, device mappers, filesystems, mount options, etc.?
next prev parent reply other threads:[~2022-12-20 14:05 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
2022-12-20 14:04 ` J. Hart [this message]
-- 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=c8dda53f-8a90-f6ba-7c51-c762bdfd2ef3@gmail.com \
--to=jfhart085@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--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