no space left on device.
So I have ended up in a state where I can't delete files with rm.
the error I get is no space on device. however I'm not even close to empty. /dev/sdb1 38G 27G 9.5G 75%
there is about 800k files/dirs in this filesystem
extra strange is that I can in another directory create and delete files.
So I tried pretty much all I could google my way to but problem persisted. So I decided to do a backup and a format. But when the backup was done I tried one more time and now it was possible to delete the directory and all content?
using the 3.5 kernel in ubuntu 12.10. Is this a known issue ? is it fixed in later kernels?
fsck /btrfs scrub and kernel log. nothing indicate any problem of any kind.
Quoted 13 lines
So I have ended up in a state where I can't delete files with rm.
the error I get is no space on device. however I'm not even close to empty.
/dev/sdb138G 27G 9.5G 75%
there is about 800k files/dirs in this filesystemextra strange is that I can in another directory create and delete files.
So I tried pretty much all I could google my way to but problem persisted. So I decided to do a backup and a format. But when the backup was done I tried one more time and now it was possible to delete the directory and all content?
Quoted 5 lines
using the 3.5 kernel in ubuntu 12.10. Is this a known issue ? is it fixed in later kernels?
fsck /btrfs scrub and kernel log. nothing indicate any problem of any kind.
First let's see the output of:
btrfs fi df /mountpoint
You're probably way over allocated in metadata so a balance should help:
btrfs bal start -m /mountpoint
or omit the -m option to run a full balance.
Quoted 19 lines · Kyle Gates
Quoted 13 lines
So I have ended up in a state where I can't delete files with rm.
the error I get is no space on device. however I'm not even close to empty.
/dev/sdb138G 27G 9.5G 75%
there is about 800k files/dirs in this filesystemextra strange is that I can in another directory create and delete files.
So I tried pretty much all I could google my way to but problem persisted. So I decided to do a backup and a format. But when the backup was done I tried one more time and now it was possible to delete the directory and all content?
Quoted 5 lines
using the 3.5 kernel in ubuntu 12.10. Is this a known issue ? is it fixed in later kernels?
fsck /btrfs scrub and kernel log. nothing indicate any problem of any kind.
Quoted 6 lines
First let's see the output of:
btrfs fi df /mountpointYou're probably way over allocated in metadata so a balance should help:
btrfs bal start -m /mountpoint
or omit the -m option to run a full balance.
Or, better, -musage=5 (or 1), which will do even less work.
... but let's see the btrfs fi df output first. Could you also add the output of "btrfs fi show" (no parameters), please?
Hugo.
Signature · 3 lines
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- You're never alone with a rubber duck... --- Quoted 16 lines · Kyle Gates
Quoted 16 lines
So I have ended up in a state where I can't delete files with rm.
the error I get is no space on device. however I'm not even close to empty.
/dev/sdb138G 27G 9.5G 75%
there is about 800k files/dirs in this filesystemextra strange is that I can in another directory create and delete files.
So I tried pretty much all I could google my way to but problem persisted. So I decided to do a backup and a format. But when the backup was done I tried one more time and now it was possible to delete the directory and all content?
using the 3.5 kernel in ubuntu 12.10. Is this a known issue ? is it fixed in later kernels?
Quoted 8 lines
Quoted 2 lines
fsck /btrfs scrub and kernel log. nothing indicate any problem of any kind.
First let's see the output of:
btrfs fi df /mountpointYou're probably way over allocated in metadata so a balance should help:
btrfs bal start -m /mountpoint
or omit the -m option to run a full balance.
I had to use the disk for work so I could not be stuck in that situation and thus had to nuke the disk. maybe I can recreate the state I put back mostly the same data again minus some stuff I did not really need.
So under what circumstance can this actually happen ? why could I remove/add files in one directory and not another? its the same partition. And also the filesystem was just a few days old and no snapshots or anything, well I do use lzo compression but other than that default values was used to create it.