Skip to contentSkip to conversation

Errors during defragmentation

DISCUSSION Andrej Podzimek 2 participants 3 messages Nov 29, 2010 Btrfs file system

lore
Share & tools
lore
#0 lore raw

Hello,

I decided to test the 'defragment' feature on my system (after a huge number of system updates and prelinking):

find /bin /sbin /lib /usr/lib /usr/bin /usr/sbin -type d -exec btrfs filesystem defragment '{}' '+'

I have already defragmented a couple of (very large) directories with no errors at all, so this was expected to work somehow. Surprisingly, this time there were thousands of messages like this:

ioctl failed on <directory name> ret -1 errno 28

Most of the reported directories had zero files/subdirectories. However, *most* of them were *not* empty...

What does this error message mean? Could someone shed more light on this, please? Should I get ready for a bad crash? ;-) (There seems to be no data loss so far. No new messages in dmesg, no unexpected system behavior.)

Andrej

#1 lore raw

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

Quoted 9 lines · Andrej Podzimek

Hello,

I decided to test the 'defragment' feature on my system (after a huge number of system updates and prelinking):

find /bin /sbin /lib /usr/lib /usr/bin /usr/sbin -type d -exec btrfs filesystem defragment '{}' '+'

I have already defragmented a couple of (very large) directories with no errors at all, so this was expected to work somehow. Surprisingly, this time there were thousands of messages like this:

ioctl failed on <directory name> ret -1 errno 28

errno 28 is ENOSPC

You've run out of disk space. (Or at least, btrfs thinks so).

Quoted 6 lines

Most of the reported directories had zero files/subdirectories. However, *most* of them were *not* empty...

What does this error message mean? Could someone shed more light on this, please? Should I get ready for a bad crash? ;-) (There seems to be no data loss so far. No new messages in dmesg, no unexpected system behavior.)

Hugo.

- --
=== 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
--- I believe that it's closely correlated with ---
the aeroswine coefficient.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFM9BoxIKyzvlFcI40RAv5SAJkB13ClPuTeRElrN1ARFhvDJ2C76gCghC/d zFczJesxQGbd2jC2ildNNI0=
=i+tI
-----END PGP SIGNATURE-----

#2 lore raw
Quoted 6 lines
Quoted 6 lines

Hello,

I decided to test the 'defragment' feature on my system (after a huge number of system updates and prelinking):

find /bin /sbin /lib /usr/lib /usr/bin /usr/sbin -type d -exec btrfs filesystem defragment '{}' '+'

Quoted 7 lines
Quoted 3 lines

I have already defragmented a couple of (very large) directories with no errors at all, so this was expected to work somehow. Surprisingly, this time there were thousands of messages like this:

ioctl failed on<directory name> ret -1 errno 28

errno 28 is ENOSPC

You've run out of disk space. (Or at least, btrfs thinks so).

Pleased to hear that this is not a fatal error. :-)

The filesystem still has quite a lot of free space. New files can be created. I have just tried to add about 10 GB of data, which worked fine. The output from 'df' indicates that only 71% of the partition (177 GB out of 250 GB) is used.

The "built-in" df shows similar numbers -- if I understand it well, there is plenty of free space left.

	# btrfs filesystem df /
	Data: total=175.01GB, used=169.57GB
	Metadata: total=6.51GB, used=3.64GB
	System: total=12.00MB, used=32.00KB
	# btrfs filesystem show octopus
	failed to read /dev/sdb
	failed to read /dev/sr0
	Label: 'octopus'  uuid: 8576b57b-b934-424e-9a8a-04abc780c963
	        Total devices 1 FS bytes used 173.21GB
	        devid    1 size 249.50GB used 188.04GB path /dev/dm-2

Btrfs Btrfs v0.19

Does defragmentation have any unexpected (and not yet documented) free space requirements? (Most of the files I was attempting to defragment were smaller than 10 MB, as the directory names suggest.)

Is there a workaround for this issue? Or should I just leave the defragmentation feature alone for the time being?

Andrej