February 25, 201511 yr Unsure if this a docker issue or a BTRFS issue or something else altogether. I have a folding@home docker that stores its work units on a mechanical cache drive that is formatted BTRFS, as part of the operation of the docker it deletes a folder that held the last completed work unit. The log is showing Feb 25 15:49:40 Unraid-Nas shfs/user: shfs_rmdir: rmdir: /mnt/cache/appdata/fah/work/00 (39) Directory not empty Feb 25 15:49:40 Unraid-Nas shfs/user: shfs_rmdir: rmdir: /mnt/cache/appdata/fah/work/00 (39) Directory not empty Feb 25 15:50:40 Unraid-Nas shfs/user: shfs_rmdir: rmdir: /mnt/cache/appdata/fah/work/00 (39) Directory not empty Feb 25 15:52:18 Unraid-Nas shfs/user: shfs_rmdir: rmdir: /mnt/cache/appdata/fah/work/00 (39) Directory not empty and it's repeating a few more times as i'm typing this. the app inside the docker is running as nobody, the files and folders it creates are owned by nobody:users , the files inside of the folder itself are being deleted but the folder itself is not and a ls -lah on the folder in question shows. root@Unraid-Nas:/mnt/user/appdata/fah/work/00# ls -lah total 1.6M drwxr-xr-x 1 nobody users 56 Feb 25 15:59 ./ drwxr-xr-x 1 nobody users 60 Feb 25 15:44 ../ -rw-r--r-- 1 nobody users 1.6M Feb 25 15:46 .fuse_hidden000282d70000017f the only way to clear the folder is to stop the docker (which then clears the fuse file) and then manually delete it.
February 25, 201511 yr Author What does "lsof /mnt/user/appdata/fah/work/00/.fuse_hidden*" show? lsof /mnt/user/appdata/fah/work/00/.fuse_hidden* COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME FAHCoreWr 19346 nobody 8r REG 0,31 1647772 164567 /mnt/user/appdata/fah/work/00/.fuse_hidden000282d7000001a0 FahCore_a 19350 nobody 8r REG 0,31 1647772 164567 /mnt/user/appdata/fah/work/00/.fuse_hidden000282d7000001a0
February 25, 201511 yr Author i'm thinking it's related to btrfs and its slow deletion of files because i've just seen my couchpotato docker reporting the same error a few times in the log, but it seems to release the file eventually and the folder couch docker log is complaining about gets deleted on about the 3rd attempt.
February 25, 201511 yr Author having said that though, the next work unit in folding@home being downloaded and started has released the lock on the fuse file in 00 and the fuse file is now gone, but the folder 00 remains and now the fah app has locked a fuse file in 01 and opened a new folder 02 for the next work unit. so while i'm not going to end up with more than one fuse file at any time, i will end up with a ton of empty folders after a while.
Archived
This topic is now archived and is closed to further replies.