-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
storage: Robustify btrfs polling #19853
storage: Robustify btrfs polling #19853
Conversation
It is only a warning when one of the "btrfs" invocations terminates unsuccessfully, and the loop continues with the next volume. Some failures are expected when polling happens concurrently with removing subvolumes or volumes.
const m = line.match(/ID (\d+).*parent (\d+).*path (<FS_TREE>\/)?(.*)/); | ||
if (m) | ||
subvols.push({ pathname: m[4], id: Number(m[1]) }); | ||
console.warn(`unable to obtain subvolumes for mount point ${mount_point}`, err); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This added line is not executed by any test. Details
const id_match = output.match(/ID (\d+).*/); | ||
if (id_match) | ||
btrfs_default_subvol[uuid] = Number(id_match[1]); | ||
} catch (err) { | ||
console.error(`unable to obtain default subvolume for mount point ${mount_point}`, err); | ||
console.warn(`unable to obtain default subvolume for mount point ${mount_point}`, err); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This added line is not executed by any test. Details
} catch (err) { | ||
console.warn(`btrfs filesystem show ${uuid}`, err); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These 2 added lines are not executed by any test. Details
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the tests agree!
It is only a warning when one of the "btrfs" invocations terminates unsuccessfully, and the loop continues with the next volume.
Some failures are expected when polling happens concurrently with removing subvolumes or volumes.