On 9/24/19 2:22 PM, Josef Bacik wrote:
>
> Just popping in to let you know I've been seeing this internally as well, I
> plan
> to dig into it after we've run down the panic we're chasing currently.
> Thanks,
No problem. The only issue it seems to be causing is balance to fail.
Pete
On Fri, Sep 20, 2019 at 03:29:32PM +0100, Pete wrote:
> I have a btrfs that is on top of an lvm logical volume on top of dm-crypt on
> a single nvme drive (Samsung 870 Pro 512GB).
>
> I added a second logical volume to give more space to get rid of ENOSPC
> errors during balance, but to no avail.
On 9/24/19 12:10 AM, Chris Murphy wrote:
> Since I've reproduced it with all new progs and kernel I don't think
> you need to add anything there.
>
Thanks, appreciated.
On Mon, Sep 23, 2019 at 5:10 PM Chris Murphy wrote:
>
> On Mon, Sep 23, 2019 at 4:11 PM Pete wrote:
> >
> > On 9/23/19 10:52 PM, Chris Murphy wrote:
> > > What features do you have set?
> > >
> > > # btrfs insp dump-s /dev/
> > >
> >
> > root@phoenix:/var/lib/lxc# btrfs insp dump-s /dev/nvme0_vg/
On Mon, Sep 23, 2019 at 4:11 PM Pete wrote:
>
> On 9/23/19 10:52 PM, Chris Murphy wrote:
> > What features do you have set?
> >
> > # btrfs insp dump-s /dev/
> >
>
> root@phoenix:/var/lib/lxc# btrfs insp dump-s /dev/nvme0_vg/lxc
...
> sectorsize 4096
> nodesize16384
..
On 9/23/19 10:52 PM, Chris Murphy wrote:
> What features do you have set?
>
> # btrfs insp dump-s /dev/
>
root@phoenix:/var/lib/lxc# btrfs insp dump-s /dev/nvme0_vg/lxc
superblock: bytenr=65536, device=/dev/nvme0_vg/lxc
-
csum_type
What features do you have set?
# btrfs insp dump-s /dev/
On Mon, Sep 23, 2019 at 3:34 PM Peter Chant wrote:
>
> On 9/23/19 7:55 PM, Pete wrote:
>
> > I'm not sure the balance is resolving anything. The filesystem has not
> > gone read only. I'll try an unfiltered balance now to see how that goes.
> >
>
> OK, result of unfiltered balance:
>
> root@phoe
On 9/23/19 7:55 PM, Pete wrote:
> I'm not sure the balance is resolving anything. The filesystem has not
> gone read only. I'll try an unfiltered balance now to see how that goes.
>
OK, result of unfiltered balance:
root@phoenix:/var/lib/lxc# btrfs bal start /var/lib/lxc
WARNING:
Ful
On 9/22/19 10:25 PM, Chris Murphy wrote:
>> OK, I'm building 5.2.17 now. Keen to avoid the corruption errors I was
>> hit by a few weeks back... May take a time as I'm in the middle of a
>> slow backup.
>
> Did you see corruption on this same file system? The 5.2 corruption
> bug has been fixed
On Sun, Sep 22, 2019 at 1:07 PM Pete wrote:
>
> On 9/22/19 6:47 PM, Chris Murphy wrote:
>
> >> Unfortunately I don't seem to have any more info in dmesg of the enospc
> >> errors:
> >
> > You need to mount with enospc_debug to get more information, it might
> > be useful for a developer. This -28
On 9/22/19 6:47 PM, Chris Murphy wrote:
>> Unfortunately I don't seem to have any more info in dmesg of the enospc
>> errors:
>
> You need to mount with enospc_debug to get more information, it might
> be useful for a developer. This -28 error is one that has mostly gone
> away, I don't know if t
On Fri, Sep 20, 2019 at 8:31 AM Pete wrote:
>
> I have a btrfs that is on top of an lvm logical volume on top of
> dm-crypt on a single nvme drive (Samsung 870 Pro 512GB).
>
> I added a second logical volume to give more space to get rid of ENOSPC
> errors during balance, but to no avail. This wa
I have a btrfs that is on top of an lvm logical volume on top of
dm-crypt on a single nvme drive (Samsung 870 Pro 512GB).
I added a second logical volume to give more space to get rid of ENOSPC
errors during balance, but to no avail. This was after I started
getting enospc during balance. Wi
14 matches
Mail list logo
