Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Donald Douwsma <ddouwsma@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfsrestore: suggest -x rather than assert for false roots
Date: Thu, 29 Jun 2023 08:00:55 -0700	[thread overview]
Message-ID: <20230629150055.GE11441@frogsfrogsfrogs> (raw)
In-Reply-To: <20230623062918.636014-1-ddouwsma@redhat.com>

On Fri, Jun 23, 2023 at 04:29:18PM +1000, Donald Douwsma wrote:
> If we're going to have a fix for false root problems its a good idea to
> let people know that there's a way to recover, error out with a useful
> message that mentions the `-x` option rather than just assert.
> 
> Before
> 
>   xfsrestore: searching media for directory dump
>   xfsrestore: reading directories
>   xfsrestore: tree.c:757: tree_begindir: Assertion `ino != persp->p_rootino || hardh == persp->p_rooth' failed.
>   Aborted
> 
> After
> 
>   xfsrestore: ERROR: tree.c:791: tree_begindir: Assertion `ino != persp->p_rootino || hardh == persp->p_rooth` failed.
>   xfsrestore: ERROR: False root detected. Recovery may be possible using the `-x` option
>   Aborted
> 
> Fixes: d7cba74 ("xfsrestore: fix rootdir due to xfsdump bulkstat misuse")
> Signed-off-by: Donald Douwsma <ddouwsma@redhat.com>
> ---
>  restore/tree.c | 13 +++++++++++--
>  1 file changed, 11 insertions(+), 2 deletions(-)
> 
> diff --git a/restore/tree.c b/restore/tree.c
> index bfa07fe..0b65d0f 100644
> --- a/restore/tree.c
> +++ b/restore/tree.c
> @@ -783,8 +783,17 @@ tree_begindir(filehdr_t *fhdrp, dah_t *dahp)
>  	/* lookup head of hardlink list
>  	 */
>  	hardh = link_hardh(ino, gen);
> -	if (need_fixrootdir == BOOL_FALSE)
> -		assert(ino != persp->p_rootino || hardh == persp->p_rooth);
> +	if (need_fixrootdir == BOOL_FALSE
> +		&& !(ino != persp->p_rootino || hardh == persp->p_rooth)) {

Usually we put the && operator on the line above.  But ignore that
comment if that's actually the predominant style in xfsrestore.

	if (need_fixrootdir == BOOL_FALSE &&
	    !(ino != persp->p_rootino || hardh == persp->p_rooth)) {

> +		mlog(MLOG_ERROR | MLOG_TREE, 

Trailing space.

> +			"%s:%d: %s: Assertion "
> +			"`ino != persp->p_rootino || hardh == persp->p_rooth` failed.\n",

Might be nice to put the entire string on one line for greppability?

		mlog(MLOG_ERROR | MLOG_TREE,
 "%s:%d: %s: Assertion `ino != persp->p_rootino || hardh == persp->p_rooth` failed.\n",

> +			__FILE__, __LINE__, __FUNCTION__);
> +		mlog(MLOG_ERROR | MLOG_TREE, _(
> +			"False root detected. "
> +			"Recovery may be possible using the `-x` option\n"));

Same here.

Otherwise this looks like a good improvement.

--D

> +		return NH_NULL;
> +	};
>  
>  	/* already present
>  	 */
> -- 
> 2.39.3
> 

      parent reply	other threads:[~2023-06-29 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  6:29 [PATCH] xfsrestore: suggest -x rather than assert for false roots Donald Douwsma
2023-06-23 14:04 ` Pavel Reichl
2023-06-29 15:00 ` Darrick J. Wong [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=20230629150055.GE11441@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=ddouwsma@redhat.com \
    --cc=linux-xfs@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