All of lore.kernel.org
 help / color / mirror / Atom feed
From: "L.A. Walsh" <xfs@tlinx.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: why crc req on free-inobt & file-type-indir options?
Date: Fri, 07 Aug 2015 19:59:43 -0700	[thread overview]
Message-ID: <55C5709F.8030705@tlinx.org> (raw)
In-Reply-To: <620A4212-818A-4375-90FC-DBB0B91A84DB@sandeen.net>



Eric Sandeen wrote:
> 
>> On Aug 7, 2015, at 5:50 PM, L.A. Walsh <xfs@tlinx.org> wrote:
>> Q: should the versions of xfsdump&restore be the same as the rest of the xfsprogs?
> Nope, they are separate packages with separate versioning.
---
I see.  So how does one tell which version of xfsdump/restore should
be used to "safely" dump (and restore) a file system made
with version i.j.k of xfsprogs(mkfs.xfs) ?  Or is that possible?


_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-08-08  2:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07  2:52 why crc req on free-inobt & file-type-indir options? L.A. Walsh
2015-08-07  5:00 ` Eric Sandeen
2015-08-07  8:14   ` L.A. Walsh
2015-08-07 17:01     ` Eric Sandeen
2015-08-07 22:55     ` Dave Chinner
2015-08-08  0:50       ` L.A. Walsh
2015-08-08  1:45         ` Eric Sandeen
2015-08-08  2:59           ` L.A. Walsh [this message]
2015-08-09  0:11             ` Dave Chinner
2015-08-13  0:24       ` L.A. Walsh
2015-08-07  8:17   ` L.A. Walsh
2015-08-07  5:36 ` Eric Sandeen
  -- strict thread matches above, loose matches on Subject: below --
2015-08-07  2:53 L.A. Walsh

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=55C5709F.8030705@tlinx.org \
    --to=xfs@tlinx.org \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.