Hi Filipe,
I finally got to debug this deeper. As it turns out, this happens only
if both "nospace_cache" and "clear_cache" are specified. You need to
unmount and mount again to cause this. After mounting, due to
"clear_cache", all the block-groups are marked as BTRFS_DC_CLEAR, and
then cache_save_
On Mon, Nov 4, 2013 at 12:16 PM, Alex Lyakas
wrote:
> Hi Filipe,
> any luck with this patch?:)
Hey Alex,
I haven't digged further, but I remember I couldn't reproduce your
issue (with latest btrfs-next of that day) of getting the free space
inodes created even when mount option nospace_cache is
Hi Filipe,
any luck with this patch?:)
Alex.
On Wed, Oct 23, 2013 at 5:26 PM, Filipe David Manana wrote:
> On Wed, Oct 23, 2013 at 3:14 PM, Alex Lyakas
> wrote:
>> Hello,
>>
>> On Wed, Oct 23, 2013 at 4:35 PM, Filipe David Manana
>> wrote:
>>> On Wed, Oct 23, 2013 at 2:33 PM, Alex Lyakas
>>>
On Wed, Oct 23, 2013 at 3:14 PM, Alex Lyakas
wrote:
> Hello,
>
> On Wed, Oct 23, 2013 at 4:35 PM, Filipe David Manana
> wrote:
>> On Wed, Oct 23, 2013 at 2:33 PM, Alex Lyakas
>> wrote:
>>> Hi Filipe,
>>>
>>>
>>> On Tue, Aug 20, 2013 at 2:52 AM, Filipe David Borba Manana
>>> wrote:
Th
Hello,
On Wed, Oct 23, 2013 at 4:35 PM, Filipe David Manana wrote:
> On Wed, Oct 23, 2013 at 2:33 PM, Alex Lyakas
> wrote:
>> Hi Filipe,
>>
>>
>> On Tue, Aug 20, 2013 at 2:52 AM, Filipe David Borba Manana
>> wrote:
>>>
>>> This issue is simple to reproduce and observe if kmemleak is enabled.
>>
On Wed, Oct 23, 2013 at 2:33 PM, Alex Lyakas
wrote:
> Hi Filipe,
>
>
> On Tue, Aug 20, 2013 at 2:52 AM, Filipe David Borba Manana
> wrote:
>>
>> This issue is simple to reproduce and observe if kmemleak is enabled.
>> Two simple ways to reproduce it:
>>
>> ** 1
>>
>> $ mkfs.btrfs -f /dev/loop0
>>
Hi Filipe,
On Tue, Aug 20, 2013 at 2:52 AM, Filipe David Borba Manana
wrote:
>
> This issue is simple to reproduce and observe if kmemleak is enabled.
> Two simple ways to reproduce it:
>
> ** 1
>
> $ mkfs.btrfs -f /dev/loop0
> $ mount /dev/loop0 /mnt/btrfs
> $ btrfs balance start /mnt/btrfs
> $
This issue is simple to reproduce and observe if kmemleak is enabled.
Two simple ways to reproduce it:
** 1
$ mkfs.btrfs -f /dev/loop0
$ mount /dev/loop0 /mnt/btrfs
$ btrfs balance start /mnt/btrfs
$ umount /mnt/btrfs
** 2
$ mkfs.btrfs -f /dev/loop0
$ mount /dev/loop0 /mnt/btrfs
$ touch /mnt/bt
