Error: -38, -61 and -95

[r4nd0m123]

Hi,

I've noticed several errors appear when running in debug mode. I couldn't see any info about these on the wiki and what they mean. Any help is greatly appreciated.

Setup

• NAS
  1 SMB share
• Ubuntu 24.04.1 server
  Mounted NAS SMB share. Mount paramters shown below.
  Running rar2fs v1.29.7. rar2fs -V output shown further below.
  Currently not sharing the rar2fs mounts outside of this server. But highly likely to do so in the future.

$ mount -l -t cifs
//IPv4/SHARE on /mnt/linux_smb type cifs (ro,relatime,vers=3.1.1,cache=strict,username=user,uid=0,noforceuid,gid=0,noforcegid,addr=IPv4,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,retrans=1,echo_interval=60,actimeo=1,closetimeo=1)

$ rar2fs -V
rar2fs v1.29.7 (DLL version 9) Copyright (C) 2009 Hans Beckerus
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under
certain conditions; see http://www.gnu.org/licenses/ for details.
FUSE library version: 2.9.9
fusermount3 version: 3.14.0
using FUSE kernel interface version 7.19

$ sudo rar2fs --exclude=.lock --seek-length=1 --relatime -o auto_cache -o direct_io -o allow_other /mnt/linux_smb/X265 /mnt/shared_X265

$ sudo rar2fs --exclude=.lock --seek-length=1 --relatime -d -o auto_cache -o direct_io -o allow_other /mnt/linux_smb/X264 /mnt/shared_X264
rar2fs[1761]: mounted /mnt/shared_X264
unique: 2, opcode: INIT (26), nodeid: 0, insize: 104, pid: 0
INIT: 7.39
flags=0x73fffffb
max_readahead=0x00020000
INIT: 7.19
flags=0x00000010
max_readahead=0x00020000
max_write=0x00020000
max_background=0
congestion_threshold=0
unique: 2, success, outsize: 40

unique: 4, opcode: ACCESS (34), nodeid: 1, insize: 48, pid: 1368
unique: 4, error: -38 (Function not implemented), outsize: 16
unique: 6, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 1368
getattr /
unique: 6, success, outsize: 120
unique: 8, opcode: GETXATTR (22), nodeid: 1, insize: 63, pid: 1368
getxattr / user.DOSATTRIB 256
unique: 8, error: -61 (No data available), outsize: 16
unique: 10, opcode: GETXATTR (22), nodeid: 1, insize: 72, pid: 1368
getxattr / system.posix_acl_access 4096
unique: 10, error: -95 (Operation not supported), outsize: 16
unique: 12, opcode: GETXATTR (22), nodeid: 1, insize: 73, pid: 1368
getxattr / system.posix_acl_default 4096
unique: 12, error: -95 (Operation not supported), outsize: 16
unique: 14, opcode: GETXATTR (22), nodeid: 1, insize: 63, pid: 1368
getxattr / user.DOSATTRIB 256
unique: 14, error: -61 (No data available), outsize: 16
unique: 16, opcode: GETXATTR (22), nodeid: 1, insize: 72, pid: 1368
getxattr / system.posix_acl_access 4096
unique: 16, error: -95 (Operation not supported), outsize: 16
unique: 18, opcode: GETXATTR (22), nodeid: 1, insize: 73, pid: 1368
getxattr / system.posix_acl_default 4096
unique: 18, error: -95 (Operation not supported), outsize: 16
unique: 20, opcode: GETXATTR (22), nodeid: 1, insize: 63, pid: 1368
getxattr / user.DOSATTRIB 256
unique: 20, error: -61 (No data available), outsize: 16

[hasse69]

I fail to fully understand if the errors you see are in fact impacting the functionality or if it is simply an observation? That FUSE throws a lot of errors in debug mode is expected since not all callbacks and operands are implemented by rar2fs and fall back to default implementations provided by FUSE library/kernel. Also errors are thrown by FUSE for various reasons that are completely normal, eg. lookup for files that does not exist etc.