On Mon, Sep 07, 2015 at 11:09:26AM +0100, fdman...@kernel.org wrote:
> From: Filipe Manana
>
> Regression test for an ENOSPC issue when attempting to write to a file in
> a filesystem without any data block groups allocated.
>
> The btrfs issue is fixed by the linux kernel patch titled
> "Btrfs:
From: Filipe Manana
Regression test for an ENOSPC issue when attempting to write to a file in
a filesystem without any data block groups allocated.
The btrfs issue is fixed by the linux kernel patch titled
"Btrfs: don't initialize a space info as full to prevent ENOSPC" and the
regression was in
On Sat, Apr 4, 2015 at 4:33 AM, Filipe David Manana wrote:
> On Sat, Apr 4, 2015 at 12:36 AM, Justin Maggard wrote:
>> Hi,
>>
>> We're hitting a consistently reproducible ENOSPC condition with a
>> simple test case:
>>
>> # truncate -s 1T btrfs.fs
>> # mkfs.btrfs btrfs.fs
>> # mount btrfs.fs /mnt
On Sat, Apr 4, 2015 at 12:36 AM, Justin Maggard wrote:
> Hi,
>
> We're hitting a consistently reproducible ENOSPC condition with a
> simple test case:
>
> # truncate -s 1T btrfs.fs
> # mkfs.btrfs btrfs.fs
> # mount btrfs.fs /mnt/
> # fallocate -l 1021G /mnt/fallocate
> # btrfs fi sync /mnt/
> # dd
Hi,
We're hitting a consistently reproducible ENOSPC condition with a
simple test case:
# truncate -s 1T btrfs.fs
# mkfs.btrfs btrfs.fs
# mount btrfs.fs /mnt/
# fallocate -l 1021G /mnt/fallocate
# btrfs fi sync /mnt/
# dd if=/dev/zero of=/mnt/dd bs=1G
# btrfs fi sync /mnt/
# rm /mnt/fallocate
# b