From: Anton Blanchard <anton@samba.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Jens Axboe <axboe@kernel.dk>,
Stephen Rothwell <sfr@canb.auug.org.au>,
jack@suse.cz, linux-kernel@vger.kernel.org, axboe@fb.com,
torvalds@linux-foundation.org,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
Paul Mackerras <paulus@samba.org>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: ext4 filesystem corruption with 4.10-rc2 on ppc64le
Date: Thu, 5 Jan 2017 21:44:10 +1100 [thread overview]
Message-ID: <20170105214410.0fc5cd58@kryten> (raw)
In-Reply-To: <20170104152837.wdh7cdncs7gyged7@thunk.org>
Hi Ted,
> Anton or Chandan, could you do me a favor and verify whether or not
> 64k block sizes are working for you on ppcle on ext4 by running
> xfstests? Light duty testing works for me but when I stress ext4 with
> pagesize==blocksize on ppcle64 via xfstests, it blows up. I suspect
> (but am not sure) it's due to (non-upstream) device driver issues, and
> a verification that you can run xfstests on your ppcle64 systems using
> standard upstream device drivers would be very helpful, since I don't
> have easy console access on the machines I have access to at
> $WORK. :-(
I fired off an xfstests run, and it looks good. There are 3 failures,
but they seem to be setup issues on my part. I also double checked
those same three failed on 4.8.
Chandan has been running the test suite regularly, and plans to do a
run against mainline too.
Anton
next prev parent reply other threads:[~2017-01-05 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 5:18 ext4 filesystem corruption with 4.10-rc2 on ppc64le Anton Blanchard
2017-01-04 6:02 ` Chandan Rajendra
2017-01-04 15:28 ` Theodore Ts'o
2017-01-04 16:23 ` Jens Axboe
2017-01-04 18:09 ` Linus Torvalds
2017-01-05 10:44 ` Anton Blanchard [this message]
2017-01-09 4:10 ` Chandan Rajendra
2017-01-04 7:34 ` luigi burdo
2017-01-04 15:09 ` Jens Axboe
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=20170105214410.0fc5cd58@kryten \
--to=anton@samba.org \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=chandan@linux.vnet.ibm.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).