Rince <rincebrain@xxxxxxxxx> wrote: > # cat /proc/fs/nfsfs/* > NV SERVER PORT USE HOSTNAME > v4 80dc463e 801 12 mant1 > NV SERVER PORT DEV FSID FSC > v4 80dc463e 801 0:19 9eab9d085c14652a no > v4 80dc463e 801 0:22 c8654208da0d3669 no > v4 80dc463e 801 0:20 212b2508ae922d14 no > v4 80dc463e 801 0:21 f0b58c08259e50c5 no > v4 80dc463e 801 0:23 cd9b8d087773ec8f no > v4 80dc463e 801 0:24 ef1fea0808113729 no > v4 80dc463e 801 0:25 138c1408eb63c29c no > v4 80dc463e 801 0:26 f0bc74085499dbc1 no > v4 80dc463e 801 0:27 4c0fa308cfa9eacf no > v4 80dc463e 801 0:28 84d624087111280d no > v4 80dc463e 801 0:29 a053d5083534c623 no > v4 80dc463e 801 0:30 2295d1089ac79a7c no I think that the problem you're seeing is one I'm also seeing. A patch went into the latest round of kernels that breaks fscache for NFS because the 'fsc' flag isn't inherited across automount points. What happened is that the lookup for mount is now done differently, and so the 'fsc' option is only applied to the '/' volume from the server, and not any other volume under that. I should have a patch for you to try shortly. David -- Linux-cachefs mailing list Linux-cachefs@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cachefs
