• 7 Posts
  • 19 Comments
Joined 2 years ago
cake
Cake day: June 6th, 2023

help-circle
  • Looks like some combination of defragging & balancing has done the trick! The space that was previously marked UNREACHABLE is now UNUSED, and my disk space is back to normal:

    Filesystem      Size  Used Avail Use% Mounted on
    /dev/sda1       227G  105G  103G  51% /
    

    Thanks for the wiki link, Btrfs is new to me and I’ve definitely got some learning to do




  • Interesting, this could be it? I haven’t configured any mounts on this device yet, but when I tried one of the other suggestions from this thread and use btdu, I get this error:

    $ ./btdu -x /
    Fatal error: The mount point you specified, "/", is not the top-level btrfs subvolume ("subvolid=5,subvol=/").
    It is the btrfs subvolume "subvolid=256,subvol=/@rootfs".
    Please specify the path to a mountpoint mounted with subvol=/ or subvolid=5.
    E.g.: mkdir /mnt/sda1 && mount -o subvol=/ /dev/sda1 /mnt/sda1 && ./btdu /mnt/sda1
    
    Note that the top-level btrfs subvolume ("subvolid=5,subvol=/") is not the same as the root of the filesystem ("/").
    

    I’m fairly new to the workings of Btrfs so this is jibberish to me right now, but I’ll look into it more

    EDIT: Nevermind! I was just using the tool wrong. I needed to mount my btrfs “sub-volume” then do the scan against that:

    sudo mkdir -p /mnt/btdu

    sudo mount -o subvolid=5 /dev/sda1 /mnt/btdu

    sudo ./btdu /mnt/btdu


  • ncdu

    Oh this one is very cool! Unfortunately it also only shows the same 101GB being used:

    ncdu 1.22 ~ Use the arrow keys to navigate, press ? for help                                                                                                                                  
    --- / ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
       93.1 GiB [###########################] /home                                                                                                                                               
        6.5 GiB [#                          ] /usr
      790.4 MiB [                           ] /var
      173.0 MiB [                           ] /boot
       12.8 MiB [                           ] /etc
        1.7 MiB [                           ] /root
        1.3 MiB [                           ] /run
       44.0 KiB [                           ] /tmp
    @   4.0 KiB [                           ]  initrd.img.old
    @   4.0 KiB [                           ]  initrd.img
    @   4.0 KiB [                           ]  vmlinuz.old
    @   4.0 KiB [                           ]  vmlinuz
    @   4.0 KiB [                           ]  lib64
    @   4.0 KiB [                           ]  sbin
    @   4.0 KiB [                           ]  lib
    @   4.0 KiB [                           ]  bin
    .   0.0   B [                           ] /proc
        0.0   B [                           ] /sys
        0.0   B [                           ] /dev
        0.0   B [                           ] /media
    e   0.0   B [                           ] /srv
    e   0.0   B [                           ] /opt
    e   0.0   B [                           ] /mnt
    
    



















  • https://blog.mmpa.info/posts/bleeding-pipe/

    Known Affected Mods

    The known affected mods include, but are not limited to:

    • EnderCore (dependency of EnderIO). The GT New Horizons fork has been fixed, and the original has been aswell, but EnderIO’s minimum versions has not yet been updated.
    • LogisticsPipes. This has once again been fixed in GT New Horizons version as of July 25, 2023, and the original is fixed since version 0.10.0.71. MC 1.12 versions are not affected. If you have played on a server with a vulnerable version, assume you are infected.
    • The 1.7-1.12 versions of BDLib. Once again, GTNH fork has this fixed, but the developer of the original currently does not plan to fix it. Assume you are infected if you have played on a server and are not on the GTNH fork.
    • Smart Moving 1.12
    • Brazier
    • DankNull
    • Gadomancy

    Currently the only confirmed exploits have been against 1.7.10/1.12.2 Forge mods.