一个小小的磁盘容量疑问
本帖最后由 WiiGe 于 2025-6-17 15:33 编辑我的/目录只用了149G, 为何却在258G的磁盘上产生了95%的占用啊?
# sudo du -sh / --exclude="/mnt" --exclude="/porc"
149G /
# lsblk -o NAME,SIZE,FSTYPE,MOUNTPOINT,LABEL
NAME SIZE FSTYPE MOUNTPOINT LABEL
loop0 11.5M squashfs /snap/canonical-livepatch/316
loop1 13.2M squashfs /snap/canonical-livepatch/333
loop2 73.9M squashfs /snap/core22/1981
loop3 73.9M squashfs /snap/core22/2010
loop4 44.4M squashfs /snap/snapd/23771
loop5 50.9M squashfs /snap/snapd/24505
sr0 1024M
nvme1n1 260.8G
├─nvme1n1p1 1G vfat /boot/efi
├─nvme1n1p2 2G ext4 /boot
└─nvme1n1p3 257.8G LVM2_member
└─ubuntu--vg-lv--0 257.8G btrfs /
nvme3n1 3.5T LVM2_member
├─memblaze--vg-Apps_rmeta_1 4M
│ └─memblaze--vg-Apps 3.5T btrfs /mnt/Apps
└─memblaze--vg-Apps_rimage_1 3.5T
└─memblaze--vg-Apps 3.5T btrfs /mnt/Apps
nvme2n1 1.9T LVM2_member
└─fanxiang--vg-DownloadCache 1.9T btrfs /mnt/DownloadCache
nvme0n1 3.5T LVM2_member
├─memblaze--vg-Apps_rmeta_0 4M
│ └─memblaze--vg-Apps 3.5T btrfs /mnt/Apps
└─memblaze--vg-Apps_rimage_0 3.5T
└─memblaze--vg-Apps 3.5T btrfs /mnt/Apps
$ df -Tha
Filesystem Type SizeUsed Avail Use% Mounted on
sysfs sysfs 0 0 0 - /sys
proc proc 0 0 0 - /proc
udev devtmpfs 126G 0126G 0% /dev
devpts devpts 0 0 0 - /dev/pts
tmpfs tmpfs 26G5.2M 26G 1% /run
efivarfs efivarfs 246K163K 79K68% /sys/firmware/efi/efivars
/dev/mapper/ubuntu--vg-lv--0 btrfs 258G239G 15G95% /
securityfs securityfs 0 0 0 - /sys/kernel/security
tmpfs tmpfs 126G8.0K126G 1% /dev/shm
tmpfs tmpfs 5.0M 05.0M 0% /run/lock
cgroup2 cgroup2 0 0 0 - /sys/fs/cgroup
pstore pstore 0 0 0 - /sys/fs/pstore
bpf bpf 0 0 0 - /sys/fs/bpf
systemd-1 - - - - - /proc/sys/fs/binfmt_misc
hugetlbfs hugetlbfs 0 0 0 - /dev/hugepages
mqueue mqueue 0 0 0 - /dev/mqueue
debugfs debugfs 0 0 0 - /sys/kernel/debug
tracefs tracefs 0 0 0 - /sys/kernel/tracing
fusectl fusectl 0 0 0 - /sys/fs/fuse/connections
configfs configfs 0 0 0 - /sys/kernel/config
/dev/loop0 squashfs 12M 12M 0 100% /snap/canonical-livepatch/316
/dev/loop1 squashfs 14M 14M 0 100% /snap/canonical-livepatch/333
/dev/loop2 squashfs 74M 74M 0 100% /snap/core22/1981
/dev/loop3 squashfs 74M 74M 0 100% /snap/core22/2010
/dev/loop4 squashfs 45M 45M 0 100% /snap/snapd/23771
/dev/loop5 squashfs 51M 51M 0 100% /snap/snapd/24505
/dev/nvme1n1p2 ext4 2.0G190M1.6G11% /boot
/dev/nvme1n1p1 vfat 1.1G6.2M1.1G 1% /boot/efi
/dev/mapper/fanxiang--vg-DownloadCache btrfs 1.9T1.6T356G82% /mnt/DownloadCache
/dev/mapper/memblaze--vg-Apps btrfs 3.5T759G2.8T22% /mnt/Apps
binfmt_misc binfmt_misc 0 0 0 - /proc/sys/fs/binfmt_misc
sunrpc rpc_pipefs 0 0 0 - /run/rpc_pipefs
tmpfs tmpfs 26G5.2M 26G 1% /run/snapd/ns
nsfs nsfs 0 0 0 - /run/snapd/ns/canonical-livepatch.mnt
为什么有239-149=90G消失了? 似乎devtempfs的尺寸和消失的容量很接近, 我的理解是被shm占用了, 不知道这样想对不对?
btrfs 用 df 获得的信息不准确，这种复杂的文件系统建议用配套的工具查看信息，另外 du 有个 -x 选项可以只计算同一个文件系统，不过考虑到文件压缩之类的东西存在，也不太准确，所以最好还是用文件系统配套工具。 archwiki说
像 df(1) 这样的用户空间工具可能不会准确的计算剩余空间 (因为并没有分别计算文件和元数据的使用情况) 。推荐使用 btrfs filesystem usage 来查看使用情况。
https://wiki.archlinuxcn.org/wiki/Btrfs#显示已使用的/空闲空间 感谢两位点拨, 我又得到了这一结果:
$ sudo btrfs filesystem usage /
Overall:
Device size: 257.78GiB
Device allocated: 257.78GiB
Device unallocated: 1.00MiB
Device missing: 0.00B
Device slack: 0.00B
Used: 227.90GiB
Free (estimated): 24.17GiB (min: 24.17GiB)
Free (statfs, df): 24.17GiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 308.14MiB (used: 0.00B)
Multiple profiles: no
Data,single: Size:249.76GiB, Used:225.59GiB (90.32%)
/dev/mapper/ubuntu--vg-lv--0249.76GiB
Metadata,DUP: Size:4.00GiB, Used:1.15GiB (28.88%)
/dev/mapper/ubuntu--vg-lv--0 8.00GiB
System,DUP: Size:8.00MiB, Used:48.00KiB (0.59%)
/dev/mapper/ubuntu--vg-lv--0 16.00MiB
Unallocated:
/dev/mapper/ubuntu--vg-lv--0 1.00MiB
但这不太合理, 我的docker 在/var/lib 里面只塞了90G+的东西, 主要集中在overlay2 , 这些空间我似乎无法释放出来
我该如何重新让它空闲空间回到100G+的状态呢? (我确信我没有什么数据放在 / 中, 能配到 /mnt 中的我都移进去了 看看fstab 里/是不是只mount了subvolume docker自带回收空间的命令，docker system prune mono 发表于 2025-6-17 23:31
docker自带回收空间的命令，docker system prune
$ sudo docker system prune
password for wiige:
WARNING! This will remove:
- all stopped containers
- all networks not used by at least one container
- all dangling images
- unused build cache
Are you sure you want to continue? y $ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type><options> <dump><pass>
# / was on /dev/ubuntu-vg/lv-0 during curtin installation
/dev/disk/by-id/dm-uuid-LVM-kEYzhlNebQ1qfK94KlRUYR7lJ7IGCx2Czw5qrtu3nUUbbXi7toApk61CuWsqfMAJ / btrfs defaults 0 1
# /boot was on /dev/nvme0n1p2 during curtin installation
/dev/disk/by-uuid/34709e90-27f9-4ce4-bbe4-6d159dde3ec3 /boot ext4 defaults 0 1
# /boot/efi was on /dev/nvme0n1p1 during curtin installation
/dev/disk/by-uuid/314A-F09A /boot/efi vfat defaults 0 1
#/swapfile.btrfsswap none swap sw 0 0
# /dev/disk/by-uuid/533af4a8-6aaf-49f7-8d01-5336db1d8307 /mnt/DownloadCache btrfs defaults 0 2
/dev/disk/by-uuid/533af4a8-6aaf-49f7-8d01-5336db1d8307 /mnt/DownloadCache btrfs defaults 0 3
/dev/disk/by-uuid/6f8ed587-7374-4f62-846d-14aa91858908 /mnt/Apps btrfs defaults 0 2
mono 发表于 2025-6-17 23:30
看看fstab 里/是不是只mount了subvolume
我应该没挂载错什么对吧?
$ ls -la /dev/disk/by-id/
total 0
drwxr-xr-x2 root root 700 Jun 17 13:51 .
drwxr-xr-x 10 root root 200 Jun 17 13:51 ..
lrwxrwxrwx1 root root 9 Jun 17 13:51 ata-hp_HLDS_DVDRW_GUD1N_7HUDNMAKKDQ44L -> ../../sr0
lrwxrwxrwx1 root root10 Jun 17 13:51 dm-name-fanxiang--vg-DownloadCache -> ../../dm-0
lrwxrwxrwx1 root root10 Jun 17 13:51 dm-name-memblaze--vg-Apps -> ../../dm-6
lrwxrwxrwx1 root root10 Jun 17 13:51 dm-name-ubuntu--vg-lv--0 -> ../../dm-1
lrwxrwxrwx1 root root10 Jun 17 13:51 dm-uuid-LVM-gjRDZXHQzYqfZp33z2khATq9hbrDpK9GUlh2HDnfL3HkbJj4aGwhGCUZnNptDlnC -> ../../dm-0
lrwxrwxrwx1 root root10 Jun 17 13:51 dm-uuid-LVM-I8bzzaAgAQ3eEaopBLLFXCP0989PgwcVzaRuyD7sRkOflN1PWbsEftESSjs1I9B5 -> ../../dm-6
lrwxrwxrwx1 root root10 Jun 17 13:51 dm-uuid-LVM-kEYzhlNebQ1qfK94KlRUYR7lJ7IGCx2Czw5qrtu3nUUbbXi7toApk61CuWsqfMAJ -> ../../dm-1
lrwxrwxrwx1 root root13 Jun 17 13:51 lvm-pv-uuid-e9cHuy-ojKb-hpz0-05xa-Pyfc-mVYU-gLrMZ5 -> ../../nvme2n1
lrwxrwxrwx1 root root13 Jun 17 13:51 lvm-pv-uuid-oFdH6W-wafl-s8zh-VdJX-lSwO-RcF9-MxLKgh -> ../../nvme0n1
lrwxrwxrwx1 root root13 Jun 17 13:51 lvm-pv-uuid-r24HoI-4StA-Wx2f-L2Wd-TRDn-BVx0-86qCmu -> ../../nvme3n1
lrwxrwxrwx1 root root15 Jun 17 13:51 lvm-pv-uuid-WU3dpn-BHyA-yYNK-BJpK-By95-kMOE-Uh50dq -> ../../nvme1n1p3
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-eui.000000000000000138b19e7418000326 -> ../../nvme0n1
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-eui.000000000000000138b19e7418000340 -> ../../nvme3n1
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-Fanxiang_S500Pro_2TB_FXS500Pro243954233 -> ../../nvme2n1
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-Fanxiang_S500Pro_2TB_FXS500Pro243954233_1 -> ../../nvme2n1
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-INTEL_SSDPED1D280GA_PHMB75160057280CGN -> ../../nvme1n1
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-INTEL_SSDPED1D280GA_PHMB75160057280CGN_1 -> ../../nvme1n1
lrwxrwxrwx1 root root15 Jun 17 13:51 nvme-INTEL_SSDPED1D280GA_PHMB75160057280CGN_1-part1 -> ../../nvme1n1p1
lrwxrwxrwx1 root root15 Jun 17 13:51 nvme-INTEL_SSDPED1D280GA_PHMB75160057280CGN_1-part2 -> ../../nvme1n1p2
lrwxrwxrwx1 root root15 Jun 17 13:51 nvme-INTEL_SSDPED1D280GA_PHMB75160057280CGN_1-part3 -> ../../nvme1n1p3
lrwxrwxrwx1 root root15 Jun 17 13:51 nvme-INTEL_SSDPED1D280GA_PHMB75160057280CGN-part1 -> ../../nvme1n1p1
lrwxrwxrwx1 root root15 Jun 17 13:51 nvme-INTEL_SSDPED1D280GA_PHMB75160057280CGN-part2 -> ../../nvme1n1p2
lrwxrwxrwx1 root root15 Jun 17 13:51 nvme-INTEL_SSDPED1D280GA_PHMB75160057280CGN-part3 -> ../../nvme1n1p3
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-MEMBLAZE_P6530CH0384M00_SH220600806 -> ../../nvme0n1
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-MEMBLAZE_P6530CH0384M00_SH220600806_1 -> ../../nvme0n1
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-MEMBLAZE_P6530CH0384M00_SH220600832 -> ../../nvme3n1
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-MEMBLAZE_P6530CH0384M00_SH220600832_1 -> ../../nvme3n1
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-nvme.1e4b-46585335303050726f323433393534323333-46616e7869616e67205335303050726f20325442-00000001 -> ../../nvme2n1
lrwxrwxrwx1 root root13 Jun 17 13:51 nvme-nvme.8086-50484d42373531363030353732383043474e-494e54454c2053534450454431443238304741-00000001 -> ../../nvme1n1
lrwxrwxrwx1 root root15 Jun 17 13:51 nvme-nvme.8086-50484d42373531363030353732383043474e-494e54454c2053534450454431443238304741-00000001-part1 -> ../../nvme1n1p1
lrwxrwxrwx1 root root15 Jun 17 13:51 nvme-nvme.8086-50484d42373531363030353732383043474e-494e54454c2053534450454431443238304741-00000001-part2 -> ../../nvme1n1p2
lrwxrwxrwx1 root root15 Jun 17 13:51 nvme-nvme.8086-50484d42373531363030353732383043474e-494e54454c2053534450454431443238304741-00000001-part3 -> ../../nvme1n1p3
lrwxrwxrwx1 root root 9 Jun 17 13:51 wwn-0x5001480000000000 -> ../../sr0
页:
[1]