Currently, fuse response log OK () is pretty generic. Replacing the OK with operation name. This is specially useful in knowing if a particular operation ReadFile or LookUpInode is happening in parallel.
Before
time="25/06/2024 03:05:52.093580" severity=TRACE message="fuse_debug: Op 0x00000160 connection.go:420] <- LookUpInode (parent 1, name \"b.txt\", PID 870932)"
time="25/06/2024 03:05:52.093777" severity=TRACE message="fuse_debug: Op 0x00000160 connection.go:513] -> OK (inode 2)"
After
time="25/06/2024 03:03:45.288441" severity=TRACE message="fuse_debug: Op 0x0000015c connection.go:420] <- LookUpInode (parent 1, name \"b.txt\", PID 869418)"
time="25/06/2024 03:03:45.505412" severity=TRACE message="fuse_debug: Op 0x0000015c connection.go:513] -> LookUpInode (inode 3)"
Currently, fuse response log
OK ()
is pretty generic. Replacing theOK
with operation name. This is specially useful in knowing if a particular operationReadFile
orLookUpInode
is happening in parallel.Before
After