From: Xiubo Li <xiubli@redhat.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: idryomov@gmail.com, vshankar@redhat.com, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] ceph: do not truncate pagecache if truncate size doesn't change
Date: Fri, 19 Nov 2021 12:33:50 +0800 [thread overview]
Message-ID: <7e2280b9-c20b-d770-4144-be44a03ec653@redhat.com> (raw)
In-Reply-To: <1a6b7a20-ba30-0b57-3927-2b61ad64be28@redhat.com>
[...]
> 3540 trunc from 0x789289 to 0xd8b1
> 3542 write 0x8571af thru 0x85e2af (0x7101 bytes)
> 3543 trunc from 0x85e2b0 to 0x7dc986
> 3550 read 0x3b37bd thru 0x3b50a8 (0x18ec bytes)
> 3551 mapread 0x686907 thru 0x693eb9 (0xd5b3 bytes)
> READ BAD DATA: offset = 0x686907, size = 0xd5b3, fname = 112.2
> OFFSET GOOD BAD RANGE
> 0x686907 0x0000 0x198f 0x00000
> operation# (mod 256) for the bad data may be 143
> 0x686908 0x0000 0x8fec 0x00001
> operation# (mod 256) for the bad data may be 143
>
> In theory that range should be truncated and zeroed in the first
> "trunc" from 0x789289 to 0xd8b1 above. From the failure logs, it is
> the same issue with before in generic/057 test case. But locally I
s/057/075/
> couldn't reproduce it after I fixing the bug in ceph fsize_support
> branch.
>
> BTW, could you reproduce this every time ? Or just occasionally ?
>
[...]
next prev parent reply other threads:[~2021-11-19 4:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 9:20 [PATCH] ceph: do not truncate pagecache if truncate size doesn't change xiubli
2021-11-16 20:06 ` Jeff Layton
2021-11-17 1:21 ` Xiubo Li
2021-11-17 13:28 ` Jeff Layton
2021-11-17 13:40 ` Xiubo Li
2021-11-17 13:50 ` Jeff Layton
2021-11-17 15:06 ` Jeff Layton
2021-11-18 2:38 ` Xiubo Li
2021-11-18 12:19 ` Jeff Layton
2021-11-19 2:20 ` Xiubo Li
2021-11-17 2:47 ` Yan, Zheng
2021-11-17 4:19 ` Xiubo Li
2021-11-17 21:10 ` Jeff Layton
2021-11-18 4:46 ` Xiubo Li
2021-11-18 9:59 ` Xiubo Li
[not found] ` <09babbaf077a76ace4793f2e6ae6127d2e7d6411.camel@kernel.org>
2021-11-19 4:29 ` Xiubo Li
2021-11-19 4:33 ` Xiubo Li [this message]
2021-11-19 11:59 ` Jeff Layton
2021-11-20 0:58 ` Xiubo Li
2021-11-22 19:10 ` Jeff Layton
2021-11-23 1:00 ` Xiubo Li
2021-11-23 8:06 ` Xiubo Li
2021-11-23 3:11 ` Xiubo Li
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=7e2280b9-c20b-d770-4144-be44a03ec653@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=vshankar@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.