Bug#876432: cryfs: does not honor noatime mount option
Thanks for reporting. This is due to fuse not passing through the noatime parameter to the filesystem implementation, so CryFS can't figure out whether noatime is enabled or not. However, to alleviate the problem a bit, the default behavior of CryFS will be switched from strictatime to relatime in the upcoming 0.10 release series. On 22/09/17 08:56, Kiko Piris wrote: Package: cryfs Version: 0.9.7-2 Severity: normal If the cryfs filesystem is mounted with noatime, it should not modify files’ access times when they are read: $ mount | grep cryfs cryfs@/home/kiko/Dropbox/safe/.cryfs on /home/kiko/Dropbox.safe type fuse.cryfs (rw,nosuid,nodev,noatime,user_id=1000,group_id=1000,allow_other) ^^^ $ stat Dropbox.safe/.placeholder File: Dropbox.safe/.placeholder Size: 60 Blocks: 0 IO Block: 16384 regular file Device: 2fh/47d Inode: 41 Links: 1 Access: (0600/-rw---) Uid: ( 1000/kiko) Gid: ( 1000/kiko) Access: 2017-09-22 09:30:51.261363123 +0200 ^^^ Modify: 2010-06-10 10:38:53.0 +0200 Change: 2017-09-20 19:17:16.072335331 +0200 Birth: - $ cat Dropbox.safe/.placeholder # DO NOT EDIT OR REMOVE # This file is a simple placeholder $ stat Dropbox.safe/.placeholder File: Dropbox.safe/.placeholder Size: 60 Blocks: 0 IO Block: 16384 regular file Device: 2fh/47d Inode: 41 Links: 1 Access: (0600/-rw---) Uid: ( 1000/kiko) Gid: ( 1000/kiko) Access: 2017-09-22 09:48:34.843560115 +0200 ^^^ Modify: 2010-06-10 10:38:53.0 +0200 Change: 2017-09-20 19:17:16.072335331 +0200 Birth: - Obviously, the corresponding block file in the encrypted directory also gets modified (and needlesly synced to Dropbox). Thanks.
Bug#876432: cryfs: does not honor noatime mount option
Package: cryfs Version: 0.9.7-2 Severity: normal If the cryfs filesystem is mounted with noatime, it should not modify files’ access times when they are read: $ mount | grep cryfs cryfs@/home/kiko/Dropbox/safe/.cryfs on /home/kiko/Dropbox.safe type fuse.cryfs (rw,nosuid,nodev,noatime,user_id=1000,group_id=1000,allow_other) ^^^ $ stat Dropbox.safe/.placeholder File: Dropbox.safe/.placeholder Size: 60 Blocks: 0 IO Block: 16384 regular file Device: 2fh/47d Inode: 41 Links: 1 Access: (0600/-rw---) Uid: ( 1000/kiko) Gid: ( 1000/kiko) Access: 2017-09-22 09:30:51.261363123 +0200 ^^^ Modify: 2010-06-10 10:38:53.0 +0200 Change: 2017-09-20 19:17:16.072335331 +0200 Birth: - $ cat Dropbox.safe/.placeholder # DO NOT EDIT OR REMOVE # This file is a simple placeholder $ stat Dropbox.safe/.placeholder File: Dropbox.safe/.placeholder Size: 60 Blocks: 0 IO Block: 16384 regular file Device: 2fh/47d Inode: 41 Links: 1 Access: (0600/-rw---) Uid: ( 1000/kiko) Gid: ( 1000/kiko) Access: 2017-09-22 09:48:34.843560115 +0200 ^^^ Modify: 2010-06-10 10:38:53.0 +0200 Change: 2017-09-20 19:17:16.072335331 +0200 Birth: - Obviously, the corresponding block file in the encrypted directory also gets modified (and needlesly synced to Dropbox). Thanks. -- Kiko -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages cryfs depends on: ii fuse 2.9.7-1 ii libc6 2.24-17 ii libcrypto++6 5.6.4-8 ii libcurl3 7.55.1-1 ii libfuse2 2.9.7-1 ii libgcc1 1:7.2.0-6 ii libstdc++67.2.0-6 cryfs recommends no packages. cryfs suggests no packages. -- no debconf information
