Skip to content

Reduce FUSE transport log level.#225

Open
georgyo wants to merge 1 commit intocloud-hypervisor:masterfrom
georgyo:adjust-log-level
Open

Reduce FUSE transport log level.#225
georgyo wants to merge 1 commit intocloud-hypervisor:masterfrom
georgyo:adjust-log-level

Conversation

@georgyo
Copy link

@georgyo georgyo commented Mar 19, 2026

The FUSE init flags are unlikely to be of use unless one is debugging a problem with the filesystem.

The messages about channel status get printed for every thread, and it's rather confusing for end-users to have a FUSE filesystem terminate with:

fuse filesystem umounted
FUSE channel already closed!
FUSE channel already closed!
FUSE channel already closed!
FUSE channel already closed!
FUSE channel already closed!
FUSE channel already closed!

...when everything went well.

NOTE: This is a rebase of #200

The FUSE init flags are unlikely to be of use unless one is debugging a problem
with the filesystem.

The messages about channel status get printed for every thread, and it's rather
confusing for end-users to have a FUSE filesystem terminate with:

fuse filesystem umounted
FUSE channel already closed!
FUSE channel already closed!
FUSE channel already closed!
FUSE channel already closed!
FUSE channel already closed!
FUSE channel already closed!

...when everything went well.
info!(
debug!(
"FUSE INIT major {} minor {}\n in_opts: {:?}\nout_opts: {:?}",
major, minor, capable, enabled
Copy link
Collaborator

@imeoer imeoer Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but in real-world usage scenario, we'd like this info (Business processe usually only enable info-level logging) to always be visible to make it easier to debug fuse-related issues across different kernels.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it make more sense to expose this somewhere via some getter and then have that application log it explicitly?

See my question regarding that on #195 (comment)

Logging this with info level is surprising for library consumers, and confusing for end users. It really should be exposed through some getter, if you want to print these values explicitly from one application.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 I think it's reasonable to provide a getter so that the business process can print it as needed.

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.

4 participants