public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/2] xfsprogs: fixes for CRC support
Date: Thu, 19 Jun 2014 15:33:50 +1000	[thread overview]
Message-ID: <1403156032-18525-1-git-send-email-david@fromorbit.com> (raw)

Hi folks,

These two patches correct a couple of oversights in the new CRC
support. Firstly, repair actually validates ACLs on disk (from a
consistency POV, not correctness) and so it needs to know that
v5 formats handle a lot more than 25 ACLs.

Secondly, we forgot all about documenting the "-m crc=1" option in
the mkfs.xfs(8) man page. So the second patch fixes that and also
adds the missing documentation for the free inode btree option as
well.

With these two fixes and all the other xfsprogs patches I've pulled
in and are currently testing, we're pretty much ready for a 3.2.1-rc
release. Is there anything that we know about that we don't have
patches for yet that needs to be done for 3.2.1?

Cheers,

Dave.

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

             reply	other threads:[~2014-06-19  5:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19  5:33 Dave Chinner [this message]
2014-06-19  5:33 ` [PATCH 1/2] repair: support more than 25 ACLs Dave Chinner
2014-06-19 13:01   ` Brian Foster
2014-06-19 21:14     ` Dave Chinner
2014-06-19 21:57       ` [PATCH 1/2 V2] " Dave Chinner
2014-06-20 12:14       ` [PATCH 1/2] " Brian Foster
2014-06-21  0:13         ` Dave Chinner
2014-06-19  5:33 ` [PATCH 2/2] mkfs: add "-m" options to the man page Dave Chinner
2014-06-19 13:02   ` Brian Foster

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=1403156032-18525-1-git-send-email-david@fromorbit.com \
    --to=david@fromorbit.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox