fsc option is ignored when trying to use cachefilesd on ubuntu 18.04How do I speed up and cache mmap file access over NFS on Linux?Using TCP protocol for NFS mount points on linux serversHow slow can be a QCOW2 vm disk (proxmox/KVM) over NFS (dedicated 1Gbit)?PHP Application with Web Root on Amazon EFS using up too much EFS bandwidthChange Ubuntu 18.04 Plymouth ColorUbuntu 18.04 - Mount NFS with FQDN not resolving addressUbuntu 18.04, NFS mount over VPN goes stale, requires manual re-mountmysql.service location on Ubuntu 18.04 server?AWS Ubuntu 18.04 Change Nameserver?Ubuntu 18.04 strange behaviour of date with --date option
Two (probably) equal real numbers which are not proved to be equal?
Was Mohammed the most popular first name for boys born in Berlin in 2018?
Names of the Six Tastes
Pre-1993 comic in which Wolverine's claws were turned to rubber?
TeX Gyre Pagella Math Integral sign much too small
Is it safe to keep the GPU on 100% utilization for a very long time?
Why did they wait for Quill to arrive?
Do Monks gain the 9th level Unarmored Movement benefit when wearing armor or using a shield?
Can the president of the United States be guilty of insider trading?
I might have messed up in the 'Future Work' section of my thesis
Why did Missandei say this?
Identity of a supposed anonymous referee revealed through "Description" of the report
How did Captain Marvel know where to find these characters?
Has everyone forgotten about wildfire?
What is a good way to allow only one non null field in an object
Was there a contingency plan in place if Little Boy failed to detonate?
Is it a good idea to copy a trader when investing?
My perfect evil overlord plan... or is it?
What's the difference between "ricochet" and "bounce"?
Why does the electron wavefunction not collapse within atoms at room temperature in gas, liquids or solids due to decoherence?
Narcissistic cube asks who are we?
How do I minimise waste on a flight?
How to avoid making self and former employee look bad when reporting on fixing former employee's work?
Company stopped paying my salary. What are my options?
fsc option is ignored when trying to use cachefilesd on ubuntu 18.04
How do I speed up and cache mmap file access over NFS on Linux?Using TCP protocol for NFS mount points on linux serversHow slow can be a QCOW2 vm disk (proxmox/KVM) over NFS (dedicated 1Gbit)?PHP Application with Web Root on Amazon EFS using up too much EFS bandwidthChange Ubuntu 18.04 Plymouth ColorUbuntu 18.04 - Mount NFS with FQDN not resolving addressUbuntu 18.04, NFS mount over VPN goes stale, requires manual re-mountmysql.service location on Ubuntu 18.04 server?AWS Ubuntu 18.04 Change Nameserver?Ubuntu 18.04 strange behaviour of date with --date option
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I'm trying to set up cachefilesd on an nfs share with one of my servers. It's not working.
The service is running, my drives are mounted, but it seems as if the "fsc" option is completely ignored.
My fstab (specific folder-names edited for privacy and relevancy):
$ cat /etc/fstab
# <device> <dir> <type> <options> <dump> <fsck>
UUID=c456dea4-e0c6-42f5-a206-d0ed2e94bc6a / ext4 rw,relatime,discard,data=ordered 0 1
UUID=693dee2e-78bb-4d4d-84e4-082328488cfe /boot ext4 rw,relatime,discard,data=ordered 0 2
UUID=843c20a9-258a-4078-bb78-0549217623e4 none swap defaults 0 0
192.168.200.20:/mnt/tank/share1 /mnt/share1 nfs4 nolock,noatime,context="system_u:object_r:httpd_sys_content_rw_t:s0" 0 0
192.168.200.20:/mnt/tank/share2 /mnt/sub/share2 nfs4 fsc,nolock,noatime 0 0
192.168.200.20:/mnt/tank/share3 /mnt/sub/share3 nfs4 nolock,noatime 0 0
192.168.200.20:/mnt/tank/share4 /mnt/sub/share4 nfs4 fsc,nolock,noatime 0 0
The Problem
No matter what I do, even mounting the shares manually (mount -t -o fsc...) the FSC option is not enabled:
$ cat /proc/fs/nfsfs/volumes
NV SERVER PORT DEV FSID FSC
v4 c0a8c814 801 0:55 c7d8b1ef:bb64cbde no
v4 c0a8c814 801 0:54 d9a63e22:cc9a3fde no
v4 c0a8c814 801 0:57 5a567c31:75f052de no
v4 c0a8c814 801 0:59 1673eeb4:b0583de no
v4 c0a8c814 801 0:60 9acb69e2:fb267bde no
v4 c0a8c814 801 0:58 a367662d:5b53a6de no
v4 c0a8c814 801 0:61 69fdc16c:c38e18de no
v4 c0a8c814 801 0:63 706408fe:60f412de no
v4 c0a8c814 801 0:64 af123987:8f7131de no
And looking at nfsstat you can see that the fsc option was totally ignored:
$ nfsstat -m
/mnt/sub/share4 from 192.168.200.20:/mnt/tank/share4
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/sub/share3 from 192.168.200.20:/mnt/tank/share3
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/share1 from 192.168.200.20:/mnt/tank/share1
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/sub/share2 from 192.168.200.20:/mnt/tank/share2
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
Troubleshooting info
Service is running:
$ sudo systemctl status cachefilesd.service
● cachefilesd.service - LSB: CacheFiles daemon
Loaded: loaded (/etc/init.d/cachefilesd; generated)
Active: active (running) since Tue 2019-04-30 04:05:28 UTC; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 21405 ExecStop=/etc/init.d/cachefilesd stop (code=exited, status=0/SUCCESS)
Process: 22001 ExecStart=/etc/init.d/cachefilesd start (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/cachefilesd.service
└─22022 /sbin/cachefilesd
Apr 30 04:05:28 orochi systemd[1]: Starting LSB: CacheFiles daemon...
Apr 30 04:05:28 orochi cachefilesd[22001]: * Starting FilesCache daemon cachefilesd
Apr 30 04:05:28 orochi cachefilesd[22020]: About to bind cache
Apr 30 04:05:28 orochi cachefilesd[22020]: Bound cache
Apr 30 04:05:28 orochi cachefilesd[22022]: Daemon Started
Apr 30 04:05:28 orochi cachefilesd[22001]: ...done.
Apr 30 04:05:28 orochi systemd[1]: Started LSB: CacheFiles daemon.
the RUN=yes option is uncommented:
$ cat /etc/default/cachefilesd
# Defaults for cachefilesd initscript
# sourced by /etc/init.d/cachefilesd
# You must uncomment the run=yes line below for cachefilesd to start.
# Before doing so, please read /usr/share/doc/cachefilesd/howto.txt.gz as
# extended user attributes need to be enabled on the cache filesystem.
RUN=yes
# Additional options that are passed to the Daemon.
DAEMON_OPTS=""
The secctx system_u:system_r:cachefiles_kernel_t:s0 option is uncomented (tried it both with and without):
$ cat /etc/cachefilesd.conf
###############################################################################
#
# Copyright (C) 2006,2010 Red Hat, Inc. All Rights Reserved.
# Written by David Howells (dhowells@redhat.com)
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version
# 2 of the License, or (at your option) any later version.
#
###############################################################################
dir /var/cache/fscache
tag mycache
brun 10%
bcull 7%
bstop 3%
frun 10%
fcull 7%
fstop 3%
# Assuming you're using SELinux with the default security policy included in
# this package
secctx system_u:system_r:cachefiles_kernel_t:s0
In a similar but ultimately unhelpful answer someone also included the output of this:
$ lsmod | grep cachefiles
cachefiles 45056 1
fscache 61440 3 cachefiles,nfsv4,nfs
and this:
$ grep CONFIG_NFS_FSCACHE /boot/config-4.15.0-20-generic
CONFIG_NFS_FSCACHE=y
nfs cache ubuntu-18.04 nfs4
add a comment |
I'm trying to set up cachefilesd on an nfs share with one of my servers. It's not working.
The service is running, my drives are mounted, but it seems as if the "fsc" option is completely ignored.
My fstab (specific folder-names edited for privacy and relevancy):
$ cat /etc/fstab
# <device> <dir> <type> <options> <dump> <fsck>
UUID=c456dea4-e0c6-42f5-a206-d0ed2e94bc6a / ext4 rw,relatime,discard,data=ordered 0 1
UUID=693dee2e-78bb-4d4d-84e4-082328488cfe /boot ext4 rw,relatime,discard,data=ordered 0 2
UUID=843c20a9-258a-4078-bb78-0549217623e4 none swap defaults 0 0
192.168.200.20:/mnt/tank/share1 /mnt/share1 nfs4 nolock,noatime,context="system_u:object_r:httpd_sys_content_rw_t:s0" 0 0
192.168.200.20:/mnt/tank/share2 /mnt/sub/share2 nfs4 fsc,nolock,noatime 0 0
192.168.200.20:/mnt/tank/share3 /mnt/sub/share3 nfs4 nolock,noatime 0 0
192.168.200.20:/mnt/tank/share4 /mnt/sub/share4 nfs4 fsc,nolock,noatime 0 0
The Problem
No matter what I do, even mounting the shares manually (mount -t -o fsc...) the FSC option is not enabled:
$ cat /proc/fs/nfsfs/volumes
NV SERVER PORT DEV FSID FSC
v4 c0a8c814 801 0:55 c7d8b1ef:bb64cbde no
v4 c0a8c814 801 0:54 d9a63e22:cc9a3fde no
v4 c0a8c814 801 0:57 5a567c31:75f052de no
v4 c0a8c814 801 0:59 1673eeb4:b0583de no
v4 c0a8c814 801 0:60 9acb69e2:fb267bde no
v4 c0a8c814 801 0:58 a367662d:5b53a6de no
v4 c0a8c814 801 0:61 69fdc16c:c38e18de no
v4 c0a8c814 801 0:63 706408fe:60f412de no
v4 c0a8c814 801 0:64 af123987:8f7131de no
And looking at nfsstat you can see that the fsc option was totally ignored:
$ nfsstat -m
/mnt/sub/share4 from 192.168.200.20:/mnt/tank/share4
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/sub/share3 from 192.168.200.20:/mnt/tank/share3
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/share1 from 192.168.200.20:/mnt/tank/share1
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/sub/share2 from 192.168.200.20:/mnt/tank/share2
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
Troubleshooting info
Service is running:
$ sudo systemctl status cachefilesd.service
● cachefilesd.service - LSB: CacheFiles daemon
Loaded: loaded (/etc/init.d/cachefilesd; generated)
Active: active (running) since Tue 2019-04-30 04:05:28 UTC; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 21405 ExecStop=/etc/init.d/cachefilesd stop (code=exited, status=0/SUCCESS)
Process: 22001 ExecStart=/etc/init.d/cachefilesd start (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/cachefilesd.service
└─22022 /sbin/cachefilesd
Apr 30 04:05:28 orochi systemd[1]: Starting LSB: CacheFiles daemon...
Apr 30 04:05:28 orochi cachefilesd[22001]: * Starting FilesCache daemon cachefilesd
Apr 30 04:05:28 orochi cachefilesd[22020]: About to bind cache
Apr 30 04:05:28 orochi cachefilesd[22020]: Bound cache
Apr 30 04:05:28 orochi cachefilesd[22022]: Daemon Started
Apr 30 04:05:28 orochi cachefilesd[22001]: ...done.
Apr 30 04:05:28 orochi systemd[1]: Started LSB: CacheFiles daemon.
the RUN=yes option is uncommented:
$ cat /etc/default/cachefilesd
# Defaults for cachefilesd initscript
# sourced by /etc/init.d/cachefilesd
# You must uncomment the run=yes line below for cachefilesd to start.
# Before doing so, please read /usr/share/doc/cachefilesd/howto.txt.gz as
# extended user attributes need to be enabled on the cache filesystem.
RUN=yes
# Additional options that are passed to the Daemon.
DAEMON_OPTS=""
The secctx system_u:system_r:cachefiles_kernel_t:s0 option is uncomented (tried it both with and without):
$ cat /etc/cachefilesd.conf
###############################################################################
#
# Copyright (C) 2006,2010 Red Hat, Inc. All Rights Reserved.
# Written by David Howells (dhowells@redhat.com)
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version
# 2 of the License, or (at your option) any later version.
#
###############################################################################
dir /var/cache/fscache
tag mycache
brun 10%
bcull 7%
bstop 3%
frun 10%
fcull 7%
fstop 3%
# Assuming you're using SELinux with the default security policy included in
# this package
secctx system_u:system_r:cachefiles_kernel_t:s0
In a similar but ultimately unhelpful answer someone also included the output of this:
$ lsmod | grep cachefiles
cachefiles 45056 1
fscache 61440 3 cachefiles,nfsv4,nfs
and this:
$ grep CONFIG_NFS_FSCACHE /boot/config-4.15.0-20-generic
CONFIG_NFS_FSCACHE=y
nfs cache ubuntu-18.04 nfs4
add a comment |
I'm trying to set up cachefilesd on an nfs share with one of my servers. It's not working.
The service is running, my drives are mounted, but it seems as if the "fsc" option is completely ignored.
My fstab (specific folder-names edited for privacy and relevancy):
$ cat /etc/fstab
# <device> <dir> <type> <options> <dump> <fsck>
UUID=c456dea4-e0c6-42f5-a206-d0ed2e94bc6a / ext4 rw,relatime,discard,data=ordered 0 1
UUID=693dee2e-78bb-4d4d-84e4-082328488cfe /boot ext4 rw,relatime,discard,data=ordered 0 2
UUID=843c20a9-258a-4078-bb78-0549217623e4 none swap defaults 0 0
192.168.200.20:/mnt/tank/share1 /mnt/share1 nfs4 nolock,noatime,context="system_u:object_r:httpd_sys_content_rw_t:s0" 0 0
192.168.200.20:/mnt/tank/share2 /mnt/sub/share2 nfs4 fsc,nolock,noatime 0 0
192.168.200.20:/mnt/tank/share3 /mnt/sub/share3 nfs4 nolock,noatime 0 0
192.168.200.20:/mnt/tank/share4 /mnt/sub/share4 nfs4 fsc,nolock,noatime 0 0
The Problem
No matter what I do, even mounting the shares manually (mount -t -o fsc...) the FSC option is not enabled:
$ cat /proc/fs/nfsfs/volumes
NV SERVER PORT DEV FSID FSC
v4 c0a8c814 801 0:55 c7d8b1ef:bb64cbde no
v4 c0a8c814 801 0:54 d9a63e22:cc9a3fde no
v4 c0a8c814 801 0:57 5a567c31:75f052de no
v4 c0a8c814 801 0:59 1673eeb4:b0583de no
v4 c0a8c814 801 0:60 9acb69e2:fb267bde no
v4 c0a8c814 801 0:58 a367662d:5b53a6de no
v4 c0a8c814 801 0:61 69fdc16c:c38e18de no
v4 c0a8c814 801 0:63 706408fe:60f412de no
v4 c0a8c814 801 0:64 af123987:8f7131de no
And looking at nfsstat you can see that the fsc option was totally ignored:
$ nfsstat -m
/mnt/sub/share4 from 192.168.200.20:/mnt/tank/share4
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/sub/share3 from 192.168.200.20:/mnt/tank/share3
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/share1 from 192.168.200.20:/mnt/tank/share1
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/sub/share2 from 192.168.200.20:/mnt/tank/share2
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
Troubleshooting info
Service is running:
$ sudo systemctl status cachefilesd.service
● cachefilesd.service - LSB: CacheFiles daemon
Loaded: loaded (/etc/init.d/cachefilesd; generated)
Active: active (running) since Tue 2019-04-30 04:05:28 UTC; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 21405 ExecStop=/etc/init.d/cachefilesd stop (code=exited, status=0/SUCCESS)
Process: 22001 ExecStart=/etc/init.d/cachefilesd start (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/cachefilesd.service
└─22022 /sbin/cachefilesd
Apr 30 04:05:28 orochi systemd[1]: Starting LSB: CacheFiles daemon...
Apr 30 04:05:28 orochi cachefilesd[22001]: * Starting FilesCache daemon cachefilesd
Apr 30 04:05:28 orochi cachefilesd[22020]: About to bind cache
Apr 30 04:05:28 orochi cachefilesd[22020]: Bound cache
Apr 30 04:05:28 orochi cachefilesd[22022]: Daemon Started
Apr 30 04:05:28 orochi cachefilesd[22001]: ...done.
Apr 30 04:05:28 orochi systemd[1]: Started LSB: CacheFiles daemon.
the RUN=yes option is uncommented:
$ cat /etc/default/cachefilesd
# Defaults for cachefilesd initscript
# sourced by /etc/init.d/cachefilesd
# You must uncomment the run=yes line below for cachefilesd to start.
# Before doing so, please read /usr/share/doc/cachefilesd/howto.txt.gz as
# extended user attributes need to be enabled on the cache filesystem.
RUN=yes
# Additional options that are passed to the Daemon.
DAEMON_OPTS=""
The secctx system_u:system_r:cachefiles_kernel_t:s0 option is uncomented (tried it both with and without):
$ cat /etc/cachefilesd.conf
###############################################################################
#
# Copyright (C) 2006,2010 Red Hat, Inc. All Rights Reserved.
# Written by David Howells (dhowells@redhat.com)
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version
# 2 of the License, or (at your option) any later version.
#
###############################################################################
dir /var/cache/fscache
tag mycache
brun 10%
bcull 7%
bstop 3%
frun 10%
fcull 7%
fstop 3%
# Assuming you're using SELinux with the default security policy included in
# this package
secctx system_u:system_r:cachefiles_kernel_t:s0
In a similar but ultimately unhelpful answer someone also included the output of this:
$ lsmod | grep cachefiles
cachefiles 45056 1
fscache 61440 3 cachefiles,nfsv4,nfs
and this:
$ grep CONFIG_NFS_FSCACHE /boot/config-4.15.0-20-generic
CONFIG_NFS_FSCACHE=y
nfs cache ubuntu-18.04 nfs4
I'm trying to set up cachefilesd on an nfs share with one of my servers. It's not working.
The service is running, my drives are mounted, but it seems as if the "fsc" option is completely ignored.
My fstab (specific folder-names edited for privacy and relevancy):
$ cat /etc/fstab
# <device> <dir> <type> <options> <dump> <fsck>
UUID=c456dea4-e0c6-42f5-a206-d0ed2e94bc6a / ext4 rw,relatime,discard,data=ordered 0 1
UUID=693dee2e-78bb-4d4d-84e4-082328488cfe /boot ext4 rw,relatime,discard,data=ordered 0 2
UUID=843c20a9-258a-4078-bb78-0549217623e4 none swap defaults 0 0
192.168.200.20:/mnt/tank/share1 /mnt/share1 nfs4 nolock,noatime,context="system_u:object_r:httpd_sys_content_rw_t:s0" 0 0
192.168.200.20:/mnt/tank/share2 /mnt/sub/share2 nfs4 fsc,nolock,noatime 0 0
192.168.200.20:/mnt/tank/share3 /mnt/sub/share3 nfs4 nolock,noatime 0 0
192.168.200.20:/mnt/tank/share4 /mnt/sub/share4 nfs4 fsc,nolock,noatime 0 0
The Problem
No matter what I do, even mounting the shares manually (mount -t -o fsc...) the FSC option is not enabled:
$ cat /proc/fs/nfsfs/volumes
NV SERVER PORT DEV FSID FSC
v4 c0a8c814 801 0:55 c7d8b1ef:bb64cbde no
v4 c0a8c814 801 0:54 d9a63e22:cc9a3fde no
v4 c0a8c814 801 0:57 5a567c31:75f052de no
v4 c0a8c814 801 0:59 1673eeb4:b0583de no
v4 c0a8c814 801 0:60 9acb69e2:fb267bde no
v4 c0a8c814 801 0:58 a367662d:5b53a6de no
v4 c0a8c814 801 0:61 69fdc16c:c38e18de no
v4 c0a8c814 801 0:63 706408fe:60f412de no
v4 c0a8c814 801 0:64 af123987:8f7131de no
And looking at nfsstat you can see that the fsc option was totally ignored:
$ nfsstat -m
/mnt/sub/share4 from 192.168.200.20:/mnt/tank/share4
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/sub/share3 from 192.168.200.20:/mnt/tank/share3
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/share1 from 192.168.200.20:/mnt/tank/share1
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
/mnt/sub/share2 from 192.168.200.20:/mnt/tank/share2
Flags: rw,noatime,vers=4.1,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.200.10,local_lock=none,addr=192.168.200.20
Troubleshooting info
Service is running:
$ sudo systemctl status cachefilesd.service
● cachefilesd.service - LSB: CacheFiles daemon
Loaded: loaded (/etc/init.d/cachefilesd; generated)
Active: active (running) since Tue 2019-04-30 04:05:28 UTC; 5min ago
Docs: man:systemd-sysv-generator(8)
Process: 21405 ExecStop=/etc/init.d/cachefilesd stop (code=exited, status=0/SUCCESS)
Process: 22001 ExecStart=/etc/init.d/cachefilesd start (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 4915)
CGroup: /system.slice/cachefilesd.service
└─22022 /sbin/cachefilesd
Apr 30 04:05:28 orochi systemd[1]: Starting LSB: CacheFiles daemon...
Apr 30 04:05:28 orochi cachefilesd[22001]: * Starting FilesCache daemon cachefilesd
Apr 30 04:05:28 orochi cachefilesd[22020]: About to bind cache
Apr 30 04:05:28 orochi cachefilesd[22020]: Bound cache
Apr 30 04:05:28 orochi cachefilesd[22022]: Daemon Started
Apr 30 04:05:28 orochi cachefilesd[22001]: ...done.
Apr 30 04:05:28 orochi systemd[1]: Started LSB: CacheFiles daemon.
the RUN=yes option is uncommented:
$ cat /etc/default/cachefilesd
# Defaults for cachefilesd initscript
# sourced by /etc/init.d/cachefilesd
# You must uncomment the run=yes line below for cachefilesd to start.
# Before doing so, please read /usr/share/doc/cachefilesd/howto.txt.gz as
# extended user attributes need to be enabled on the cache filesystem.
RUN=yes
# Additional options that are passed to the Daemon.
DAEMON_OPTS=""
The secctx system_u:system_r:cachefiles_kernel_t:s0 option is uncomented (tried it both with and without):
$ cat /etc/cachefilesd.conf
###############################################################################
#
# Copyright (C) 2006,2010 Red Hat, Inc. All Rights Reserved.
# Written by David Howells (dhowells@redhat.com)
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version
# 2 of the License, or (at your option) any later version.
#
###############################################################################
dir /var/cache/fscache
tag mycache
brun 10%
bcull 7%
bstop 3%
frun 10%
fcull 7%
fstop 3%
# Assuming you're using SELinux with the default security policy included in
# this package
secctx system_u:system_r:cachefiles_kernel_t:s0
In a similar but ultimately unhelpful answer someone also included the output of this:
$ lsmod | grep cachefiles
cachefiles 45056 1
fscache 61440 3 cachefiles,nfsv4,nfs
and this:
$ grep CONFIG_NFS_FSCACHE /boot/config-4.15.0-20-generic
CONFIG_NFS_FSCACHE=y
nfs cache ubuntu-18.04 nfs4
nfs cache ubuntu-18.04 nfs4
asked Apr 30 at 4:34
Tal BullTal Bull
11
11
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f965204%2ffsc-option-is-ignored-when-trying-to-use-cachefilesd-on-ubuntu-18-04%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f965204%2ffsc-option-is-ignored-when-trying-to-use-cachefilesd-on-ubuntu-18-04%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown