Hi,
the patch unfortunately did not work, because I didn't know for which
version/tree was made, since it does not apply for 4.14. or 4.15. But
since I got your hint with the possibility of the old age of my btrfs
volume, I simply tried an old ubuntu live disk, and it mounted the
volume :-) Then I
On 2017年12月11日 05:16, Benjamin Beichler wrote:
> The patch let the chunk-recover be successful. But I'm no lucky man,
> the recovered chunk tree does not work or other metadata is also
> broken.
>
> Mounting the system is not successful (dmesg):
> BTRFS critical (device dm-0): corrupt node, inva
On 2017年12月11日 05:16, Benjamin Beichler wrote:
> The patch let the chunk-recover be successful. But I'm no lucky man,
> the recovered chunk tree does not work or other metadata is also
> broken.
>
> Mounting the system is not successful (dmesg):
> BTRFS critical (device dm-0): corrupt node, inva
The patch let the chunk-recover be successful. But I'm no lucky man,
the recovered chunk tree does not work or other metadata is also
broken.
Mounting the system is not successful (dmesg):
BTRFS critical (device dm-0): corrupt node, invalid item slot:
block=16384, root=1, slot=0
BTRFS error (devic
On 2017年12月10日 08:29, Qu Wenruo wrote:
>
>
> On 2017年12月10日 07:12, Benjamin Beichler wrote:
>> Hi Qu,
>>
>> 2017-12-07 12:09 GMT+00:00 Qu Wenruo :
>>>
>>> Since the btrfs chunk recovery doesn't work and my dirty quick hack
>>> doesn't work either, I don't expect much to recovery.
>>>
>>> Unless
On 2017年12月10日 07:12, Benjamin Beichler wrote:
> Hi Qu,
>
> 2017-12-07 12:09 GMT+00:00 Qu Wenruo :
>>
>> Since the btrfs chunk recovery doesn't work and my dirty quick hack
>> doesn't work either, I don't expect much to recovery.
>>
>> Unless we have more detailed info about the how and why the
Hi Qu,
2017-12-07 12:09 GMT+00:00 Qu Wenruo :
>
> Since the btrfs chunk recovery doesn't work and my dirty quick hack
> doesn't work either, I don't expect much to recovery.
>
> Unless we have more detailed info about the how and why the BUG_ON() of
> chunk recovery is triggered.
>
> That's to say
On 2017年12月06日 14:08, Chris Murphy wrote:
> On Tue, Dec 5, 2017 at 12:22 PM, Benjamin Beichler
> wrote:
>> Hi,
>>
>> I have a setup as following: (1,7TB drive + 128GB SSD in Bcache) <==>
>> luks device <==> btrfs FS
>> I have been running Arch linux with newest stable kernel 4.14.
>
> There is
On Tue, Dec 5, 2017 at 12:22 PM, Benjamin Beichler
wrote:
> Hi,
>
> I have a setup as following: (1,7TB drive + 128GB SSD in Bcache) <==>
> luks device <==> btrfs FS
> I have been running Arch linux with newest stable kernel 4.14.
There is a known bug in 4.14 that affects all bcache backed file
On 2017年12月06日 03:22, Benjamin Beichler wrote:
> Hi,
>
> I have a setup as following: (1,7TB drive + 128GB SSD in Bcache) <==>
> luks device <==> btrfs FS
> I have been running Arch linux with newest stable kernel 4.14.
>
> After a reboot last week my btrfs volume becomes unmountable, because
10 matches
Mail list logo