Hi,
I''m running archlinux, kernel 2.6.33.2, btrfs-progs 0.19.
I was copying a folder (cca 2GB) to a btrfs partition(8GB free) and got a
''disk full'' error message. Had to kill the process and remove
the files
otherwise apps report full disk.
I can always reproduce this by creating some big files on the partition.
Since then, btrfsck reports errors, is there a way to fix them?
Thank you, Mark
// here follows contents of files attached for your comfort
Here are some clues:
*output of df -h:
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 20G 13G 6.0G 68% /
udev 10M 248K 9.8M 3% /dev
none 1.0G 0 1.0G 0% /dev/shm
/dev/mapper/homeDevice
21G 13G 8.0G 62% /home
tmpfs 3.0G 29M 3.0G 1% /tmp
/dev/sda8 3.4G 2.3G 976M 71% /var
/dev/sda2 145M 20M 118M 15% /boot
/dev/mapper/storeDevice
40G 38G 2.0G 96% /mnt/store
/dev/sda10 18G 9.1G 7.4G 56% /mnt/recovery
/dev/sda12 9.8G 9.6G 206M 98% /media/disk
/dev/sda1 30G 22G 7.5G 75% /mnt/winxp
* I''ve heard df has issues with btrfs, but du -sh /mountpoint reports
approx
same size used
*btrfsck /dev/mapper/homeDevice - is there a way to fix these errors??
I''m
worried to take snapshots or defragment not to make it worse.
root 5 inode 552424 errors 2
root 5 inode 552425 errors 2
root 5 inode 552426 errors 2
root 5 inode 552427 errors 2
root 5 inode 552429 errors 2
root 5 inode 552431 errors 2
root 5 inode 552515 errors 2
found 13520416768 bytes used err is 1
total csum bytes: 12991604
total tree bytes: 217014272
total fs tree bytes: 182243328
btree space waste bytes: 63087601
file data blocks allocated: 50432675840
referenced 12764286976
Btrfs Btrfs v0.19
*dmesg /snip/
no space left, need 32768, 0 delalloc bytes, 15466033152 bytes_used, 80084992
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 15546122240 total
no space left, need 4096, 0 delalloc bytes, 15466033152 bytes_used, 80084992
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 4096 may use 15546122240
total
no space left, need 32768, 0 delalloc bytes, 15470936064 bytes_used, 75182080
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 4096 may use 15546122240
total
no space left, need 40960, 0 delalloc bytes, 15470936064 bytes_used, 75182080
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 4096 may use 15546122240
total
no space left, need 12288, 0 delalloc bytes, 15476994048 bytes_used, 69124096
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 4096 may use 15546122240
total
no space left, need 4096, 4096 delalloc bytes, 15515852800 bytes_used,
30105600 bytes_reserved, 159744 bytes_pinned, 0 bytes_readonly, 0 may use
15546122240 total
no space left, need 4096, 204800 delalloc bytes, 15545917440 bytes_used, 0
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 15546122240 total
no space left, need 8192, 200704 delalloc bytes, 15545917440 bytes_used, 0
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 15546122240 total
no space left, need 32768, 200704 delalloc bytes, 15545917440 bytes_used, 0
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 15546122240 total
no space left, need 32768, 200704 delalloc bytes, 15545917440 bytes_used, 0
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 15546122240 total
no space left, need 8192, 200704 delalloc bytes, 15545917440 bytes_used, 0
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 15546122240 total
no space left, need 8192, 204800 delalloc bytes, 15545917440 bytes_used, 0
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 15546122240 total
no space left, need 4096, 204800 delalloc bytes, 15545917440 bytes_used, 0
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 15546122240 total
no space left, need 4096, 204800 delalloc bytes, 15545917440 bytes_used, 0
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 15546122240 total
no space left, need 8192, 204800 delalloc bytes, 15545917440 bytes_used, 0
bytes_reserved, 0 bytes_pinned, 0 bytes_readonly, 0 may use 15546122240 total
* btrfs-show
Label: home uuid: 5682534d-9365-4e78-a37b-30b51fff5e49
Total devices 1 FS bytes used 12.59GB
devid 1 size 20.50GB used 20.50GB path /dev/dm-2
Label: store uuid: c2bbe121-e7f2-48f4-9fb1-77252304ce4c
Total devices 1 FS bytes used 37.14GB
devid 1 size 39.06GB used 39.04GB path /dev/dm-3
Btrfs Btrfs v0.19
* btrfs-debug-tree
it''s a 115MB file, i am uploading it and will post a link asap.
--
Marek Otahal :o)
Marek Otahal
2010-Apr-07 15:43 UTC
Re: btrfs error: ''disk full'' although 8 of 21 GB free
here is the output of btrfs-debug-tree /dev/mapper/homeDevice cca 115MB http://leteckaposta.cz/file/156803395.1/02a22dde7c98235100610b24f28db4b064e7be4c or http://leteckaposta.cz/156803395 Regards, Marek -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Apr 07, 2010 at 04:59:02PM +0200, Marek Otahal wrote:> Hi, > I''m running archlinux, kernel 2.6.33.2, btrfs-progs 0.19. > I was copying a folder (cca 2GB) to a btrfs partition(8GB free) and got a > ''disk full'' error message. Had to kill the process and remove the files > otherwise apps report full disk. > I can always reproduce this by creating some big files on the partition. > Since then, btrfsck reports errors, is there a way to fix them? > Thank you, Mark > > // here follows contents of files attached for your comfort > > Here are some clues: > > *output of df -h: > > Filesystem Size Used Avail Use% Mounted on > /dev/sda5 20G 13G 6.0G 68% / > udev 10M 248K 9.8M 3% /dev > none 1.0G 0 1.0G 0% /dev/shm > /dev/mapper/homeDevice > 21G 13G 8.0G 62% /home > tmpfs 3.0G 29M 3.0G 1% /tmp > /dev/sda8 3.4G 2.3G 976M 71% /var > /dev/sda2 145M 20M 118M 15% /boot > /dev/mapper/storeDevice > 40G 38G 2.0G 96% /mnt/store > /dev/sda10 18G 9.1G 7.4G 56% /mnt/recovery > /dev/sda12 9.8G 9.6G 206M 98% /media/disk > /dev/sda1 30G 22G 7.5G 75% /mnt/winxp > > * I''ve heard df has issues with btrfs, but du -sh /mountpoint reports approx > same size used > > *btrfsck /dev/mapper/homeDevice - is there a way to fix these errors?? I''m > worried to take snapshots or defragment not to make it worse. >Some work has been done in this area recently. Can you run with the latest btrfs-unstable tree? Df will tell you something that is more along the lines with what you are expecting, and you can use the new btrfs-progs-unstable tree and run a btrfs filesystem df /mount/point and it will spit out specific space info that will be helpfull. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Andrew Carlson
2010-Apr-07 17:38 UTC
Re: btrfs error: ''disk full'' although 8 of 21 GB free
I can tell you from experience that the later unstable git pull works much better in this regard. I have a 299GB filesystem compressed to 1.2TB full with 507M free. And it handles the ENOSPC condition like it should. On Wed, Apr 7, 2010 at 10:48 AM, Josef Bacik <josef@redhat.com> wrote:> On Wed, Apr 07, 2010 at 04:59:02PM +0200, Marek Otahal wrote: >> Hi, >> I''m running archlinux, kernel 2.6.33.2, btrfs-progs 0.19. >> I was copying a folder (cca 2GB) to a btrfs partition(8GB free) and got a >> ''disk full'' error message. Had to kill the process and remove the files >> otherwise apps report full disk. >> I can always reproduce this by creating some big files on the partition. >> Since then, btrfsck reports errors, is there a way to fix them? >> Thank you, Mark >> >> // here follows contents of files attached for your comfort >> >> Here are some clues: >> >> *output of df -h: >> >> Filesystem Size Used Avail Use% Mounted on >> /dev/sda5 20G 13G 6.0G 68% / >> udev 10M 248K 9.8M 3% /dev >> none 1.0G 0 1.0G 0% /dev/shm >> /dev/mapper/homeDevice >> 21G 13G 8.0G 62% /home >> tmpfs 3.0G 29M 3.0G 1% /tmp >> /dev/sda8 3.4G 2.3G 976M 71% /var >> /dev/sda2 145M 20M 118M 15% /boot >> /dev/mapper/storeDevice >> 40G 38G 2.0G 96% /mnt/store >> /dev/sda10 18G 9.1G 7.4G 56% /mnt/recovery >> /dev/sda12 9.8G 9.6G 206M 98% /media/disk >> /dev/sda1 30G 22G 7.5G 75% /mnt/winxp >> >> * I''ve heard df has issues with btrfs, but du -sh /mountpoint reports approx >> same size used >> >> *btrfsck /dev/mapper/homeDevice - is there a way to fix these errors?? I''m >> worried to take snapshots or defragment not to make it worse. >> > > Some work has been done in this area recently. Can you run with the latest > btrfs-unstable tree? Df will tell you something that is more along the lines > with what you are expecting, and you can use the new btrfs-progs-unstable tree > and run a > > btrfs filesystem df /mount/point > > and it will spit out specific space info that will be helpfull. Thanks, > > Josef > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >-- Andy Carlson --------------------------------------------------------------------------- Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License: $8.95/month, The feeling of seeing the red box with the item you want in it:Priceless. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html