On Sun, Sep 27, 2020 at 3:54 PM Matthew Wilcox <willy@xxxxxxxxxxxxx> wrote: > > On Sun, Sep 27, 2020 at 03:48:39PM +0200, Sedat Dilek wrote: > > With your patch and assertion diff I hit the same issue like with Ext4-FS... > > > > [So Sep 27 15:40:18 2020] run fstests generic/095 at 2020-09-27 15:40:19 > > [So Sep 27 15:40:26 2020] XFS (sdb1): Mounting V5 Filesystem > > [So Sep 27 15:40:26 2020] XFS (sdb1): Ending clean mount > > [So Sep 27 15:40:26 2020] xfs filesystem being mounted at /mnt/scratch > > supports timestamps until 2038 (0x7fffffff) > > [So Sep 27 15:40:28 2020] Page cache invalidation failure on direct > > I/O. Possible data corruption due to collision with buffered I/O! > > [So Sep 27 15:40:28 2020] File: /mnt/scratch/file1 PID: 12 Comm: kworker/0:1 > > [So Sep 27 15:40:29 2020] Page cache invalidation failure on direct > > I/O. Possible data corruption due to collision with buffered I/O! > > [So Sep 27 15:40:29 2020] File: /mnt/scratch/file1 PID: 73 Comm: kworker/0:2 > > [So Sep 27 15:40:30 2020] Page cache invalidation failure on direct > > I/O. Possible data corruption due to collision with buffered I/O! > > [So Sep 27 15:40:30 2020] File: /mnt/scratch/file2 PID: 12 Comm: kworker/0:1 > > [So Sep 27 15:40:30 2020] Page cache invalidation failure on direct > > I/O. Possible data corruption due to collision with buffered I/O! > > [So Sep 27 15:40:30 2020] File: /mnt/scratch/file2 PID: 3271 Comm: fio > > [So Sep 27 15:40:30 2020] Page cache invalidation failure on direct > > I/O. Possible data corruption due to collision with buffered I/O! > > [So Sep 27 15:40:30 2020] File: /mnt/scratch/file2 PID: 3273 Comm: fio > > [So Sep 27 15:40:31 2020] Page cache invalidation failure on direct > > I/O. Possible data corruption due to collision with buffered I/O! > > [So Sep 27 15:40:31 2020] File: /mnt/scratch/file1 PID: 3308 Comm: fio > > [So Sep 27 15:40:36 2020] Page cache invalidation failure on direct > > I/O. Possible data corruption due to collision with buffered I/O! > > [So Sep 27 15:40:36 2020] File: /mnt/scratch/file1 PID: 73 Comm: kworker/0:2 > > [So Sep 27 15:40:43 2020] Page cache invalidation failure on direct > > I/O. Possible data corruption due to collision with buffered I/O! > > [So Sep 27 15:40:43 2020] File: /mnt/scratch/file1 PID: 73 Comm: kworker/0:2 > > [So Sep 27 15:40:52 2020] Page cache invalidation failure on direct > > I/O. Possible data corruption due to collision with buffered I/O! > > [So Sep 27 15:40:52 2020] File: /mnt/scratch/file2 PID: 73 Comm: kworker/0:2 > > [So Sep 27 15:40:56 2020] Page cache invalidation failure on direct > > I/O. Possible data corruption due to collision with buffered I/O! > > [So Sep 27 15:40:56 2020] File: /mnt/scratch/file2 PID: 12 Comm: kworker/0:1 > > > > Is that a different issue? > > The test is expected to emit those messages; userspace has done something > so utterly bonkers (direct I/O to an mmaped, mlocked page) that we can't > provide the normal guarantees of data integrity. Thanks for the explanations. Will run 25 iterations with your iomap patch and assertion-diff using XFS and your MKFS_OPTIONS="-m reflink=1,rmapbt=1 -i sparse=1 -b size=1024"... $ sudo ./check -i 25 generic/095 ...and report later. - Sedat -
