From: "David C. Partridge" <david.partridge@perdrix.co.uk>
To: "'Qu Wenruo'" <quwenruo.btrfs@gmx.com>, <linux-btrfs@vger.kernel.org>
Subject: RE: Problems with btrfs
Date: Sun, 29 Apr 2018 10:55:29 +0100 [thread overview]
Message-ID: <003101d3dfa0$35ba0060$a12e0120$@perdrix.co.uk> (raw)
In-Reply-To: <2471e5c7-fcb6-947e-359a-a59f634c02ca@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]
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: btrfs-dump-tree1.log --]
[-- Type: application/octet-stream, Size: 7006 bytes --]
btrfs: unknown token 'inpect'
usage: btrfs [--help] [--version] <group> [<group>...] <command> [<args>]
btrfs subvolume create [-i <qgroupid>] [<dest>/]<name>
Create a subvolume
btrfs subvolume delete [options] <subvolume> [<subvolume>...]
Delete subvolume(s)
btrfs subvolume list [options] [-G [+|-]value] [-C [+|-]value] [--sort=gen,ogen,rootid,path] <path>
List subvolumes (and snapshots)
btrfs subvolume snapshot [-r] [-i <qgroupid>] <source> <dest>|[<dest>/]<name>
Create a snapshot of the subvolume
btrfs subvolume get-default <path>
Get the default subvolume of a filesystem
btrfs subvolume set-default <subvolid> <path>
Set the default subvolume of a filesystem
btrfs subvolume find-new <path> <lastgen>
List the recently modified files in a filesystem
btrfs subvolume show <subvol-path>
Show more information of the subvolume
btrfs subvolume sync <path> [<subvol-id>...]
Wait until given subvolume(s) are completely removed from the filesystem.
btrfs filesystem df [options] <path>
Show space usage information for a mount point
btrfs filesystem du [options] <path> [<path>..]
Summarize disk usage of each file.
btrfs filesystem show [options] [<path>|<uuid>|<device>|label]
Show the structure of a filesystem
btrfs filesystem sync <path>
Force a sync on a filesystem
btrfs filesystem defragment [options] <file>|<dir> [<file>|<dir>...]
Defragment a file or a directory
btrfs filesystem resize [devid:][+/-]<newsize>[kKmMgGtTpPeE]|[devid:]max <path>
Resize a filesystem
btrfs filesystem label [<device>|<mount_point>] [<newlabel>]
Get or change the label of a filesystem
btrfs filesystem usage [options] <path> [<path>..]
Show detailed information about internal filesystem usage .
btrfs balance start [options] <path>
Balance chunks across the devices
btrfs balance pause <path>
Pause running balance
btrfs balance cancel <path>
Cancel running or paused balance
btrfs balance resume <path>
Resume interrupted balance
btrfs balance status [-v] <path>
Show status of running or paused balance
btrfs device add [options] <device> [<device>...] <path>
Add a device to a filesystem
btrfs device delete <device>|<devid> [<device>|<devid>...] <path> btrfs device remove <device>|<devid> [<device>|<devid>...] <path>
Remove a device from a filesystem
btrfs device scan [(-d|--all-devices)|<device> [<device>...]]
Scan devices for a btrfs filesystem
btrfs device ready <device>
Check device to see if it has all of its devices in cache for mounting
btrfs device stats [-z] <path>|<device>
Show current device IO stats.
btrfs device usage [options] <path> [<path>..]
Show detailed information about internal allocations in devices.
btrfs scrub start [-BdqrRf] [-c ioprio_class -n ioprio_classdata] <path>|<device>
Start a new scrub. If a scrub is already running, the new one fails.
btrfs scrub cancel <path>|<device>
Cancel a running scrub
btrfs scrub resume [-BdqrR] [-c ioprio_class -n ioprio_classdata] <path>|<device>
Resume previously canceled or interrupted scrub
btrfs scrub status [-dR] <path>|<device>
Show status of running or finished scrub
btrfs check [options] <device>
Check structural integrity of a filesystem (unmounted).
btrfs rescue chunk-recover [options] <device>
Recover the chunk tree by scanning the devices one by one.
btrfs rescue super-recover [options] <device>
Recover bad superblocks from good copies
btrfs rescue zero-log <device>
Clear the tree log. Usable if it's corrupted and prevents mount.
btrfs restore [options] <device> <path> | -l <device>
Try to restore files from a damaged filesystem (unmounted)
btrfs inspect-internal inode-resolve [-v] <inode> <path>
Get file system paths for the given inode
btrfs inspect-internal logical-resolve [-Pv] [-s bufsize] <logical> <path>
Get file system paths for the given logical address
btrfs inspect-internal subvolid-resolve <subvolid> <path>
Get file system paths for the given subvolume ID.
btrfs inspect-internal rootid <path>
Get tree ID of the containing subvolume of path.
btrfs inspect-internal min-dev-size [options] <path>
Get the minimum size the device can be shrunk to. The
btrfs inspect-internal dump-tree [options] device
Dump tree structures from a given device
btrfs inspect-internal dump-super [options] device [device...]
Dump superblock from a device in a textual form
btrfs inspect-internal tree-stats [options] <device>
Print various stats for trees
btrfs property get [-t <type>] <object> [<name>]
Gets a property from a btrfs object.
btrfs property set [-t <type>] <object> <name> <value>
Sets a property on a btrfs object.
btrfs property list [-t <type>] <object>
Lists available properties with their descriptions for the given object.
btrfs send [-ve] [-p <parent>] [-c <clone-src>] [-f <outfile>] <subvol> [<subvol>...]
Send the subvolume(s) to stdout.
btrfs receive [-ve] [-f <infile>] [--max-errors <N>] <mount>
Receive subvolumes from stdin.
btrfs quota enable <path>
Enable subvolume quota support for a filesystem.
btrfs quota disable <path>
Disable subvolume quota support for a filesystem.
btrfs quota rescan [-sw] <path>
Trash all qgroup numbers and scan the metadata again with the current config.
btrfs qgroup assign [options] <src> <dst> <path>
Assign SRC as the child qgroup of DST
btrfs qgroup remove <src> <dst> <path>
Remove a child qgroup SRC from DST.
btrfs qgroup create <qgroupid> <path>
Create a subvolume quota group.
btrfs qgroup destroy <qgroupid> <path>
Destroy a quota group.
btrfs qgroup show -pcreFf [--sort=qgroupid,rfer,excl,max_rfer,max_excl] <path>
Show subvolume quota groups.
btrfs qgroup limit [options] <size>|none [<qgroupid>] <path>
Set the limits a subvolume quota group.
btrfs replace start [-Bfr] <srcdev>|<devid> <targetdev> <mount_point>
Replace device of a btrfs filesystem.
btrfs replace status [-1] <mount_point>
Print status and progress information of a running device replace
btrfs replace cancel <mount_point>
Cancel a running device replace operation.
btrfs help [--full]
Display help information
btrfs version
Display btrfs-progs version
Use --help as an argument for information on a specific group or command.
next prev parent reply other threads:[~2018-04-29 9:55 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 [this message]
2018-04-29 10:00 ` Qu Wenruo
[not found] ` <003501d3dfa0$ce3f1b40$6abd51c0$@perdrix.co.uk>
2018-04-29 10:15 ` Qu Wenruo
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='003101d3dfa0$35ba0060$a12e0120$@perdrix.co.uk' \
--to=david.partridge@perdrix.co.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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