Running out of disk space. Something in the Kub. is accummulating log files that take up all the partition (50 Gb).

[jglen490]

No. Gi = gibi (1024 cubed). So GiB = gibibytes. G = giga (1000 cubed). So GB = gigabytes.

The calculation ends up with a different number, based on 1000 vs. 1024.

In general conversation, it's a distinction without a difference. In IT, is a distinction that could run one out of space.

[RLynwood]

Thank you.
I still need direction from my last post #42 displaying the results of my attempts to follow oshunluvr's previous instruction. I clearly don't understand something critical here.

[oshunluvr]

Thanks again. This looks great.
Will you explain what GiB is?

I don't understand option 3.

It looks like I've already added btrfs to /dev/sda4 or created it separately (I tried to add /sda3's btrfs to /sda4 per your instructions (see next line), & it said it was already there).
"To add the empty partition, it's as simple as sudo btrfs device add <device> <mountpoint>" So, it's sudo btrfs /dev/sda add /dev/sdb /mnt ? This didn't work: it said that btrfs already was in /dev/sda4. So I tried to force the /sda3 btrfs to overwrite /sda4's btrfs and got this result:
ubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 -f
btrfs device add: not enough arguments: 1 but at least 2 expected

Please show me what I'm doing wrong.

I posted this:

sudo btrfs device add <device> <mountpoint>

You skipped the mount point.

To expand a bit: you're adding a device to an existing btrfs file system. The add command expects the file system you are adding to is mounted. So you mount it somewhere, then "add" the device.

If you have, in fact, already "added" it to /dev/sda3 it wouldn't report it's size as 50GB, it would report it as 100GB.

[RLynwood]

I thought this was clear enough that I could figure it out, but, no. I'm flummoxed.
Here's the last series I've tried:

kubuntu@kubuntu:~$ sudo mount /dev/sda3 /mnt
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 /mnt
/dev/sda4 appears to contain an existing filesystem (btrfs).
ERROR: use the -f option to force overwrite of /dev/sda4
kubuntu@kubuntu:~$ btrfs device add /dev/sda4 /mnt -f
ERROR: mount check: cannot open /dev/sda4: Permission denied
ERROR: cannot check mount status of /dev/sda4: Permission denied
kubuntu@kubuntu:~$

I still have my terminal up with all previous attempts, so if you want/need earlier attempts, I still can provide them.

Now what?

[oshunluvr]

You left out sudo on the last command.

[RLynwood]

It may be that simple, but I still haven't gotten it.
Here is the display for my last series' of attempts. What the dickens am I missing?

kubuntu@kubuntu:~$ sudo mount /dev/sda3 /mnt
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 /mnt
/dev/sda4 appears to contain an existing filesystem (btrfs).
ERROR: use the -f option to force overwrite of /dev/sda4
kubuntu@kubuntu:~$ btrfs device add /dev/sda4 /mnt -f
ERROR: mount check: cannot open /dev/sda4: Permission denied
ERROR: cannot check mount status of /dev/sda4: Permission denied
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 /mnt -f
ERROR: /dev/sda4 is mounted
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 -f
btrfs device add: not enough arguments: 1 but at least 2 expected
kubuntu@kubuntu:~$ sudo btrfs device /dev/sda3 add /dev/sda4 -f
btrfs device: unknown token '/dev/sda3'
usage: btrfs device <command> [<args>]

btrfs device add [options] <device> [<device>...] <path>
Add one or more devices to a mounted filesystem.
btrfs device delete <device>|<devid> [<device>|<devid>...] <path>
btrfs device remove <device>|<devid> [<device>|<devid>...] <path>
Remove a device from a filesystem
btrfs device scan [-d|--all-devices] <device> [<device>...]
btrfs device scan -u|--forget [<device>...]
Scan or forget (unregister) devices of btrfs filesystems
btrfs device ready <device>
Check and wait until a group of devices of a filesystem is ready for mount
btrfs device stats [options] <path>|<device>
Show device IO error statistics
btrfs device usage [options] <path> [<path>..]
Show detailed information about internal allocations in devices.

manage and query devices in the filesystem
kubuntu@kubuntu:~$ sudo mount /dev/sda3 /mnt
mount: /mnt: /dev/sda3 already mounted on /mnt.
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 /mnt
/dev/sda4 appears to contain an existing filesystem (btrfs).
ERROR: use the -f option to force overwrite of /dev/sda4
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 /mnt -f
ERROR: /dev/sda4 is mounted
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 -f
btrfs device add: not enough arguments: 1 but at least 2 expected
kubuntu@kubuntu:~$ sudo mount /dev/sda3 /mnt
mount: /mnt: /dev/sda3 already mounted on /mnt.
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 /mnt
/dev/sda4 appears to contain an existing filesystem (btrfs).
ERROR: use the -f option to force overwrite of /dev/sda4
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 -f
btrfs device add: not enough arguments: 1 but at least 2 expected
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 /mnt -f
ERROR: /dev/sda4 is mounted
kubuntu@kubuntu:~$ sudo btrfs device add /dev/sda4 -f
btrfs device add: not enough arguments: 1 but at least 2 expected
kubuntu@kubuntu:~$

[oshunluvr]

I suggest you reboot the to the USB again and go back to post #33 in this thread and enter exactly what is there.

Do not leave out sudo and expect it to work.

If the error message says to use the -f option, use it WITH SUDO.

You cannot rearrange the entries in the command or leave out parts or add other parts and expect it to work.

[RLynwood]

Whew. Ok. I certainly didn't intend to skip anything (I mistakenly missed sudo only once), and I couldn't figure out what I was missing. The automated help instructions weren't clear enough for me.
I'll do that, but that means that, if it doesn't work, I'll have to start all over copying/storing all the login infos to use the computer until Main gets accessible because it's so much more powerful than the 15-yr.-old, low powered, borrowed laptop that does have much of my stored info.

[RLynwood]

I'm not working from a Live USB any more; now I've found I have another installation of Kub. 22.04 on a second SSD (had completely forgotten about it), and I'm using it. So, does your last instruction still hold, or do you advise a different command sequence? Thanks.

[oshunluvr]

Nope, exactly the same set of commands. HOWEVER, depending on how your computer assigns device names the drive device may no longer be /dev/sda.

I have had computers in the past where, when booting from a drive, always make that drive SDA and the others follow. My current one does not do that.

The lsblk command should help you determine which drive is which - just in case it changes

[RLynwood]

Just as I suspected, the SSD I'm using (the whole thing) is sdb. The two partitions I've been addressing still are sda3, -4. However, here's the result:

ynn@lynn-All-Series:~$ sudo mount /dev/sda3 /mnt
sudo btrfs balance start /mnt
WARNING:

Full balance without filters requested. This operation is very
intense and takes potentially very long. It is recommended to
use the balance filters to narrow down the scope of balance.
Use 'btrfs balance start --full-balance' option to skip this
warning. The operation will start in 10 seconds.
Use Ctrl-C to stop it.
10 9 8 7 6 5 4 3 2 1
Starting balance without any filters.
ERROR: error during balancing '/mnt': No space left on device
There may be more info in syslog - try dmesg | tail

This didn't work:
lynn@lynn-All-Series:~$ sudo /dev/sda3 dmesg | tail
sudo: /dev/sda3: command not found

I tried this next:
lynn@lynn-All-Series:~$ sudo dmesg | tail
[64811.990273] BTRFS info (device sda3): relocating block group 5667553280 flags data
[64812.114599] BTRFS info (device sda3): relocating block group 4593811456 flags data
[64812.176229] BTRFS info (device sda3): relocating block group 3520069632 flags data
[64812.209996] BTRFS info (device sda3): relocating block group 2446327808 flags data
[64812.312347] BTRFS info (device sda3): relocating block group 1372585984 flags data
[64812.477429] BTRFS info (device sda3): relocating block group 298844160 flags data
[64812.564628] BTRFS info (device sda3): relocating block group 30408704 flags metadata|dup
[64817.264309] BTRFS info (device sda3): relocating block group 22020096 flags system|dup
[64817.590811] BTRFS info (device sda3): 50 enospc errors during balance
[64817.590816] BTRFS info (device sda3): balance: ended with status: -28

does this mean anything to you?

I used Filelight to look at sda3's @ and @/home and see that I cans save any image from it as an .svg. I don't see how to display that in a post here? It does reflect what we've seen from the cl output.
It shows that, @/home takes 23.6 GB (32%), all of which is in my named home (/home/lynn), and -./local takes 18.0 GB, all of which is in -/.local/share, 15.7% of which is in /baloo. I don't remember what that is. If I could get that out of there, esp. by moving it to /sdb, where I could evaluate its contents. I'm sure I could boot into sda3 and clean up the rest.
Similarly, @/ has 11.1 GB in /var, of which 8.6 is in /var/lib, and 9.5 in /usr, of which 7.3 GB is in /usr/lib.

Btw, it looks like you've got quite a rig, there.

[RLynwood]

I just made a humongous mistake &, I believe, preliminarily wiped ALL of sda3. So further help for now is not necessary. So, though I don't want to close this request for help, I'm going to stop posting until I learn if my OS is recoverable. I can't tell you how much I appreciate all the help you've given.