Hi,
is it safe (has it an effect?) to use the 'clear_cache' option in a
'mount -o remount'? I recognize messages in my kernel log regarding
'BTRFS info (device dm-7): The free space cache file (31215079915520)
is invalid. skip it'. I would like to fix it and would do it (in best
case) without reboo
On Sun, Aug 6, 2017 at 8:49 AM, Cloud Admin wrote:
> Hi,
> is it safe (has it an effect?) to use the 'clear_cache' option in a
> 'mount -o remount'? I recognize messages in my kernel log regarding
> 'BTRFS info (device dm-7): The free space cache file (31215079915520)
> is invalid. skip it'. I wou
On Thu, Aug 3, 2017 at 11:51 PM, Shyam Prasad N wrote:
> Hi all,
>
> We're running a couple of experiments on our servers with btrfs
> (kernel version 4.4).
> And we're running some abrupt power-off tests for a couple of scenarios:
>
> 1. We have a filesystem on top of two different btrfs filesyst
On Thu, Aug 3, 2017 at 11:51 PM, Shyam Prasad N wrote:
> Hi all,
>
> We're running a couple of experiments on our servers with btrfs
> (kernel version 4.4).
> And we're running some abrupt power-off tests for a couple of scenarios:
>
> 1. We have a filesystem on top of two different btrfs filesyst
On Fri, Aug 4, 2017 at 6:09 AM, Shyam Prasad N wrote:
> Thanks guys. I've enabled that option now. Let's see how it goes.
> One general question regarding the stability of btrfs in kernel
> version 4.4. Is this okay for power off test cases? Or are there many
> important fixes in newer kernels?
On Sun, Aug 06, 2017 at 08:15:45PM -0600, Chris Murphy wrote:
> On Thu, Aug 3, 2017 at 11:51 PM, Shyam Prasad N
> wrote:
> > We're running a couple of experiments on our servers with btrfs
> > (kernel version 4.4).
> > And we're running some abrupt power-off tests for a couple of scenarios:
> >
>
Now i do a btrfs-find-root, but it runs now since 5 day without a result.
How long should i wait? Or is it already to late to hope?
mainframe:~ # btrfs-find-root.static /dev/sdb1
parent transid verify failed on 29376512 wanted 1327723 found 1489835
parent transid verify failed on 29376512 wanted 1
Hi Chris,
Thanks for the detailed reply. :)
Read my answers inline:
On Mon, Aug 7, 2017 at 7:45 AM, Chris Murphy wrote:
>
> This is astronomically more complicated than the already complicated
> scenario with one file system on a single normal partition of a well
> behaved (non-lying) single dri
