Skip to contentSkip to conversation

No space left on device (again)

DISCUSSION Marcus Sundman 6 participants 12 messages Feb 25, 2014 – Feb 27, 2014 Btrfs file system

lore
Share & tools
lore
#0 lore raw

Hi

I get "No space left on device" and it is unclear why:

Quoted 7 lines
# df -h|grep sda3
/dev/sda3       413G  368G   45G  90% /home
# btrfs filesystem show /dev/sda3
Label: 'home'  uuid: 46279061-51f4-40c2-afd0-61d6faab7f60
    Total devices 1 FS bytes used 371.11GB
    devid    1 size 412.54GB used 412.54GB path /dev/sda3
Quoted 6 lines

Btrfs v0.20-rc1

# btrfs filesystem df /home
Data: total=410.52GB, used=369.61GB
System: total=4.00MB, used=64.00KB
Metadata: total=2.01GB, used=1.50GB
#

So, 'data' and 'metadata' seem to be fine(?), but 'system' is a bit low. Is that it? If so, can I do something about it? Or should I look somewhere else?

I really wish I could get a warning before running out of disk space, instead of everything breaking suddenly when there seems to be lots and lots of space left.

- Marcus

#1 lore raw

370GB of 410GB used isn't really "fine", it's over 90% usage.

That said, I'd be interested to know why btrfs fi show /dev/sda3 shows 412.54G used, but btrfs fi df /home shows 379G used...

Quoted 28 lines · Marcus Sundman

Hi

I get "No space left on device" and it is unclear why:

Quoted 7 lines
# df -h|grep sda3
/dev/sda3       413G  368G   45G  90% /home
# btrfs filesystem show /dev/sda3
Label: 'home'  uuid: 46279061-51f4-40c2-afd0-61d6faab7f60
    Total devices 1 FS bytes used 371.11GB
    devid    1 size 412.54GB used 412.54GB path /dev/sda3
Quoted 6 lines

Btrfs v0.20-rc1

# btrfs filesystem df /home
Data: total=410.52GB, used=369.61GB
System: total=4.00MB, used=64.00KB
Metadata: total=2.01GB, used=1.50GB
#

So, 'data' and 'metadata' seem to be fine(?), but 'system' is a bit low. Is that it? If so, can I do something about it? Or should I look somewhere else?

I really wish I could get a warning before running out of disk space, instead of everything breaking suddenly when there seems to be lots and lots of space left.

- Marcus

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw
Quoted 1 line · Jim Salter

370GB of 410GB used isn't really "fine", it's over 90% usage.

Still, 45 gigs should be free there. If those 45 gigs aren't really there then it shouldn't say they are there, imho.

Quoted 1 line

That said, I'd be interested to know why btrfs fi show /dev/sda3 shows 412.54G used, but btrfs fi df /home shows 379G used...

The former also says "bytes used 371.11GB" and there's not *that* much difference between "371.11" and "369.61" gigs. The devid line seems to always say "412.54GB used 412.54GB" no matter how much is actually in use. I have no idea what these numbers actually mean.

Quoted 34 lines · Marcus Sundman
Quoted 28 lines

Hi

I get "No space left on device" and it is unclear why:

Quoted 7 lines
# df -h|grep sda3
/dev/sda3       413G  368G   45G  90% /home
# btrfs filesystem show /dev/sda3
Label: 'home'  uuid: 46279061-51f4-40c2-afd0-61d6faab7f60
    Total devices 1 FS bytes used 371.11GB
    devid    1 size 412.54GB used 412.54GB path /dev/sda3
Quoted 6 lines

Btrfs v0.20-rc1

# btrfs filesystem df /home
Data: total=410.52GB, used=369.61GB
System: total=4.00MB, used=64.00KB
Metadata: total=2.01GB, used=1.50GB
#

So, 'data' and 'metadata' seem to be fine(?), but 'system' is a bit low. Is that it? If so, can I do something about it? Or should I look somewhere else?

I really wish I could get a warning before running out of disk space, instead of everything breaking suddenly when there seems to be lots and lots of space left.

- Marcus

Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw
In reply to Jim Salter
Quoted 4 lines · Jim Salter

370GB of 410GB used isn't really "fine", it's over 90% usage.

That said, I'd be interested to know why btrfs fi show /dev/sda3 shows 412.54G used, but btrfs fi df /home shows 379G used...

This is an FAQ...

btrfs fi show tells you how much is allocated out of the available
pool on each disk. btrfs fi df then shows how much of that allocated space (in each category) is used.

The problem here is also in the FAQ: the metadata is close to full
-- typically something like 500-750 MiB of headroom is needed in metadata. The FS can't allocate more metadata because it's allocated everything already (total=used in btrfs fi show), so the solution is to do a filtered balance:

btrfs balance start -dusage=5 /mountpoint

Hugo.

Quoted 30 lines · Marcus Sundman
Quoted 28 lines

Hi

I get "No space left on device" and it is unclear why:

Quoted 7 lines
# df -h|grep sda3
/dev/sda3       413G  368G   45G  90% /home
# btrfs filesystem show /dev/sda3
Label: 'home'  uuid: 46279061-51f4-40c2-afd0-61d6faab7f60
   Total devices 1 FS bytes used 371.11GB
   devid    1 size 412.54GB used 412.54GB path /dev/sda3
Quoted 6 lines

Btrfs v0.20-rc1

# btrfs filesystem df /home
Data: total=410.52GB, used=369.61GB
System: total=4.00MB, used=64.00KB
Metadata: total=2.01GB, used=1.50GB
#

So, 'data' and 'metadata' seem to be fine(?), but 'system' is a bit low. Is that it? If so, can I do something about it? Or should I look somewhere else?

I really wish I could get a warning before running out of disk space, instead of everything breaking suddenly when there seems to be lots and lots of space left.

- Marcus

Signature · 4 lines
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
    --- Jazz is the sort of music where no-one plays anything the ---    
                             same way once.                              
#4 lore raw
Quoted 10 lines · Hugo Mills
Quoted 4 lines · Jim Salter

370GB of 410GB used isn't really "fine", it's over 90% usage.

That said, I'd be interested to know why btrfs fi show /dev/sda3 shows 412.54G used, but btrfs fi df /home shows 379G used...

This is an FAQ...

btrfs fi show tells you how much is allocated out of the available
pool on each disk. btrfs fi df then shows how much of that allocated space (in each category) is used.

What is the difference between the "used 371.11GB" and the "used 412.54GB" displayed by "btrfs fi show"?

Quoted 7 lines

The problem here is also in the FAQ: the metadata is close to full
-- typically something like 500-750 MiB of headroom is needed in metadata. The FS can't allocate more metadata because it's allocated everything already (total=used in btrfs fi show), so the solution is to do a filtered balance:

btrfs balance start -dusage=5 /mountpoint

Of course that was the first thing I tried, and it didn't help *at* *all*:

Quoted 3 lines
# btrfs filesystem balance start -dusage=5 /home
Done, had to relocate 0 out of 415 chunks
#

... and it really didn't free anything.

Quoted 28 lines
Quoted 28 lines · Marcus Sundman
Quoted 27 lines

Hi

I get "No space left on device" and it is unclear why:

Quoted 7 lines
# df -h|grep sda3
/dev/sda3       413G  368G   45G  90% /home
# btrfs filesystem show /dev/sda3
Label: 'home'  uuid: 46279061-51f4-40c2-afd0-61d6faab7f60
    Total devices 1 FS bytes used 371.11GB
    devid    1 size 412.54GB used 412.54GB path /dev/sda3
Quoted 6 lines

Btrfs v0.20-rc1

# btrfs filesystem df /home
Data: total=410.52GB, used=369.61GB
System: total=4.00MB, used=64.00KB
Metadata: total=2.01GB, used=1.50GB
#

So, 'data' and 'metadata' seem to be fine(?), but 'system' is a bit low. Is that it? If so, can I do something about it? Or should I look somewhere else?

I really wish I could get a warning before running out of disk space, instead of everything breaking suddenly when there seems to be lots and lots of space left.

- Marcus

#5 lore raw

Try btrfs filesystem balance start -dusage=15 /home, and gradually increase it until you see it relocate at least one chunk.

Quoted 74 lines · Marcus Sundman
Quoted 5 lines · Hugo Mills
Quoted 3 lines · Jim Salter

370GB of 410GB used isn't really "fine", it's over 90% usage.

Quoted 8 lines
Quoted 2 lines

That said, I'd be interested to know why btrfs fi show /dev/sda3 shows 412.54G used, but btrfs fi df /home shows 379G used...

This is an FAQ...

btrfs fi show tells you how much is allocated out of the available
pool on each disk. btrfs fi df then shows how much of that allocated space (in each category) is used.

What is the difference between the "used 371.11GB" and the "used 412.54GB" displayed by "btrfs fi show"?

Quoted 7 lines

The problem here is also in the FAQ: the metadata is close to full
-- typically something like 500-750 MiB of headroom is needed in metadata. The FS can't allocate more metadata because it's allocated everything already (total=used in btrfs fi show), so the solution is to do a filtered balance:

btrfs balance start -dusage=5 /mountpoint

Of course that was the first thing I tried, and it didn't help *at* *all*:

Quoted 3 lines
# btrfs filesystem balance start -dusage=5 /home
Done, had to relocate 0 out of 415 chunks
#

... and it really didn't free anything.

Quoted 24 lines
Quoted 24 lines · Marcus Sundman
Quoted 23 lines

Hi

I get "No space left on device" and it is unclear why:

Quoted 7 lines
# df -h|grep sda3
/dev/sda3       413G  368G   45G  90% /home
# btrfs filesystem show /dev/sda3
Label: 'home'  uuid: 46279061-51f4-40c2-afd0-61d6faab7f60
    Total devices 1 FS bytes used 371.11GB
    devid    1 size 412.54GB used 412.54GB path /dev/sda3
Quoted 6 lines

Btrfs v0.20-rc1

# btrfs filesystem df /home
Data: total=410.52GB, used=369.61GB
System: total=4.00MB, used=64.00KB
Metadata: total=2.01GB, used=1.50GB
#

So, 'data' and 'metadata' seem to be fine(?), but 'system' is a bit low. Is that it? If so, can I do something about it? Or should I look somewhere else?

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

I really wish I could get a warning before running out of disk space, instead of everything breaking suddenly when there seems to be lots and lots of space left.

- Marcus

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#6 lore raw
In reply to Marcus Sundman

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 22 lines · Marcus Sundman
Quoted 11 lines · Hugo Mills
Quoted 5 lines · Jim Salter

370GB of 410GB used isn't really "fine", it's over 90% usage.

That said, I'd be interested to know why btrfs fi show /dev/sda3 shows 412.54G used, but btrfs fi df /home shows 379G used...

This is an FAQ...

btrfs fi show tells you how much is allocated out of the available pool on each disk. btrfs fi df then shows how much of that allocated space (in each category) is used.

What is the difference between the "used 371.11GB" and the "used 412.54GB" displayed by "btrfs fi show"?

Quoted 6 lines

The problem here is also in the FAQ: the metadata is close to full -- typically something like 500-750 MiB of headroom is needed in metadata. The FS can't allocate more metadata because it's allocated everything already (total=used in btrfs fi show), so the solution is to do a filtered balance:

Quoted 5 lines
Quoted 1 line

btrfs balance start -dusage=5 /mountpoint

Of course that was the first thing I tried, and it didn't help *at* *all*:

The -dusage=<number> is a means to an end, so if that doesn't work try a larger number, up to 100. Really once you pass 50 and it's not working then it's time to just do a balance. The next thing is to use compression (too late for this option really) or add another disk. Thanks,

Josef

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTDP1mAAoJEANb+wAKly3BQooQAMjRfSc0fJcrVFhNqAXvuxKO f9ALYcENk7mVEMiyPg9v/7oiHW+FSQuJxaJ+yPlLTvepFmh3VE00t4PHsTCheAld KdIoP9KzvCrmPSH5YxBg9Tmk60lonYnGfCsggK3kgRP8JIHUcBRKzlFKAc3p8vzY UEEYLS0AYXvBAPdY3bUwhB5txMDvNbetew8ak5nUgZaC1J4rWe7LL6ccv845hhf5 OHcKLu3MjR6ejW9qDK9RC2ryjCY+vDCUMO4VPpma3OZ6OHA3g7niaXYqBEvht7O0 yNeGQA54O1goIFo9knPG4XE7WurlF69n+knQA7dsqjux9bIXHVClCCwsrUpXJIY3 98KigtPVz737j1dNqaeQdn6xl6kwRpj2lRhWuPBZ1AnJNWr1cLK2jmWOuFmyrdi8 vTNJJvUlpwGnnUHdXu8WjMCSNgXX9pIXDZIC/f22wjZFyY23yfSYOTCXTEOlpH8b b4R7VnZ6QfxGgJnqhHPWBE7FRaekI2MLfT6aYVL2sNvVPZoMo0wzjnxshwp2+8dK C0j2sNsoRdKPlGECYuh2eG40JQG2JKnZr2bMSwDI40GvDcQmyG7gD+jouOtei/vv KUDDfhNGnv0SdqmAk/UC4Cl1dDD9Y4Z0kAuAd7iTJhAcLszteeGqiDvdvtup5o7i HZcFmZX6EPBZXKrIcnzJ
=+Oe0
-----END PGP SIGNATURE-----

#7 lore raw

Josef Bacik wrote (ao):

Quoted 4 lines

The -dusage=<number> is a means to an end, so if that doesn't work try a larger number, up to 100. Really once you pass 50 and it's not working then it's time to just do a balance. The next thing is to use compression (too late for this option really) or add another disk.

btrfs filesystem defragment -vrc /home/

would apply compression to all files, no?

Sander

#8 lore raw
In reply to Josef Bacik
Quoted 22 lines · Josef Bacik
Quoted 21 lines · Marcus Sundman
Quoted 11 lines · Hugo Mills
Quoted 5 lines · Jim Salter

370GB of 410GB used isn't really "fine", it's over 90% usage.

That said, I'd be interested to know why btrfs fi show /dev/sda3 shows 412.54G used, but btrfs fi df /home shows 379G used...

This is an FAQ...

btrfs fi show tells you how much is allocated out of the available pool on each disk. btrfs fi df then shows how much of that allocated space (in each category) is used.

What is the difference between the "used 371.11GB" and the "used 412.54GB" displayed by "btrfs fi show"?

Quoted 6 lines

The problem here is also in the FAQ: the metadata is close to full -- typically something like 500-750 MiB of headroom is needed in metadata. The FS can't allocate more metadata because it's allocated everything already (total=used in btrfs fi show), so the solution is to do a filtered balance:

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

btrfs balance start -dusage=5 /mountpoint

Of course that was the first thing I tried, and it didn't help *at* *all*:

The -dusage=<number> is a means to an end, so if that doesn't work try a larger number, up to 100. Really once you pass 50 and it's not working then it's time to just do a balance. The next thing is to use compression (too late for this option really) or add another disk.

So it relocates some chunks. What will that do? Does it mean I can now use the remaining 45 GB? Or will it run out of "disk space" again after using a gig or two? If it's the allocated metadata space that is the problem then how can I pre-allocate more of it so it won't run out of it?

- Marcus

#9 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 34 lines · Marcus Sundman
Quoted 24 lines · Josef Bacik
Quoted 23 lines · Marcus Sundman
Quoted 4 lines · Hugo Mills
Quoted 3 lines · Jim Salter

370GB of 410GB used isn't really "fine", it's over 90% usage.

Quoted 8 lines
Quoted 3 lines

That said, I'd be interested to know why btrfs fi show /dev/sda3 shows 412.54G used, but btrfs fi df /home shows 379G used...

This is an FAQ...

btrfs fi show tells you how much is allocated out of the available pool on each disk. btrfs fi df then shows how much of that allocated space (in each category) is used.

What is the difference between the "used 371.11GB" and the "used 412.54GB" displayed by "btrfs fi show"?

Quoted 7 lines

The problem here is also in the FAQ: the metadata is close to full -- typically something like 500-750 MiB of headroom is needed in metadata. The FS can't allocate more metadata because it's allocated everything already (total=used in btrfs fi show), so the solution is to do a filtered balance:

btrfs balance start -dusage=5 /mountpoint

Quoted 8 lines
Quoted 3 lines

Of course that was the first thing I tried, and it didn't help *at* *all*:

The -dusage=<number> is a means to an end, so if that doesn't work try a larger number, up to 100. Really once you pass 50 and it's not working then it's time to just do a balance. The next thing is to use compression (too late for this option really) or add another disk.

Quoted 7 lines

So it relocates some chunks. What will that do? Does it mean I can now use the remaining 45 GB? Or will it run out of "disk space" again after using a gig or two? If it's the allocated metadata space that is the problem then how can I pre-allocate more of it so it won't run out of it?

It will allocate more as it sees fit, there is a metadata_ratio=N option which lets you force it to allocate a metadata chunk for every N data chunk allocations, but that shouldn't be needed in this case. What does btrfs fi df and btrfs show look like now? Thanks,

Josef
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTDpIMAAoJEANb+wAKly3BfKUQAK/WzvL/SENlUhruUoL7ADid tM6ivq2BZOwmlw+CzOIzjrwv9gwRe+UAfjKjGstueLoVY+lHNYaCC5OI94OOWDPo SyLJdJhcA3FYYBlyz7EC6gG4fNFyJg6egshoyMmWJuny5ivfnltdQhLLz2IQIHek Ud9ElN+SMvCeQmGZxdKg5yc2oIgBdc5xGfegtfuCqFkdhu+BZTbcXFsOD4Pjnsg0 Mtw8H5YBeXcFBV34I8F6l+O3AGjDl8jF/cFuCEbRTJQFkvpKhoHMw+O2AWykDQqc xw3H1YghGeY1fqN2geyYSYVGVOGxWeO2kju7Itom8Ph5AinMPMf8lpe97nChp2hr D3T1QwhkmMD9T1O02hvF9C8E46q2iyjOrPxPU8z3LsRTKaNXNzJ+u1P2ac7kIQSk x2stB9u0Qluut+5twzLQuefzoCNf/2RtAlL2cPXyq6ikLHBSNkebqbGBD2IpTsa7 5TsXNHWbIc0maDdXrJ0BYJ7obEaU/2nBCkSA3DaGBupTtC3vwSWAoAEw8/JtVeQr ARXSIPblXZqwrGyJyvtNmC8zjDGAD93H/xr0+oCOzHqPIr7NvTT9vZKfENmblsfm vx8wmgbSBzWp9W9YpUO5X0ZjLestPzOziIesCrMJ2yKBUEUtafiFdbT5D7e9dn8x 7Z2MZcYyk5H7QF65+IWt
=8iSO
-----END PGP SIGNATURE-----

#10 lore raw
In reply to Marcus Sundman
Quoted 27 lines · Marcus Sundman
Quoted 26 lines · Josef Bacik
Quoted 25 lines · Marcus Sundman
Quoted 11 lines · Hugo Mills
Quoted 5 lines · Jim Salter

370GB of 410GB used isn't really "fine", it's over 90% usage.

That said, I'd be interested to know why btrfs fi show /dev/sda3 shows 412.54G used, but btrfs fi df /home shows 379G used...

This is an FAQ...

btrfs fi show tells you how much is allocated out of the available pool on each disk. btrfs fi df then shows how much of that allocated space (in each category) is used.

What is the difference between the "used 371.11GB" and the "used 412.54GB" displayed by "btrfs fi show"?

Quoted 7 lines

The problem here is also in the FAQ: the metadata is close to full -- typically something like 500-750 MiB of headroom is needed in metadata. The FS can't allocate more metadata because it's allocated everything already (total=used in btrfs fi show), so the solution is to do a filtered balance:

btrfs balance start -dusage=5 /mountpoint

Of course that was the first thing I tried, and it didn't help *at* *all*:

Quoted 8 lines
Quoted 4 lines

The -dusage=<number> is a means to an end, so if that doesn't work try a larger number, up to 100. Really once you pass 50 and it's not working then it's time to just do a balance. The next thing is to use compression (too late for this option really) or add another disk.

So it relocates some chunks. What will that do? Does it mean I can now use the remaining 45 GB? Or will it run out of "disk space" again after using a gig or two?

What it's done is moved some of the data around. One effect of this
process is that when a balance operation balances a chunk, it deallocates that space. Therefore you should now see that the "used" value for the device in btrfs fi show is lower than the "total" value. Also, the "total" value for data in btrfs fi df should now be lower than it was before.

This means that the next time the FS needs some metadata space
(probably real soon now, because it was running out of it earlier), it now has uncommitted space to allocate to metadata.

Quoted 2 lines

If it's the allocated metadata space that is the problem then how can I pre-allocate more of it so it won't run out of it?

It's possible that when filling up the remaining 45 GiB of space
the metadata will need to expand again, and you will need to run a balance to do the same job again. Unless you have lots and lots of small files or small fragments (or lots more snapshots than you've been making to date), I'd say it's probably unlikely, though.

Hugo.

Signature · 4 lines
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
        --- Well, sir, the floor is yours.  But remember, the ---        
                              roof is ours!                              
#11 lore raw
In reply to Marcus Sundman
Quoted 6 lines · Marcus Sundman
Quoted 5 lines · Hugo Mills
Quoted 4 lines · Jim Salter

370GB of 410GB used isn't really "fine", it's over 90% usage.

That said, I'd be interested to know why btrfs fi show /dev/sda3 shows 412.54G used, but btrfs fi df /home shows 379G used...

Quoted 8 lines
Quoted 5 lines

This is an FAQ...

btrfs fi show tells you how much is allocated out of the available
pool on each disk. btrfs fi df then shows how much of that allocated space (in each category) is used.

What is the difference between the "used 371.11GB" and the "used 412.54GB" displayed by "btrfs fi show"?

The first and smaller value is (in this case) the sum of all the
"used" values in the output of btrfs fi df. The second is the total amount of raw disk space that has been allocated. (Yes, this is a bit of a mess -- there's been discussions recently about improving the output).

Quoted 8 lines
Quoted 7 lines

The problem here is also in the FAQ: the metadata is close to full
-- typically something like 500-750 MiB of headroom is needed in metadata. The FS can't allocate more metadata because it's allocated everything already (total=used in btrfs fi show), so the solution is to do a filtered balance:

btrfs balance start -dusage=5 /mountpoint

Quoted 7 lines

Of course that was the first thing I tried, and it didn't help *at* *all*:

Quoted 3 lines
# btrfs filesystem balance start -dusage=5 /home
Done, had to relocate 0 out of 415 chunks
#

... and it really didn't free anything.

OK, so crank up the number to 10 and try again. If that still moves
nothing, then increase again until it frees up something. With an FS at 90% full or so, particularly if it's seen heavy use, the chances are reasonable that all of the chunks are over 5% full, so putting the value up will eventually get to the point of moving at least one chunk, which should be all that's needed at this point.

Hugo.

Quoted 29 lines
Quoted 28 lines
Quoted 28 lines · Marcus Sundman
Quoted 27 lines

Hi

I get "No space left on device" and it is unclear why:

Quoted 7 lines
# df -h|grep sda3
/dev/sda3       413G  368G   45G  90% /home
# btrfs filesystem show /dev/sda3
Label: 'home'  uuid: 46279061-51f4-40c2-afd0-61d6faab7f60
   Total devices 1 FS bytes used 371.11GB
   devid    1 size 412.54GB used 412.54GB path /dev/sda3
Quoted 6 lines

Btrfs v0.20-rc1

# btrfs filesystem df /home
Data: total=410.52GB, used=369.61GB
System: total=4.00MB, used=64.00KB
Metadata: total=2.01GB, used=1.50GB
#

So, 'data' and 'metadata' seem to be fine(?), but 'system' is a bit low. Is that it? If so, can I do something about it? Or should I look somewhere else?

I really wish I could get a warning before running out of disk space, instead of everything breaking suddenly when there seems to be lots and lots of space left.

- Marcus

Signature · 4 lines
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
    --- Jazz is the sort of music where no-one plays anything the ---    
                             same way once.