From: Skirnir Torvaldsson <skirnir.torvaldsson@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: support request: btrfs df reports drive is out of space, cannot find what occupies it
Date: Fri, 19 Apr 2024 13:40:22 +0500 [thread overview]
Message-ID: <b996820e-efa5-4fb5-ba4e-57cc295c1b64@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1809 bytes --]
Dear btrfs experts,
Could you please help me sort out the following situation:
btrfs df reports my 100Gb device is almost out of space (which agrees
with the results produced by the standard "df"):
root@next:/home/support# btrfs fi df /
Data, single: total=82.00GiB, used=78.23GiB
System, DUP: total=32.00MiB, used=16.00KiB
Metadata, DUP: total=1.00GiB, used=153.70MiB
GlobalReserve, single: total=68.45MiB, used=0.00B
root@next:/home/support# df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 96G 79G 16G 84% /
However when I try to locate files to delete with du that's what I get:
|root||@next||:/home/support# du -hd1 /|
|70M /boot|
|0| |/dev|
|2||.2G /.snapshots|
|14M /bin|
|4||.5M /etc|
|2||.5M /home|
|348M /lib|
|4||.0K /lib64|
|0| |/media|
|0| |/mnt|
|0| |/opt|
|0| |/proc|
|40K /root|
|2||.7M /run|
|12M /sbin|
|0| |/srv|
|0| |/sys|
|0| |/tmp|
|566M /usr|
|5||.0G /var|
|29G /next|
|38G /|
|
|
|I.e. almost 40Gb just gone somewhere. Am I doing something wrong? Is
there a problem or a piece of theory I'm missing? Kindly advice.|
|
|
|+++++++++++++++++++++++++++++++++++++|
|root@next:~||# uname -a|
|Linux next 5.10.0-28-amd64 ||#1 SMP Debian 5.10.209-2 (2024-01-31)
x86_64 GNU/Linux|
|root@next:~||# btrfs --version|
|btrfs-progs v5.10.1|
|root@next:~||# btrfs fi show|
|Label: ||'NEXT_ROOTFS'| |uuid: abc71bdb-c570-461d-a28a-54294a646089|
|||Total devices 1 FS bytes used 78.37GiB|
|||devid 1 size 95.46GiB used 84.06GiB path ||/dev/sda3|
|root@next:~||# btrfs fi df /|
|Data, single: total=82.00GiB, used=78.22GiB|
|System, DUP: total=32.00MiB, used=16.00KiB|
|Metadata, DUP: total=1.00GiB, used=153.64MiB|
|GlobalReserve, single: total=68.45MiB, used=0.00B|
|
|
[-- Attachment #1.2: Type: text/html, Size: 8568 bytes --]
[-- Attachment #2: dmesg.log.gz --]
[-- Type: application/x-gzip, Size: 20313 bytes --]
next reply other threads:[~2024-04-19 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 8:40 Skirnir Torvaldsson [this message]
2024-04-19 11:19 ` support request: btrfs df reports drive is out of space, cannot find what occupies it Andrei Borzenkov
2024-04-19 13:18 ` Skirnir Torvaldsson
2024-04-19 13:41 ` Andrei Borzenkov
2024-04-19 15:27 ` Skirnir Torvaldsson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b996820e-efa5-4fb5-ba4e-57cc295c1b64@gmail.com \
--to=skirnir.torvaldsson@gmail.com \
--cc=linux-btrfs@vger.kernel.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).