From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "David C. Partridge" <david.partridge@perdrix.co.uk>,
linux-btrfs@vger.kernel.org
Subject: Re: Problems with btrfs
Date: Sun, 29 Apr 2018 18:15:07 +0800 [thread overview]
Message-ID: <544df9e0-e7b3-d93e-f385-d58049be121a@gmx.com> (raw)
In-Reply-To: <003501d3dfa0$ce3f1b40$6abd51c0$@perdrix.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 2495 bytes --]
On 2018年04月29日 17:59, David C. Partridge wrote:
> Here's the correct output - I mistyped inspect so I got the help output instead of the dump-tree!!! <BLUSH>
>
> David
The archive is corrupted.
Would you mind to upload it google drive/dropbox?
Thanks,
Qu
>
> -----Original Message-----
> From: David C. Partridge [mailto:david.partridge@perdrix.co.uk]
> Sent: 29 April 2018 10:55
> To: 'Qu Wenruo'; 'linux-btrfs@vger.kernel.org'
> Subject: RE: Problems with btrfs
>
> 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.btrfs@gmx.com]
> Sent: 29 April 2018 10:36
> To: David C. Partridge; linux-btrfs@vger.kernel.org
> Subject: Re: Problems with btrfs
>
>
>
> On 2018年04月29日 17:20, David C. Partridge wrote:
>> Here is the result of btrfs check after applying the patch
>
> Doesn't work as expected.
>
> Did you apply the patched tree block with "seek="?
>
> If so, please dump extent tree again to verify if the modification is done correct.
>
> # btrfs inspect dump-tree -t extent <device>
>
> Thanks,
> Qu
>
>>
>> Dave
>> -----Original Message-----
>> From: Qu Wenruo [mailto:quwenruo.btrfs@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 by the following command (copy1 and copy2 are the same).
>>
>> # dd if=copy1.img of=<device> bs=1 count=16K seek=25942081536 # dd
>> if=copy1.img of=<device> bs=1 count=16K seek=26478952448
>>
>> And after that, try btrfs check to see if it reports new error.
>>
>> Thanks,
>> Qu
>>
>> On 2018年04月29日 16:24, David C. Partridge wrote:
>>> Attached as requested
>>>
>>> -----Original Message-----
>>> From: linux-btrfs-owner@vger.kernel.org
>>> [mailto:linux-btrfs-owner@vger.kernel.org] On Behalf Of Qu Wenruo
>>> Sent: 29 April 2018 03:08
>>> To: David C. Partridge; linux-btrfs@vger.kernel.org
>>> Subject: Re: Problems with btrfs
>>>
>>>
>>>
>>> On 2018年04月29日 09:55, David C. Partridge wrote:
>>>> Not a problem
>>>>
>>>> See attached
>>>
>>> The final binary dump:
>>>
>>> # dd if=<device> of=/tmp/copy1.img bs=1 count=16K skip=25942081536 #
>>> dd if=<device> of=/tmp/copy2.img bs=1 count=16K skip=26478952448
>>>
>>> Thanks,
>>> Qu
>>>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-04-29 10:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 18:38 Problems with btrfs David C. Partridge
2018-04-28 0:20 ` Qu Wenruo
2018-04-28 3:09 ` Chris Murphy
[not found] ` <003801d3def2$d90965c0$8b1c3140$@perdrix.co.uk>
[not found] ` <a5c24cee-ad20-f317-28e8-40e88039db45@gmx.com>
[not found] ` <004d01d3def6$4000ed40$c002c7c0$@perdrix.co.uk>
[not found] ` <60674123-6fe2-2cfe-e7a8-25d62e023c53@gmx.com>
2018-04-28 14:06 ` David C. Partridge
2018-04-28 14:23 ` Qu Wenruo
2018-04-28 16:02 ` David C. Partridge
2018-04-29 1:35 ` Qu Wenruo
[not found] ` <002f01d3df5d$25dd0270$71970750$@perdrix.co.uk>
2018-04-29 2:07 ` Qu Wenruo
[not found] ` <002a01d3df93$74b7b760$5e272620$@perdrix.co.uk>
[not found] ` <126b8a98-384e-af68-8a36-ad702f07fad2@gmx.com>
2018-04-29 9:20 ` David C. Partridge
2018-04-29 9:36 ` Qu Wenruo
2018-04-29 9:55 ` David C. Partridge
2018-04-29 10:00 ` Qu Wenruo
[not found] ` <003501d3dfa0$ce3f1b40$6abd51c0$@perdrix.co.uk>
2018-04-29 10:15 ` Qu Wenruo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=544df9e0-e7b3-d93e-f385-d58049be121a@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=david.partridge@perdrix.co.uk \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox