-
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
Can't run compsize on / #14
Comments
I can't reproduce: I've messed recently with this code, but changed only the error message. |
... I'm an idiot. Obviously, I do get the error message you say, it just takes a while — unless the cache is hot or one of special filesystems gets enumerated by readdir before something that takes a substantial time to process; in both of these cases the error is returned quickly. And, the error message doesn't say what file the ioctl failed on, making it hard for the user to see what's wrong. In the short term, you can run |
@kilobyte yeah, ✘ yard@arch ~ sudo compsize -x /
Processed 308087 files, 228092 regular extents (234987 refs), 171354 inline.
Type Perc Disk Usage Uncompressed Referenced
TOTAL 63% 17G 27G 27G
none 100% 12G 12G 12G
zstd 32% 4.7G 14G 15G I don't really know which method is better, but we can add blacklist for folders like |
I get a slightly different message with the latest checkout:
But |
I'm running into this problem as well, and -x doesn't really help because it ends up skipping nested btrfs subvolumes on the same file system. So what's really needed is a way to skip non-btrfs file systems. Example:
In the case of |
Actually, there are multiple schemes people can legitimately want:
|
Hello, thanks for your great program!
I have a little issue - I can't run compsize on / directory:
yard@arch ~ sudo compsize / Not btrfs (or SEARCH_V2 unsupported).
But btrfs command can detect that it's btrfs:
Is it a limitation?
The text was updated successfully, but these errors were encountered: