public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: L A Walsh <xfs@tlinx.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfsdump 3.1.10 released
Date: Thu, 17 Feb 2022 06:58:57 -0800	[thread overview]
Message-ID: <620E62B1.2030801@tlinx.org> (raw)
In-Reply-To: <31eec545-8d42-2147-59bf-5eaffaa230d1@sandeen.net>



On 2022/02/14 06:28, Eric Sandeen wrote:
> On 2/12/22 8:47 PM, L A Walsh wrote:
>>
>> On 2022/02/11 12:59, Eric Sandeen wrote:
>>> Hi folks,
>>> because I don't want to stall on getting the fix for the root inode
>>> problems out there any longer. It's been ... quite long enough.
>>>
>>> Next release we can think about the dmapi junk, and possibly the
>>> workaround for the broken dumps with the root inode problem.
>>>
>>> This should at least be generating valid dumps on those filesystems
>>> with "interesting" geometry, again.
>> ----
>>
>> Thanks for the Cc.
>>
>>  As near as I understand your comments, this should generate new dumps that won't
>> have the problem I'm seeing, but will still leave previous dumps in the old format
>> that may show problems upon restoration.
> 
> Correct, I want to spend more time on the workaround to be sure we have confidence
> in it, sorry.
---

	No need to apologize, Fixing the problem in stages is perfectly logical
Even if some existing dumps have inconsistencies in them, cutting off the source
of them will guarantee the number of those existing dumps will 
decrease, eventually, assuming recycling of dump-space to zero.  :-)


      reply	other threads:[~2022-02-17 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 20:59 [ANNOUNCE] xfsdump 3.1.10 released Eric Sandeen
2022-02-13  2:47 ` L A Walsh
2022-02-14 14:28   ` Eric Sandeen
2022-02-17 14:58     ` L A Walsh [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=620E62B1.2030801@tlinx.org \
    --to=xfs@tlinx.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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