-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
zfs mounts used size not always correctly reported #66
Comments
Thanks for the report. Any element of investigation would be valuable before I find the time to try reproduce this. |
@Canop Let me know if I can give you more information. |
I don't know. Unless you want to dive yourself into debugging lfs-core and see where the data are misinterpreted. |
Sorry. I'd love to help but I don't know rust. Could it be that the logic where the mount-point is read the value gets overwritten by previous values?
only shared values that I see are that the one mount is ontop the other. Here is the output from mount:
|
I can't dive into this this week. I'll use your observations when work becomes a little more quiet. |
I found another scenario where dysk is not reporting correctly on ZFS. My suspicion that the mount point sharing a portion of the same path, causing a problem is therefore wrong. Also the used size differs. Dysk 2.8.0 -u SI
Dysk 2.8.0 -u binary
zfs list
|
Could the crate |
Could pools not be printed like the following example:
where:
and
provides the correct values? An example of where dysk got it wrong:
The total size should be the same for the 4 mounts. The free space is correct. |
I've notices that the reporting on zfs pools is not accurate. The used value for each is not correct as can be seen here:
zfs list
show the used as:It seems to catch the 301M for
/var/log
and apply it to/var/log/audit
too.The text was updated successfully, but these errors were encountered: