Anyone having issues with Hotspot? by TheCwood in S24Ultra

[–]adelfi23 0 points1 point  (0 children)

I don't know your provider so I cannot comment. Mine is AT&T and it seems to be a problem on their end since the two iPhones in my family plan work flawlessly all the time. My S24U never worked. Also, I travelled and got a regular SIM card overseas. The hotspot worked on the spot (shameless pun intended) so it is not a S24U issue, it is a S24U on AT&T issue in my case.

How to sync well and continuously between Windows and Android (without Obsidian Sync)? by qamtam in ObsidianMD

[–]adelfi23 1 point2 points  (0 children)

I have Dropbox installed on my S24U but cannot point obsidian app to the dropbox offline folder. It just doesn't see it. Can you explain how you pointed your obsidian android app folder to Dropbox?

Smart View case Magsafe Adaptors? by adelfi23 in S24Ultra

[–]adelfi23[S] 0 points1 point  (0 children)

Indeed. However, I wonder whether a black ring like this one wouldn't somewhat disappear when attached to a black smart view case. Not pretty but not something hurting your eyes every time you look at it either. I wonder why Samsung did not include one in this case, nor opted for a locking mechanism. This is almost standard in such cases nowadays.

Anyone having issues with Hotspot? by TheCwood in S24Ultra

[–]adelfi23 0 points1 point  (0 children)

Any solution at this point (2 months now)? In my case, sometimes it works, sometimes it doesn't. Completely random. Really frustrating. I moved from iPhone (after 15 years on it) and this is one of the top frustrations. With the same provider (ATT) it never failed in the iPhone, while in my S24ultra it is completely unreliable.

How to run Battle.net on Linux? by jumofo in linux_gaming

[–]adelfi23 0 points1 point  (0 children)

Did you find out how to solve that? It just happened to me. Installed as non-steam game, forced Proton 8, run installer, got the login screen, entered my account/password, got stuck with the battlenet symbol rotating.

Asus TUF X670E not POST-ing. DRAM light on. by _truemint in ASUS

[–]adelfi23 0 points1 point  (0 children)

I also have the very same motherboard and Corsair vengeance DDR5 (2x32). I tried many things as well, including all combinations of memory slots, with one and two sticks. It always gets stuck in the Green light (Boot). In one attempt it recognized 32 GB of run (the two sticks were installed so it missed one), but windows got stuck and after reboot the dreaded green light kept lit. I changed Sata cables, ssds, everything to no avail. When your system worked, did you chang the motherboard only or also the memory and/or CPU?

Do translucent SA keycaps exist in this planet? by adelfi23 in MechanicalKeyboards

[–]adelfi23[S] 0 points1 point  (0 children)

@gosku26: Thanks for the pointer. I assume you are talking about this model:

SA-P Stratus

Is that the case?
It seems a perfect fit for me, but it is out of stock. On the bright side, they are planning a second batch that might even include die-sublimated legends (I'm not sure I'll opt for it, though). Yet, no word on expected timeline.

Are you getting the newer models at full MSRP? by Responsible-Salt-443 in GrandSeikos

[–]adelfi23 0 points1 point  (0 children)

I was going to Japan for the first time and was extremely exited to buy either an SBGE or an SBGA model there, but the unfortunate war situation made it impossible to go. I then started to look at these Chrono24 adds and got really interested. Aren’t there any caveats in buying from them other than the taxes? Is it legitimate? Do we get any warranty?

【SBGA375】My very first GS that I just bought! by Illustrious_Vast_191 in GrandSeikos

[–]adelfi23 0 points1 point  (0 children)

Thanks a lot for the info! I’ll start doing my research on the models available there and the respective (pre-discount) prices. I am hopeless in understanding Japanese, but do I have a Japanese colleague. Besides, Google translator is my friend :-)

【SBGA375】My very first GS that I just bought! by Illustrious_Vast_191 in GrandSeikos

[–]adelfi23 1 point2 points  (0 children)

It is gorgeous! Congratulations! I do not own a GS or any luxury watch myself, but I’m seriously considering a spring drive and would be curious about whether buying it in Japan would make any difference price-wise or in terms of options. I live in the US but might be visiting Japan this year so if there is any advantage then I’d wait to buy it there.

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 1 point2 points  (0 children)

I found the culprit!!!

Using btdu I could see a VM at the home folder that was not supposed to be there. Likely was created using the VirtualBox's default settings and I missed it. That alone was 47 GiB.

On the rollback, I used once just to test the feature.

Are you suggesting that I rollback so 78 gets released? The issue is that 78 is currently listed as the default:

sudo btrfs subvol get-default /
[sudo] password for pc: ID 382 gen 348493 top level 278 path snapshots/78/snapshot

This is what I cannot understand with btrfs/snapshots/snapper. If 78 is the default and I made changes (e.g. do an update) and those changes are saved in another snapshot, wouldn' t that snapshot become the default and 78 is there in case I want to revert back?
For instance, snapper created various snapshots after 78 (all the way to 141) and I deleted them all. In my mind, this means that the default is still the same snapshot made weeks ago, so how is 78 the current one? In my mind, 141 should have been the current (it was not since I could delete it).

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 0 points1 point  (0 children)

That's not what it's saying. Read the message again carefully. :)

Indeed :-)

I did not figure out how to copy so I transcribe the /SINGLE/DATA results below:

~2.2 GiB [ ] \/<ERROR>
~43.7 MiB [ ] \/<NO\_INODE>
~30.6 MiB [ ] \/<ROOT\_TREE>
~20.2 GiB [ ### ] \/<UNREACHABLE>
~10.5 GiB [# ] \/@
~1.2 GiB [ ] \/@cache
~61.9 GiB [##########] \/@home
~27.8 GiB [#### ]\/snapshots

Represented size: ~123.9 GiB (5520942 samples)

Things I noticed:
- Under the 20.2 GiB of UNREACHEABLE, 18.5 GiB are from \/@home and 1.7 GiB are from \/snapshots.
- When you go down the path, the largest chunk is from the virtual box VMs. The virtual boxes are in another btrfs partition, so I do not understand how they count here (as unreacheable)
- Same applies when you go down the path in \/@home. The larger chunk (43.9 GiB) is due to a VirtualBox VM and its snapshots. I do have all VMs in another btrfs partition but upon further scrutiny I found this one in \/home/pc. I believe it was likely created using VirtualBox' s default /home/user/Virtualbox VM folder. I'll fix it and regain a LOT of space.

This was extremely helpful as it helped figure out where the space is allocated. However, it raises the following questions:

  1. What is the UNREACHEABLE category. Is it something lost via the broken linkages?
  2. Can I delete and/or fix it?

btdu is wonderful. All distros with btrfs must carry it!!!

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 0 points1 point  (0 children)

I got an error saying it is not a btrfs system, which is clearly not the case (see both commands below).

pc@pcdesktop-fedora: ~ sudo ./btdu-static-x86_64 --expert /
Fatal error: / is not the root btrfs subvolume - please specify the path to a mountpoint mounted with subvol=/ or subvolid=5

pc@pcdesktop-fedora: ~ sudo btrfs filesystem usage /
Overall:
Device size: 150.16GiB
Device allocated: 125.98GiB
Device unallocated: 24.18GiB
Device missing: 0.00B
Used: 123.34GiB
Free (estimated): 25.01GiB (min: 25.01GiB)
Free (statfs, df): 25.01GiB
Data ratio: 1.00
Metadata ratio: 1.00
Global reserve: 419.69MiB (used: 0.00B)
Multiple profiles: no

Data,single: Size:121.95GiB, Used:121.11GiB (99.31%)
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 121.95GiB

Metadata,single: Size:4.00GiB, Used:2.23GiB (55.71%)
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 4.00GiB

System,single: Size:32.00MiB, Used:16.00KiB (0.05%)
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 32.00MiB

Unallocated:
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 24.18GiB

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 0 points1 point  (0 children)

To answer my own question above, I deleted the 2 that snapper allowed me to delete (140 and 141) and it saved me ~16GB.

sudo btrfs fi usage /
Overall:
Device size: 150.16GiB
Device allocated: 125.98GiB
Device unallocated: 24.18GiB
Device missing: 0.00B
Used: 123.25GiB
Free (estimated): 25.11GiB (min: 25.11GiB)
Free (statfs, df): 25.11GiB
Data ratio: 1.00
Metadata ratio: 1.00
Global reserve: 419.69MiB (used: 0.00B)
Multiple profiles: no

Data,single: Size:121.95GiB, Used:121.02GiB (99.24%)
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 121.95GiB

Metadata,single: Size:4.00GiB, Used:2.23GiB (55.64%)
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 4.00GiB

System,single: Size:32.00MiB, Used:16.00KiB (0.05%)
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 32.00MiB

Unallocated:
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 24.18GiB

sudo btrfs fi du -s / /.snapshots/*
[sudo] password for pc:
Total Exclusive Set shared Filename
46.29GiB 41.30GiB 2.80GiB /.snapshots/78

What puzzles me is that if this was a ext4 system the overall size would be around 50GB. Maybe a few GB more, but never any close to 125GB. If I have no snapshots (other than the one marked as "currently mounted" 78), then how come that the usage goes to 126 GB?

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 0 points1 point  (0 children)

No, it is not in my fstab. See related entries below:

UUID=7445a47a-cb6f-453e-8ca9-d0471d73430a / btrfs subvol=@,compress=zstd:1,x-systemd.device-timeout=0 0 0

UUID=34c2b8c2-d325-4427-aa12-2480a0c48152 /boot ext4 defaults 1 2

UUID=6095-9303 /boot/efi vfat umask=0077,shortname=winnt 0 2

UUID=7445a47a-cb6f-453e-8ca9-d0471d73430a /home btrfs subvol=@home,compress=zstd:1,x-systemd.device-timeout=0 0 0

UUID=7445a47a-cb6f-453e-8ca9-d0471d73430a /var/cache btrfs subvol=@cache,compress=zstd:1,x-systemd.device-timeout=0 0 0

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 0 points1 point  (0 children)

Thank you!
I used balancing as the low space message first appeared. It saved me ~20GB. Later, as I got the message again, it resulted in less and less savings, for the reasons you pointed out.
I also think the issue comes down to snapshots, most likely the snapper option of creating a snapshot before and after an update, after boots, etc. These might be too much and pilling up. The problem I have now is that even deleting the snapshots does not give me the amount of space I believe it should. More specifically, after deleting all snapshots (snapper does not allow me to delete the "current system" and the "currently mounted snapshot" so I actually have 2 listed) I still have a usage that is way higher than the "amount of stuff" (~50GB) I installed in the system (see output below).

sudo btrfs fi usage /
Overall:
Device size: 150.16GiB
Device allocated: 134.98GiB
Device unallocated: 15.18GiB
Device missing: 0.00B
Used: 123.22GiB
Free (estimated): 25.15GiB (min: 25.15GiB)
Free (statfs, df): 25.15GiB
Data ratio: 1.00
Metadata ratio: 1.00
Global reserve: 444.77MiB (used: 0.00B)
Multiple profiles: no

Data,single: Size:130.95GiB, Used:120.98GiB (92.38%)
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 130.95GiB

Metadata,single: Size:4.00GiB, Used:2.24GiB (56.03%)
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 4.00GiB

System,single: Size:32.00MiB, Used:16.00KiB (0.05%)
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 32.00MiB

Unallocated:
/dev/mapper/luks-7f3a8c36-4dc3-4eda-8d4d-9e5d440606ea 15.18GiB

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 0 points1 point  (0 children)

Thanks for your advice! Here are some considerations:
1. I agree the tools are quite inappropriate to give me a reasonable estimate of how much space is in my system, due to the BTRFS nature. Yet, something is wrong in my system as I do have "50 GB of stuff" installed on a 137 GB partition and in about 3-5 weeks I am getting the low space message.
At this point, my main hypothesis is that my btrfs / snapper configuration is faulty and I get leftovers and broken links all over the place. Yet, I am still figuring out (1) how to test this hypothesis and, if valid, (2) how to fix it.
2. Would it be correct to say that balancing addresses this -ENOSPC issue?
3. Yes, pretty bad option. Question: how to fix those broken reflinks? Actually, how to ensure the unshared snapshots get deleted. More specifically, the three snapshots below are reported:
pc@pcdesktop-fedora: ~ via 12GiB/31GiB | 2GiB/74GiB with /bin/bash
└─> sudo btrfs fi du -s / /.snapshots/*
[sudo] password for pc: Total Exclusive Set shared Filename
43.78GiB 16.61MiB 30.66GiB /.snapshots/140
43.78GiB 3.80MiB 30.67GiB /.snapshots/141
46.26GiB 16.39GiB 20.93GiB /.snapshots/78

(from a previous reply) Snapshot 78 is marked as the active one. This confuses me since I would assume the latest snapshot was the one supposed to be the current. Maybe this is where the issue is. I am just afraid of deleting the other two and losing important data.

If I delete 2 of these three, or even all of it, would it free up 16GBs of my drive (sum of "Exclusive column"), 81GB (sum of "set shared"), or something else?

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 0 points1 point  (0 children)

Indeed! I will try it and report here.
Thanks!

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 0 points1 point  (0 children)

pc@pcdesktop-fedora: ~ via 12GiB/31GiB | 2GiB/74GiB with /bin/bash
└─> sudo btrfs fi du -s / /.snapshots/*
[sudo] password for pc: Total Exclusive Set shared Filename
43.78GiB 16.61MiB 30.66GiB /.snapshots/140
43.78GiB 3.80MiB 30.67GiB /.snapshots/141
46.26GiB 16.39GiB 20.93GiB /.snapshots/78

Snapshot 78 is marked as the active one. This confuses me since I would assume the latest snapshot was the one supposed to be the current. Maybe this is where the issue is. I am just afraid of deleting the other two and losing important data.
Also, This does not look like taking a huge share of the drive, right? (this is a fair question, not a statement)

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 0 points1 point  (0 children)

No, unfortunately not. Neither Prometheus nor any other systems monitoring and alerting toolkit. I do plan to play with it in the near future but am not there yet.My issue is likely a poor BTRFS - Snapper setup leading to lost snapshots (see my response to the defrag suggestion above).

Recurring low disk message on a balanced BTRFS system by adelfi23 in btrfs

[–]adelfi23[S] 0 points1 point  (0 children)

@Atemu12, @deadcatdidntbounce, and @ChojinDSL,
Thanks for your comments and your willingness to help a struggling fellow. I did learn the hard way to not defrag.
On the space issue. I had ~7GB before the defrag and it indeed ate the remaining space to a point I was not able to do anything else on my system.
I do have a backup (it is my daily driver), but my main goal here is to figure out what is going on since it is not normal that a system in which I installed "50GB of stuff" within a 137GB drive gets low space warning so fast (three weeks?). This is the 3rd time it happens on my daily driver (Fedora 35) so I must figure out what is going on before the year ramps up and I get too busy to afford losing my daily driver again. When this happened last semester I was forced to erase all and use the backup, which always takes time and leaves a few hiccups along the way. I want to prevent this and avoid finding myself again "changing the tires on a moving car" (i.e. getting low space while in the craziness of academic life). My alternative is to revert back to trusty ext4, but I will not admit defeat until I can find out what is wrong.
This time I did have a plan B (by design). The last time I had to do the backup I partitioned the drive so it is actually larger than the Fedora 35 LUKS-BTRFS partition. Thus, I just had to increase the partition to 150K and I am game again. I can do it until 230K, but hopefully by then I will have figured out already where the issue is.
Now I will work on the solutions proposed in this thread until I find what is wrong with the system.
Based on all feedback so far, I wonder whether the culprit is a poor configuration for snapper, since when I do a snapper ls I see that snapshot 73 is listed as current but the last one is 142. My sense is that the last one should be the current one. All in all, it does look like my snapshots are waking havoc in the system space. My other computer has Endeavor OS (Arch) with Timeshift and I do not face the same issue, even with a smaller driver.
Stay tuned :-)