Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improving fuse response log for better debuggability #165

Merged
merged 1 commit into from
Jun 26, 2024

Conversation

raj-prince
Copy link
Contributor

@raj-prince raj-prince commented Jun 25, 2024

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)"

@stapelberg stapelberg merged commit 8a36813 into jacobsa:master Jun 26, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants