On Thu, Sep 21, 2017 at 11:00 PM, 陶冬冬 <tdd21151186@xxxxxxxxx> wrote: > sorry, i don’t have the detail log that could show if the mds has revoked the cap successful > > i have done “echo 1 > /proc/sys/vm/drop_caches”, and after that the client can read the latest data. > > i have tried “ceph +p > /sys/kernel/debug/dynamic_debug/control” to enable the kernel log. > but where can i find the ceph log ? > > could you please show me the code path that directly operate on page cache without checking CEPH_CAP_FILE_CACHE in kernel 3.10 ? > splice_read, splice_write and readahead > Thanks, > Dongdong > >> 在 2017年9月21日，下午10:38，Yan, Zheng <ukernel@xxxxxxxxx> 写道： >> >> On Thu, Sep 21, 2017 at 8:25 PM, 陶冬冬 <tdd21151186@xxxxxxxxx> wrote: >>> >>> thanks zheng, >>> >>> that issue happened again today. >>> and from the log, client A write one file, but the mds didn’t revoke the >>> CEPH_CAP_FILE_CACHE of the file from client B. >>> so that, when client B trying to read that file, client B just read it from >>> its page cache which has the old data. >> >> Are you sure that mds didn't revoke CEPH_CAP_FILE_CACHE? could you >> provide mds log. In old version kernel, there are code paths that >> operate directly on page cache, without checking if >> CEPH_CAP_FILE_CACHE is issued. >> >> Regards >> Yan, Zheng >> >> >>> >>> Regards, >>> Dongdong >>> >>> 在 2017年9月21日，下午8:00，Yan, Zheng <ukernel@xxxxxxxxx> 写道： >>> >>> On Wed, Sep 20, 2017 at 11:42 AM, 陶冬冬 <tdd21151186@xxxxxxxxx> wrote: >>> >>> Hi Zheng, >>> >>> we have been suffering from an inconsistent issue in cephfs : >>> >>> kernel version : 3.1.0 >>> ceph version: 10.2.5 >>> >>> we are using the kernel client to mount cephfs >>> we mount the ceph filesystem on two machines all with kernel 3.1.0, >>> but the strange thing is that the content of one same file is different from >>> the two machines. >>> and we are certain one machine has the correct content. >>> >>> we didn’t know the way to reproduce it , and we don’t have the log here. >>> i’m wondering maybe it’s because there is some bug within kernel client, so >>> that the client think >>> it has enough capability to read it just from it’s buffer, no need to get >>> the cap from mds, so it didn’t get the latest content. >>> >>> since the kernel is too old, may be you have fixed this kind inconsistent >>> issues ? >>> >>> >>> we fixed a splice issue about 1 year ago, it could cause inconsistent >>> data when multiples client read/write a file at the same time. The >>> issue the is the only bug I remember, that can cause inconsistent >>> data. Please try recent kernel, check if the issue still happen. >>> >>> Regards >>> Yan, Zheng >>> >>> >>> Regards, >>> Dongdong >>> >>> > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
