Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1638200 > unrolled thread
| Started by | Jeff Layton <jlayton@redhat.com> |
|---|---|
| First post | 2017-05-09 17:40 +0200 |
| Last post | 2017-05-09 17:40 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RFC xfstests PATCH] xfstests: add a writeback error handling test Jeff Layton <jlayton@redhat.com> - 2017-05-09 17:40 +0200
| From | Jeff Layton <jlayton@redhat.com> |
|---|---|
| Date | 2017-05-09 17:40 +0200 |
| Subject | Re: [RFC xfstests PATCH] xfstests: add a writeback error handling test |
| Message-ID | <tFfp0-3Bv-25@gated-at.bofh.it> |
On Mon, 2017-04-24 at 08:00 -0700, Christoph Hellwig wrote: > On Mon, Apr 24, 2017 at 09:45:51AM -0400, Jeff Layton wrote: > > With the patch series above, ext4 now passes. xfs and btrfs end up in > > r/o mode after the test. xfs returns -EIO at that point though, and > > btrfs returns -EROFS. What behavior we actually want there, I'm not > > certain. We might be able to mitigate that by putting the journals on a > > separate device? > > This looks like XFS shut down because of a permanent write error from > dm-error. Which seems like the expected behavior. Oops, didn't see this message earlier... Yeah, that's entirely reasonable when there is a write error to the journal. The latest version of this uses $SCRATCH_LOGDEV to put the journal on a different device, and with that I get the expected behavior from xfs. Thanks, -- Jeff Layton <jlayton@redhat.com>
Back to top | Article view | linux.kernel
csiph-web