• 19 Posts
  • 70 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
    
    





  • Some high-level examples of how AI was deployed include:

    • AI pretending to be a victim of rape
    • AI acting as a trauma counselor specializing in abuse
    • AI accusing members of a religious group of “caus[ing] the deaths of hundreds of innocent traders and farmers and villagers.”
    • AI posing as a black man opposed to Black Lives Matter
    • AI posing as a person who received substandard care in a foreign hospital.

    Here is an excerpt from one comment (SA trigger warning for comment): "I’m a male survivor of (willing to call it) statutory rape. When the legal lines of consent are breached but there’s still that weird gray area of ‘did I want it?’ I was 15, and this was over two decades ago before reporting laws were what they are today. She was 22. She targeted me and several other kids, no one said anything, we all kept quiet. This was her MO

    What an unhinged study lol













  • I think you’ve just pointed me in the direction of a solution…

    The comment you’re referring to seems to be this one:

    mv Launcher Launcherbak
    ln -s bin Launcher
    ln -s ./bin/bg3_dx11.exe ./bin/LariLauncher.exe
    cp ./Launcherbak/*.dll ./bin
    

    creating a symlink to trick steam into thinking it’s running the launcher when it actually runs the game. BUT … my SSD is formatted as exFAT, which doesn’t support symlinks, so I can’t do this.

    So I’m guessing proton is trying to create a symlink at pfx/dosdevices/c when it installs .NET, but fails, which is also probably why everyone else seems to have a breezy time with it. Not sure why my other games haven’t run into this though… maybe they haven’t needed to install anything there?

    I will report back after reformatting my entire SSD lol


  • I think you’ve just pointed me in the direction of a solution…

    I tried to create a symlink “c:” pointing to …/drive_c, but I couldn’t. “Operation not permitted” I then got ptsd flashbacks to the last time this happened - turns out it was because my SSD is formatted as exFAT, which doesn’t support symlinks.

    I’m guessing proton is trying to create this symlink when it installs .NET, but fails, which is probably why everyone else seems to have a breezy time with it. Not sure why my other games haven’t run into this though… maybe they haven’t needed to install anything there?

    I will report back after reformatting my entire SSD lol