fuse-overlayfs icon indicating copy to clipboard operation
fuse-overlayfs copied to clipboard

touch: setting times of 'XXX' : No such file or directory

Open Shadow8472 opened this issue 1 year ago • 0 comments

For the greater context, I'm trying to run Nextcloud:

It was suggested I look into fuse-overlayfs, and while I've been making inches of progress unguided, I'm focused enough of a question that my 1/3 to 1/2 of my search results are in Chinese.

(Run from an account in sudoers)

$ sudo ./startfuse.sh 
uid=unchanged
gid=unchanged
upperdir=/mnt/PhotoTrunk/nextcloudPhotoVault
workdir=/mnt/PhotoTrunk/.fuseWorkdir
lowerdir=/home/nextclouduser-redlaptop/nextcloudBase/fuseLower/
mountpoint=/home/nextclouduser-redlaptop/nextcloudBase/photoMountpoint
plugins=<none>
fsync=enabled
FUSE library version: 3.10.3
unique: 2, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.32
flags=0x03fffffb
max_readahead=0x00020000
   INIT: 7.31
   flags=0x0041f069
   max_readahead=0x00020000
   max_write=0x00100000
   max_background=0
   congestion_threshold=0
   time_gran=1
   unique: 2, success, outsize: 80
unique: 4, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 738278
ovl_getattr(ino=1)
   unique: 4, success, outsize: 120
unique: 6, opcode: LOOKUP (1), nodeid: 1, insize: 51, pid: 748152
ovl_lookup(parent=1, name=helloWorld)
   unique: 6, success, outsize: 144
unique: 8, opcode: CREATE (35), nodeid: 1, insize: 67, pid: 748152
ovl_create(parent=1, name=helloWorld)
   unique: 8, error: -1 (Operation not permitted), outsize: 16

startfuse.sh

fuse-overlayfs \
        -d \
        -o allow_other \
        -o lowerdir=/home/nextclouduser-redlaptop/nextcloudBase/fuseLower/ \
        -o upperdir=/mnt/PhotoTrunk/nextcloudPhotoVault/ \
        -o workdir=/mnt/PhotoTrunk/.fuseWorkdir \
        /home/nextclouduser-redlaptop/nextcloudBase/photoMountpoint

(limited account)

nextclouduser-redlaptop@Shadow8472-Laptop:~/nextcloudBase/photoMountpoint$ touch helloWorld
touch: setting times of 'helloWorld': No such file or directory

So far, I've tried rebooting (both NFS client and server) as well as making sure both systems' clocks are adjusted from Daylight Savings Time ending.

Shadow8472 avatar Nov 10 '23 22:11 Shadow8472