From: Christoph Hellwig <hch@lst.de>
To: "J. Hart" <jfhart085@gmail.com>
Cc: linux-nvme@lists.infradead.org, kbusch@kernel.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: Thu, 15 Dec 2022 09:23:44 +0100 [thread overview]
Message-ID: <20221215082344.GB3816@lst.de> (raw)
In-Reply-To: <fe013f52-ac3c-4be2-6f1e-e68fea46e4c2@gmail.com>
On Thu, Dec 15, 2022 at 10:38:33AM +0900, J. Hart wrote:
> I am attempting to load an nvme device (nvme0n1) to use as main system
> drive using the following command:
>
> rsync -axvH /. --exclude=/lost+found --exclude=/var/log.bu
> --exclude=/usr/var/log.bu --exclude=/usr/X11R6/var/log.bu
> --exclude=/home/jhart/.cache/mozilla/firefox/are7uokl.default-release/cache2.bu
> --exclude=/home/jhart/.cache/thunderbird/7zsnqnss.default/cache2.bu
> /mnt/root_new 2>&1 | tee root.log
>
> The total transfer would be approximately 50 GB. This is being done at run
> level 1, and only the kernel threads and the root shell are observed to be
> active.
>
> The following log messages appear after a minute or so, and rsync hangs.
> The nvme drive cannot be unmounted without a reboot.
Ok, this looks like the driver has firmware / hardware problems and
can't copy wit hthe load.
>
> dmesg reports the following:
nvme0 is the destination driver I guess?
>
> [Dec14 19:24] nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting
Can you enable CONFIG_NVME_VERBOSE_ERRORS so that we can see what
commands are hanging?
> I have also observed file system corruption on the source drive of the
> transfer. I would not normally think this to be related, except that after
> the first time I observed it, I made certain that I corrected the file
> content before any additional attempts, but have seen this again after
> every attempt. The modification dates and file sizes did not change, but
> the file content on the source drive did. I confirmed this using the
> "diff" utility, and again using a rsync dry run with the check sum test
> enabled.
Ok, that's really odd. The only way I could think of that happening
is if the driver does stay DMAs, which would be really grave.
Do you have CONFIG_INTEL_IOMMU and CONFIG_INTEL_IOMMU_DEFAULT_ON enabled?
If not, it would be good to enable those to see if the iommu catches
any stray DMAs.
next prev parent reply other threads:[~2022-12-15 8:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 1:38 nvme nvme0: I/O 0 (I/O Cmd) QID 1 timeout, aborting, source drive corruption observed J. Hart
2022-12-15 8:23 ` Christoph Hellwig [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2022-12-17 12:07 J. Hart
2022-12-17 15:07 J. Hart
2022-12-17 16:14 J. Hart
2022-12-17 21:57 J. Hart
2022-12-18 6:20 J. Hart
2022-12-18 12:08 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
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=20221215082344.GB3816@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=jfhart085@gmail.com \
--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