nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed

[J. Hart]

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.

The 50 GB transfer was to partition 3 (/dev/nvme0n1p3)

The consecutive fsck runs in the previous message were to the 64 MB 
partition 2 (/dev/nvme0n1p2).

I am presently updating the util-linux and e2fsprogs packages to see if 
that makes any difference.  The versions I was using were rather old.

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.?