From: Eric Sandeen <sandeen@sandeen.net>
To: "L.A. Walsh" <xfs@tlinx.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: why crc req on free-inobt & file-type-indir options?
Date: Thu, 06 Aug 2015 22:36:07 -0700 [thread overview]
Message-ID: <55C443C7.3010608@sandeen.net> (raw)
In-Reply-To: <55C41D75.4040504@tlinx.org>
On 8/6/15 7:52 PM, L.A. Walsh wrote:
>
> Could anyone point me at the discussion or literature as to why
> a free-inodeB-Tree and inline-types, should *REQUIRE* a -crc=1 option?
FWIW, you can enable ftype w/o crcs. Today it's a little broken, if you
specify in the wrong order it fails. I just sent a patch for that.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-08-07 5:36 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
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 [this message]
-- 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=55C443C7.3010608@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.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 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.