From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Su Yue <suy.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 02/13] btrfs-progs: lowmem: move nbytes check before isize check
Date: Tue, 23 Oct 2018 18:07:42 +0800 [thread overview]
Message-ID: <4e76d260-0496-3bfc-f9b8-3b6ab68bd25b@gmx.com> (raw)
In-Reply-To: <20181023094147.7906-3-suy.fnst@cn.fujitsu.com>
On 2018/10/23 下午5:41, Su Yue wrote:
> For files, lowmem repair will try to check nbytes and isize,
> but isize check depends nbytes.
>
> Once bytes has been repaired, then isize should be checked and
> repaired.
> So move nbytes check before isize check. Also set nbytes to
> extent_size once repaired successfully.
>
> Signed-off-by: Su Yue <suy.fnst@cn.fujitsu.com>
Overall looks good.
Just a small nitpick.
> ---
> check/mode-lowmem.c | 29 ++++++++++++++++-------------
> 1 file changed, 16 insertions(+), 13 deletions(-)
>
> diff --git a/check/mode-lowmem.c b/check/mode-lowmem.c
> index c8e4f13d816f..76e7be81ceb1 100644
> --- a/check/mode-lowmem.c
> +++ b/check/mode-lowmem.c
> @@ -2125,7 +2125,7 @@ out:
> error("failed to set nbytes in inode %llu root %llu",
> ino, root->root_key.objectid);
> else
> - printf("Set nbytes in inode item %llu root %llu\n to %llu", ino,
> + printf("Set nbytes in inode item %llu root %llu to %llu\n", ino,
It's better to fix it in another patch.
Thanks,
Qu
> root->root_key.objectid, nbytes);
>
> /* research path */
> @@ -2543,28 +2543,31 @@ out:
> }
> }
>
> - if (!nbytes && !no_holes && extent_end < isize) {
> - if (repair)
> - ret = punch_extent_hole(root, path, inode_id,
> - extent_end, isize - extent_end);
> + if (nbytes != extent_size) {
> + if (repair) {
> + ret = repair_inode_nbytes_lowmem(root, path,
> + inode_id, extent_size);
> + if (!ret)
> + nbytes = extent_size;
> + }
> if (!repair || ret) {
> err |= NBYTES_ERROR;
> error(
> - "root %llu INODE[%llu] size %llu should have a file extent hole",
> - root->objectid, inode_id, isize);
> + "root %llu INODE[%llu] nbytes %llu not equal to extent_size %llu",
> + root->objectid, inode_id, nbytes,
> + extent_size);
> }
> }
>
> - if (nbytes != extent_size) {
> + if (!nbytes && !no_holes && extent_end < isize) {
> if (repair)
> - ret = repair_inode_nbytes_lowmem(root, path,
> - inode_id, extent_size);
> + ret = punch_extent_hole(root, path, inode_id,
> + extent_end, isize - extent_end);
> if (!repair || ret) {
> err |= NBYTES_ERROR;
> error(
> - "root %llu INODE[%llu] nbytes %llu not equal to extent_size %llu",
> - root->objectid, inode_id, nbytes,
> - extent_size);
> + "root %llu INODE[%llu] size %llu should have a file extent hole",
> + root->objectid, inode_id, isize);
> }
> }
> }
>
next prev parent reply other threads:[~2018-10-23 10:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 9:41 [PATCH 00/13] btrfs-progs: fixes of file extent in original and lowmem check Su Yue
2018-10-23 9:41 ` [PATCH 01/13] btrfs-progs: lowmem: add argument path to punch_extent_hole() Su Yue
2018-10-23 10:04 ` Qu Wenruo
2018-10-24 1:18 ` Su Yue
2018-12-02 14:34 ` [PATCH v2 " damenly.su
2018-10-23 9:41 ` [PATCH 02/13] btrfs-progs: lowmem: move nbytes check before isize check Su Yue
2018-10-23 10:07 ` Qu Wenruo [this message]
2018-12-02 14:38 ` [PATCH v2 " damenly.su
2018-10-23 9:41 ` [PATCH 03/13] btrfs-progs: lowmem: fix false alert if extent item has been repaired Su Yue
2018-10-23 10:30 ` Qu Wenruo
2018-10-24 1:27 ` Su Yue
2018-10-24 1:24 ` Qu Wenruo
2018-12-02 14:45 ` [PATCH v2 " damenly.su
2018-10-23 9:41 ` [PATCH 04/13] btrfs-progs: lowmem: fix false alert about the existence of gaps in the check_file_extent Su Yue
2018-10-24 0:13 ` Qu Wenruo
2018-10-23 9:41 ` [PATCH 05/13] btrfs-progs: lowmem: check unaligned disk_bytenr for extent_data Su Yue
2018-10-24 0:13 ` Qu Wenruo
2018-10-23 9:41 ` [PATCH 06/13] btrfs-progs: lowmem: rename delete_extent_tree_item() to delete_item() Su Yue
2018-10-24 0:15 ` Qu Wenruo
2018-10-23 9:41 ` [PATCH 07/13] btrfs-progs: lowmem: delete unaligned bytes extent data under repair Su Yue
2018-10-24 0:16 ` Qu Wenruo
2018-10-23 9:41 ` [PATCH 08/13] btrfs-progs: Revert "btrfs-progs: Add repair and report function for orphan file extent." Su Yue
2018-10-24 0:28 ` Qu Wenruo
2018-10-23 9:41 ` [PATCH 09/13] btrfs-progs: Revert "btrfs-progs: Record orphan data extent ref to corresponding root." Su Yue
2018-10-24 0:29 ` Qu Wenruo
2018-11-07 9:09 ` Su Yanjun <suyj.fnst@cn.fujitsu.com>
2018-11-07 9:14 ` Qu Wenruo
2018-10-23 9:41 ` [PATCH 10/13] btrfs-progs: check: fix bug in find_possible_backrefs Su Yue
2018-10-24 0:34 ` Qu Wenruo
2018-11-07 6:28 ` Su Yanjun <suyj.fnst@cn.fujitsu.com>
2018-11-07 6:40 ` Qu Wenruo
2018-10-23 9:41 ` [PATCH 11/13] btrfs-progs: check: Delete file extent item with unaligned extent backref Su Yue
2018-10-24 0:45 ` Qu Wenruo
2018-11-07 6:21 ` Su Yanjun <suyj.fnst@cn.fujitsu.com>
2018-11-07 6:38 ` Qu Wenruo
2018-11-07 7:04 ` Su Yanjun <suyj.fnst@cn.fujitsu.com>
2018-11-07 7:13 ` Qu Wenruo
2018-10-23 9:41 ` [PATCH 12/13] btrfs-progs: tests: add case for inode lose one file extent Su Yue
2018-10-23 9:41 ` [PATCH 13/13] btrfs-progs: fsck-test: enable lowmem repair for case 001 Su Yue
2018-10-23 9:45 ` [PATCH 00/13] btrfs-progs: fixes of file extent in original and lowmem check 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=4e76d260-0496-3bfc-f9b8-3b6ab68bd25b@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=suy.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).