From: Omar Sandoval <osandov@osandov.com>
To: Chandan Rajendra <chandan@linux.vnet.ibm.com>
Cc: Chris Mason <clm@fb.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 0/3] Btrfs: fix free space tree bitmaps+tests on big-endian systems
Date: Fri, 15 Jul 2016 12:15:15 -0700 [thread overview]
Message-ID: <20160715191515.GA13357@vader.DHCP.thefacebook.com> (raw)
In-Reply-To: <48955009.Up9FeqXyzx@localhost.localdomain>
On Fri, Jul 15, 2016 at 12:34:10PM +0530, Chandan Rajendra wrote:
> On Thursday, July 14, 2016 07:47:04 PM Chris Mason wrote:
> > On 07/14/2016 07:31 PM, Omar Sandoval wrote:
> > > From: Omar Sandoval <osandov@fb.com>
> > >
> > > So it turns out that the free space tree bitmap handling has always been
> > > broken on big-endian systems. Totally my bad.
> > >
> > > Patch 1 fixes this. Technically, it's a disk format change for
> > > big-endian systems, but it never could have worked before, so I won't go
> > > through the trouble of any incompat bits. If you've somehow been using
> > > space_cache=v2 on a big-endian system (I doubt anyone is), you're going
> > > to want to mount with nospace_cache to clear it and wait for this to go
> > > in.
> > >
> > > Patch 2 fixes a similar error in the sanity tests (it's the same as the
> > > v2 I posted here [1]) and patch 3 expands the sanity tests to catch the
> > > oversight that patch 1 fixes.
> > >
> > > Applies to v4.7-rc7. No regressions in xfstests, and the sanity tests
> > > pass on x86_64 and MIPS.
> >
> > Thanks for fixing this up Omar. Any big endian friends want to try this
> > out in extended testing and make sure we've nailed it down?
> >
>
> Hi Omar & Chris,
>
> I will run fstests with this patchset applied on ppc64 BE and inform you about
> the results.
>
Thanks, Chandan! I set up my xfstests for space_cache=v2 by doing:
mkfs.btrfs "$TEST_DEV"
mount -o space_cache=v2 "$TEST_DEV" "$TEST_DIR"
umount "$TEST_DEV"
and adding
export MOUNT_OPTIONS="-o space_cache=v2"
to local.config. btrfsck also needs the patch here [1].
Thanks again.
1: http://thread.gmane.org/gmane.comp.file-systems.btrfs/58382
--
Omar
next prev parent reply other threads:[~2016-07-15 19:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 23:31 [PATCH 0/3] Btrfs: fix free space tree bitmaps+tests on big-endian systems Omar Sandoval
2016-07-14 23:31 ` [PATCH 1/3] Btrfs: fix free space tree bitmaps " Omar Sandoval
2016-07-14 23:31 ` [PATCH 2/3] Btrfs: fix extent buffer bitmap tests " Omar Sandoval
2016-07-14 23:31 ` [PATCH 3/3] Btrfs: expand free space tree sanity tests to catch endianness bug Omar Sandoval
2016-07-14 23:47 ` [PATCH 0/3] Btrfs: fix free space tree bitmaps+tests on big-endian systems Chris Mason
2016-07-15 7:04 ` Chandan Rajendra
2016-07-15 19:15 ` Omar Sandoval [this message]
2016-07-17 12:19 ` Chandan Rajendra
2016-07-18 18:43 ` Chris Mason
2016-07-18 22:31 ` Omar Sandoval
2016-07-19 16:06 ` Chandan Rajendra
2016-07-19 19:25 ` Chris Mason
2016-08-18 20:33 ` Omar Sandoval
2016-08-26 11:06 ` Anatoly Pugachev
2016-08-27 0:56 ` Omar Sandoval
2016-08-27 7:16 ` Anatoly Pugachev
2016-09-21 14:50 ` David Sterba
2016-09-21 17:35 ` Omar Sandoval
2016-07-31 13:04 ` Anatoly Pugachev
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=20160715191515.GA13357@vader.DHCP.thefacebook.com \
--to=osandov@osandov.com \
--cc=chandan@linux.vnet.ibm.com \
--cc=clm@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.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 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).