linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: Eric Sandeen <sandeen@sandeen.net>,
	Hironori Shiina <shiina.hironori@gmail.com>,
	linux-xfs@vger.kernel.org, Donald Douwsma <ddouwsma@redhat.com>,
	Hironori Shiina <shiina.hironori@fujitsu.com>
Subject: Re: [RFC PATCH V3] xfsrestore: fix rootdir due to xfsdump bulkstat misuse
Date: Fri, 21 Apr 2023 09:14:56 -0700	[thread overview]
Message-ID: <20230421161456.GP360895@frogsfrogsfrogs> (raw)
In-Reply-To: <20230421091006.nodvelbpuztwoir6@andromeda>

On Fri, Apr 21, 2023 at 11:10:06AM +0200, Carlos Maiolino wrote:
> Hi Darrick.
> 
> > > >> This patch adds a '-x' option (another awkward thing is that
> > > >> the codebase doesn't support long options) to address
> > > >> problamatic images by searching for the real dir, the reason
> > > >> that I don't enable it by default is that I'm not very confident
> > > >> with the xfsrestore codebase and xfsdump bulkstat issue will
> > > >> also be fixed immediately as well, so this function might be
> > > >> optional and only useful for pre-exist corrupted dumps.
> > > >
> > > > As far as fixing xfsdump -- wasn't XFS_BULK_IREQ_SPECIAL_ROOT supposed
> > > > to solve that problem by enabling dump to discover it it's really been
> > > > passed the fs root directory?
> > >
> > > Yes, but as I understand it this patch is to allow the user to recover
> > > from an already corrupted dump, at restore time, right?
> > 
> > Right, though I still haven't seen any patches to dump to employ
> > XFS_BULK_IREQ_SPECIAL_ROOT to avoid spitting out bad dumps in the first
> > place.  I think the heuristic that we applied is probably good enough,
> > but we might as well query the kernel when possible.
> > 
> > > This still feels like deep magic in xfsdump that most people struggle
> > > to understand, but it seems clear to me that the changes here are truly
> > > isolated to the new "-x" option - IOWs if "-x" is not specified, there is
> > > no behavior change at all.
> > >
> > > Since this is intended to attempt recovery from an already-corrupted
> > > dump image as a last resort, and given that there are already some xfstests
> > > in place to validate the behavior, I feel reasonably comfortable with
> > > merging this.
> > 
> > Documentation nit: Can restore detect that it's been given a corrupt
> > dump, and if so, should it warn the user to rerun with -x?
> > 
> > --D
> 
> I am assuming that even though you have concerns about not having
> XFS_BULK_IREQ_SPECIAL_ROOT employed in dump yet (and the documentation nit :),
> you are not opposed to have this patch merged?

Correct.  Consider this my somewhat passive-aggressive prod not to
forget to improve dump's "I'm doing something stupid" detector.

--D

> 
> -- 
> Carlos Maiolino

      reply	other threads:[~2023-04-21 16:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 12:51 [RFC PATCH] xfsrestore: fix rootdir due to xfsdump bulkstat misuse Gao Xiang
2020-11-13 14:10 ` Eric Sandeen
2020-11-13 14:15   ` Gao Xiang
2020-11-16  8:23     ` Gao Xiang
2020-11-16  8:07 ` [RFC PATCH v2] " Gao Xiang
2020-11-16  8:13   ` Gao Xiang
2021-09-27 15:00   ` Bill O'Donnell
2021-12-20 15:14   ` Masayoshi Mizuma
2022-06-10 23:05   ` Hironori Shiina
2022-06-30 19:19     ` Hironori Shiina
2022-09-28 19:10   ` [RFC PATCH V3] " Hironori Shiina
2022-09-29 18:17     ` Darrick J. Wong
2023-04-19 14:16       ` Eric Sandeen
2023-04-19 15:40         ` Darrick J. Wong
2023-04-21  9:10           ` Carlos Maiolino
2023-04-21 16:14             ` 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=20230421161456.GP360895@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=ddouwsma@redhat.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=shiina.hironori@fujitsu.com \
    --cc=shiina.hironori@gmail.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).