HOWEVER, when removing "ssd_spread" from the format/mount options said unbalancing problem doesn't h
HOWEVER, when removing "ssd_spread" from the format/mount options said unbalancing problem doesn't happen
KInteresting, I've never been able to reproduce this problem on any hardware, even back in the steamos days
KBut I will play with that
Vi've ran into it multiple times on bazzite
Vand i'm pretty sure that's what it is now. before i thought it was something with the compression level
KThere were users that ran into it on SteamOS too, with the SteamOS BTRFS script
Vtrial and error beating my head against the wall
KBut I have not once ever been able to reproduce it
KIt's definitely Hardware specific
KHardware being the actual SD card
KI'll see if removing it can be done without harming performance for others
KOtherwise we just have a new step for a minority of users to play with
Vwell, i know for a fact that the problem happens with these
Vhave had it happen on 3 different ones
Vbut yeah, since removing that mount/format option the btrfs partition is near perfectly balanced and the sd card is filling up with no issue
Vdigging into the btrfs docs, they don't recommend that option
VSince 4.14, the block layout optimizations have been dropped. This used to help with first generations of SSD devices. Their FTL (flash translation layer) was not effective and the optimization was supposed to improve the wear by better aligning blocks. This is no longer true with modern SSD devices and the optimization had no real benefit. Furthermore it caused increased fragmentation. The layout tuning has been kept intact for the option ssd_spread.
Vthe 'increased fragmentation' seems to be what's happening that's leading to the exess metadata writing
Vbut i'm not an expert, just a dumbass trying to beat their head against an issue
V
VJust noticed that in console
Vflatpaks using older backends and flathub nagging for the developers to update their dependencies
VAh
VFlathub the nagging ole granny
Von my last install i had to rebalance the sd cards like 5-6 times to fill them up. and here i remove one option in the /etc/defaults config file for it and the issue is gone. all that past pain waisted. :AquaPanic:
Ahuh, weird.
AI haven't actually tweaked any packages outside of mutter, mutter-common and gnome-settings-daemon but I don't know if cooler control fucks with those
KHello everyone someone know how to configure a cam to use in the waydroid???
V
VSomething is very wrong
VI'm on a fresh install and I can't use either of these
Vright click, properties, enable the run as executable box
VAlright I'll do that after the restart
VTrying to make my microsd work again
VBut it ain't showing up, lol
VAnd apparently bazzite despises restarting
Vit'a a gui shortcut for command line "(sudo) chmod +x /path/to/file/here" that flags a .desktop or .sh (sript) file as executable
Vgnome has a similar gui shortcut in their file manager
Bgamescope on the preview version doesn't actually have complete oled black on the corner, and no its not burn in
Bin kde, its not there, and going back to stable doesn't have it either
Bmagicblack is the greatest decky plugin ever for the oled frfr
VSo that thing you told me to do?
VIt made it vanish
VSame thing with the other one
Vmarking a file as executable doesn't delete it
VThen I don't understand why It isn't there anymore
VDo I have to reinstall bazzite again?
Kfor some reason, after I formatted my computer today, OBS seems to be destroying my performance while recording, am I alone on this one?
KI seem to have found the culprit, I was recording my entire screen, now I'm only recording the game's window, this is not impacting my performance anymore
the weird thig is: this did not happened before the formating, and this does not happen on my Steam Deck, which has a less powerfull hardware
the weird thig is: this did not happened before the formating, and this does not happen on my Steam Deck, which has a less powerfull hardware
VAnyone know what to do to get gamemode back?
VOkay I figured out how to make it come back
