This is just a hunch, but maybe the handling of spare files (such as
.vdi) is not ideal or not what we're used to with extN. Normally
skipped blocks do not count towards the disk full size, but given
btrfs' nature they may count as a reservation that would certainly
cause an early ENOSPC.
On Mon, Mar 09, 2009 at 07:08:16AM -0600, Yien Zheng wrote:
At this point I'm wondering if this is a anomaly or if it has anything
to do with using an SSD. It seems the pre-2.7.29-rc7 code had a hard
stop at 85%. But the recent patch doesn't seem to have solve the
issue for me. Is there
On Wed, 04 Mar 2009 14:48:43 -0600, Hugo Mills hugo-l...@carfax.org.uk wrote:
On Wed, Mar 04, 2009 at 01:50:53PM -0500, Josef Bacik wrote:
On Wed, Mar 04, 2009 at 06:06:19PM +, Hugo Mills wrote:
Last night, this event jammed up a good chunk of my server:
Mar 4 01:51:36 vlad
I just tried umounting the partition and got this:
[ 1395.028651] btrfs searching for 69632 bytes, num_bytes 69632, loop
2, allowed_alloc 1
[ 1395.028661] btrfs allocation failed flags 1, wanted 69632
[ 1395.028667] space_info has 81920 free, is full
[ 1395.028673] space_info total=10720313344,
Last night, this event jammed up a good chunk of my server:
Mar 4 01:51:36 vlad kernel: btrfs searching for 1716224 bytes, num_bytes
1716224, loop 2, allowed_alloc 1
Mar 4 01:51:36 vlad kernel: btrfs searching for 860160 bytes, num_bytes
860160, loop 2, allowed_alloc 1
[lots of this...]
On Wed, Mar 04, 2009 at 06:06:19PM +, Hugo Mills wrote:
Last night, this event jammed up a good chunk of my server:
Mar 4 01:51:36 vlad kernel: btrfs searching for 1716224 bytes, num_bytes
1716224, loop 2, allowed_alloc 1
Mar 4 01:51:36 vlad kernel: btrfs searching for 860160
On Wed, Mar 04, 2009 at 01:50:53PM -0500, Josef Bacik wrote:
On Wed, Mar 04, 2009 at 06:06:19PM +, Hugo Mills wrote:
Last night, this event jammed up a good chunk of my server:
Mar 4 01:51:36 vlad kernel: btrfs searching for 1716224 bytes, num_bytes
1716224, loop 2,
