this post was submitted on 30 Apr 2024
30 points (96.9% liked)

Linux

47952 readers
1675 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
30
How to figure out why BTRFS drive reports it is out of space (lemmy.sdf.org)
submitted 6 months ago by daq@lemmy.sdf.org to c/linux@lemmy.ml
15 comments fedilink hide all child comments
 
# sudo btrfs fi df /mnt/disk3
Data, single: total=12.70TiB, used=12.27TiB
System, DUP: total=8.00MiB, used=1.34MiB
Metadata, DUP: total=15.00GiB, used=14.50GiB
GlobalReserve, single: total=512.00MiB, used=608.00KiB

# mkdir /mnt/disk3/tst
mkdir: cannot create directory ‘tst’: No space left on device

I suspect this is BTRFS balancing issue, but even BTRFS's own utility is indicating there's still SOME space left. Certainly should be enough to create a directory.

Any ideas?

Just in general BTRFS default options for creating new volumes seem to not work well for disks that I intend to fill completely immediately after formatting. Are there better options for this use case? I just use

# mkfs.btrfs /dev/sdd1

you are viewing a single comment's thread
view the rest of the comments
[–] jlsalvador@lemmy.ml 10 points 6 months ago (3 children)

When you create a filesystem, there is a parameter named as "block percent free". This parameter should be "5%", so a 5% of your partition size can only be written by the "root" user.

You can decrease this value or just free some space. You can try to create files or folders as root as well.

[–] Hawke@lemmy.world 4 points 6 months ago* (last edited 6 months ago) (2 children)

Is there any reason this 5% number still holds true? Back in the days of 40 MB hard drives it made sense to make sure the system didn’t totally run out while root was fixing the low disk situation … but these days even 1% is still several gigabytes of space, not likely to run out that quickly.

[–] ryannathans@aussie.zone 2 points 6 months ago

Fragmentation probably but seems arbitrary

[–] daq@lemmy.sdf.org 3 points 6 months ago

Are you sure that's the case with btrfs? I know ext has that feature. My understanding is btrfs just has a global reserve that can be used for any data in an low space situation.

# sudo btrfs fi usage /mnt/disk3
Overall:
    Device size:                  12.73TiB
    Device allocated:             12.73TiB
    Device unallocated:            1.00MiB
    Device missing:                  0.00B
    Device slack:                    0.00B
    Used:                         12.29TiB
    Free (estimated):            449.43GiB      (min: 449.43GiB)
    Free (statfs, df):           449.43GiB
    Data ratio:                       1.00
    Metadata ratio:                   2.00
    Global reserve:              512.00MiB      (used: 0.00B)
    Multiple profiles:                  no

Data,single: Size:12.70TiB, Used:12.26TiB (96.55%)
   /dev/sdd1      12.70TiB

Metadata,DUP: Size:15.00GiB, Used:14.49GiB (96.58%)
   /dev/sdd1      30.00GiB

System,DUP: Size:8.00MiB, Used:1.34MiB (16.80%)
   /dev/sdd1      16.00MiB

Unallocated:
   /dev/sdd1       1.00MiB
[–] narc0tic_bird@lemm.ee 3 points 6 months ago

You/I learn something new every day. Cool info!