space info full

space info full

[Martin Bürger]

Hello,
'space info full' was the only message I got from dmesg. df reports:

/dev/sdb1             33551720  28504548   5047172 =20
85% /mnt/btrfstest

df -i reports:
/dev/sdb1                  0       0       0    -  /mnt/btrfstest

Any (e.g., touch, rm) operation on that mounted filesystem lets the=20
CPU rise and the system hang...

I was filling up the partition with compilebench to the ration=20
mentioned above. During this process I tried to create a subvolume=20
with
	btrfsctl -s sub_vol /mnt/btrfstest
which did not, as opposed to the advices from the INSTALL file,=20
create anything within /mnt/btrfstest.

Regards,
--=20
Martin B=C3=BCrger
1024D/27C9019B@www.edu.uni-klu.ac.at/~mbuerger/key.asc
Key fingerprint =3D D10D 97EF 0C32 B337 5A12  0B6C 2D47 7575 27C9 019B
--
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

Re: space info full

[Yan Zheng]

Martin B=C3=BCrger wrote:
> Hello,
> 'space info full' was the only message I got from dmesg. df reports:
>=20
> /dev/sdb1             33551720  28504548   5047172 =20
> 85% /mnt/btrfstest

The output of df can be inaccurate. Although df shows the FS is 85% ful=
l,
It's possible the FS is completely full.

>=20
> df -i reports:
> /dev/sdb1                  0       0       0    -  /mnt/btrfstest
>=20
> Any (e.g., touch, rm) operation on that mounted filesystem lets the=20
> CPU rise and the system hang...

btrfs can't properly handle disk full condition currently. ENOSPC can
result in BUG()

>=20
> I was filling up the partition with compilebench to the ration=20
> mentioned above. During this process I tried to create a subvolume=20
> with
> 	btrfsctl -s sub_vol /mnt/btrfstest
> which did not, as opposed to the advices from the INSTALL file,=20
> create anything within /mnt/btrfstest.

Please try mount the FS with -o subvol=3D. option, you will see the new
subvol.

Regards
Yan Zheng
--
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

Re: space info full

[Josef Bacik]

On Sat, Oct 04, 2008 at 09:45:55AM +0200, Martin B=FCrger wrote:
> Hello,
> 'space info full' was the only message I got from dmesg. df reports:
>

space info full doesn't mean the disk is full, just means we've allocat=
ed all of
the block group chunks that the filesystem can hold, so you will get th=
at
message well before you actually run out of disk space.  As it stands n=
ow btrfs
has a short circuit when you hit ~15% free to go ahead an ENOSPC to avo=
id
hitting the many BUG()'s that are sitting around to handle ENOSPC.
=20
> /dev/sdb1             33551720  28504548   5047172 =20
> 85% /mnt/btrfstest
>=20
> df -i reports:
> /dev/sdb1                  0       0       0    -  /mnt/btrfstest
>=20
> Any (e.g., touch, rm) operation on that mounted filesystem lets the=20
> CPU rise and the system hang...
>

are you running the latest git trees of both btrfs-unstable and
btrfs-progs-unstable?  I'd expect BUG()'s or something like that, shoul=
dn't be
getting hangs.  Thanks,

Josef=20
--
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

Re: space info full

[Martin Bürger]

On Monday 06 October 2008, Josef Bacik wrote:
> are you running the latest git trees of both btrfs-unstable and
> btrfs-progs-unstable? =A0I'd expect BUG()'s or something like that,
> shouldn't be getting hangs. =A0Thanks,

Yes, I used both unstable versions from the git tree for the tests.=20
No further messages than the one I mentioned occurred. Furthermore=20
the system did hang at any operation on that particular file system=20
after (can not exactly tell when) the 'space info full' message had=20
turned up. Unfortunately I've not been able to reproduce this (yet),=20
hence this might have been an issue with the virtual machine=20
(VMWare) I using for the tests.

Regards,
--=20
Martin B=FCrger
1024D/27C9019B@www.edu.uni-klu.ac.at/~mbuerger/key.asc
Key fingerprint =3D D10D 97EF 0C32 B337 5A12  0B6C 2D47 7575 27C9 019B
--
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