From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: "hch@infradead.org" <hch@infradead.org>,
"dsterba@suse.cz" <dsterba@suse.cz>,
Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH 4/7] btrfs: Switch to iomap_dio_rw() for dio
Date: Tue, 26 May 2020 15:03:18 +0000 [thread overview]
Message-ID: <SN4PR0401MB35981C3BAEDA15CC85D13AE79BB00@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200522123837.1196-5-rgoldwyn@suse.de
Just as a heads up, this one gives me lot's of Page cache invalidation
failure prints from dio_warn_stale_pagecache() on btrfs/004 with
current misc-next:
[ 16.607545] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
[ 16.609328] File: /mnt/scratch/next/p0/d0/d77/de2/d5c/dc9/fee PID: 766 Comm: fsstress
[ 16.743572] BTRFS info (device zram1): disk space caching is enabled
[ 16.744620] BTRFS info (device zram1): has skinny extents
[ 16.747458] BTRFS info (device zram1): enabling ssd optimizations
[ 18.303877] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
[ 18.305476] File: /mnt/scratch/bgnoise/p0/d5/d53/d21/f27 PID: 2064 Comm: fsstress
[ 18.768426] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
[ 18.770074] File: /mnt/scratch/bgnoise/p0/d9/de/f15 PID: 2490 Comm: fsstress
[ 18.916118] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
[ 18.917843] File: /mnt/scratch/bgnoise/p0/f0 PID: 2694 Comm: fsstress
[ 21.170384] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
[ 21.172375] File: /mnt/scratch/bgnoise/p0/f3 PID: 4325 Comm: fsstress
[ 21.812452] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
[ 21.814232] File: /mnt/scratch/bgnoise/p0/fb PID: 5000 Comm: fsstress
[ 21.826027] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
[ 21.827741] File: /mnt/scratch/bgnoise/p0/fb PID: 5000 Comm: fsstress
[ 22.127966] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
[ 22.129413] File: /mnt/scratch/bgnoise/p0/df/d28/d26/f3b PID: 5196 Comm: fsstress
[ 22.160542] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
[ 22.161972] File: /mnt/scratch/bgnoise/p0/df/d10/d5f/f64 PID: 5196 Comm: fsstress
[ 23.696400] Page cache invalidation failure on direct I/O. Possible data corruption due to collision with buffered I/O!
[ 23.698115] File: /mnt/scratch/bgnoise/p0/f0 PID: 6562 Comm: fsstress
I have no idea yet why but I'm investigating.
next prev parent reply other threads:[~2020-05-26 15:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 12:38 [PATCH 0/7 v8] btrfs direct-io using iomap Goldwyn Rodrigues
2020-05-22 12:38 ` [PATCH 1/7] fs: Export generic_file_buffered_read() Goldwyn Rodrigues
2020-05-25 12:25 ` David Sterba
2020-05-22 12:38 ` [PATCH 2/7] iomap: add a filesystem hook for direct I/O bio submission Goldwyn Rodrigues
2020-05-22 12:38 ` [PATCH 3/7] iomap: Remove lockdep_assert_held() Goldwyn Rodrigues
2020-05-28 15:40 ` Darrick J. Wong
2020-05-28 16:45 ` Goldwyn Rodrigues
2020-05-22 12:38 ` [PATCH 4/7] btrfs: Switch to iomap_dio_rw() for dio Goldwyn Rodrigues
2020-05-26 15:03 ` Johannes Thumshirn [this message]
2020-05-26 16:44 ` Goldwyn Rodrigues
2020-05-28 15:13 ` Filipe Manana
2020-05-28 16:34 ` Goldwyn Rodrigues
2020-05-28 16:45 ` Filipe Manana
2020-05-28 18:38 ` Goldwyn Rodrigues
2020-06-03 11:35 ` Filipe Manana
2020-06-05 15:17 ` Filipe Manana
2020-06-05 20:43 ` Goldwyn Rodrigues
2020-06-06 9:57 ` Filipe Manana
2020-06-08 15:39 ` Goldwyn Rodrigues
2020-05-22 12:38 ` [PATCH 5/7] fs: Remove dio_end_io() Goldwyn Rodrigues
2020-05-22 12:38 ` [PATCH 6/7] btrfs: remove BTRFS_INODE_READDIO_NEED_LOCK Goldwyn Rodrigues
2020-05-22 12:38 ` [PATCH 7/7] btrfs: btrfs: split btrfs_direct_IO Goldwyn Rodrigues
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=SN4PR0401MB35981C3BAEDA15CC85D13AE79BB00@SN4PR0401MB3598.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=dsterba@suse.cz \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rgoldwyn@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).