Yes I did use seek=
I attach the new dump-tree - it seems very short compared to the last one you
requested ???
Dave
-Original Message-
From: Qu Wenruo [mailto:quwenruo.bt...@gmx.com]
Sent: 29 April 2018 10:36
To: David C. Partridge; linux-btrfs@vger.kernel.org
Subject: Re: Problems
Here is the result of btrfs check after applying the patch
Dave
-Original Message-
From: Qu Wenruo [mailto:quwenruo.bt...@gmx.com]
Sent: 29 April 2018 09:36
To: David C. Partridge
Subject: Re: Problems with btrfs
Here is the patched binary tree block.
You could apply them
Here are the dumps you requested.
-Original Message-
From: Qu Wenruo [mailto:quwenruo.bt...@gmx.com]
Sent: 28 April 2018 15:23
To: David C. Partridge; linux-btrfs@vger.kernel.org
Subject: Re: Problems with btrfs
On 2018年04月28日 22:06, David C. Partridge wrote:
> Here's the log
Here's the log you asked for ...
David
-Original Message-
From: Qu Wenruo [mailto:quwenruo.bt...@gmx.com]
Sent: 28 April 2018 14:54
To: David C. Partridge
Subject: Re: Problems with btrfs
On 2018年04月28日 21:38, David C. Partridge wrote:
> Oh! doing a private build from source a
To what level of btrfs-progs do you recommend I should upgrade once my
corrupt FS is fixed? What is the kernel pre-req for that?
Would prefer not to build from source ... currently running Ubuntu 16.04LTS
Thanks
David
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
I'm running Ubuntu 16.04. I rebooted my server today as it wasn't
responding.
When I rebooted the root FS was read only.
I booted a live Ubuntu CD and checked the drive with the results shown in
attachment btrfs-check.log.
The error was still there after completing the btrfs check --repair :(
