From: "Krzysztof Żelechowski" <giecrilj@stegny.2a.pl>
To: 60335@debbugs.gnu.org
Subject: bug#60335: du should warn about btrfs
Date: Mon, 26 Dec 2022 09:55:56 +0100 [thread overview]
Message-ID: <2272224.ElGaqSPkdT@localhost.localdomain> (raw)
The tool du does not handle btrfs volumes correctly. The total reported on my
system is almost twice the volume capacity. This is unexpected and should be
indicated with a warning, both in the output and in the documentation. Since
the head of the output is often lost because it is not that important, the
warning should be emitted at the end.
The total reported by { du /; } agrees on the total reported by { btrfs
filesystem du /; } but the latter command also prints a shared size which is
not paradoxical. The problem with the tool btrfs is that it is a system
command and not a user command so our code cannot just execute their code and
be happy with it. Also, their output is different because it has 3 columns as
I mentioned earlier.
I understand that the total reported by { du /; } is still useful if one were
to create an archive of the file system; such an archive would be much bigger
than the file system itself and thus could not be restored unless the volume
has lots of free space or the archiver itself is btrfs-aware, which I am
afraid it is not. The moral of this story apparently is that btrfs volumes
cannot be reasonably archived using standard tools.
next reply other threads:[~2022-12-26 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 8:55 Krzysztof Żelechowski [this message]
2022-12-26 18:42 ` bug#60335: du should warn about btrfs Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2272224.ElGaqSPkdT@localhost.localdomain \
--to=giecrilj@stegny.2a.pl \
--cc=60335@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).