From: Dave Chinner <david@fromorbit.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: axboe@kernel.dk, Eric Sandeen <sandeen@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
device-mapper development <dm-devel@redhat.com>,
linux-fsdevel@vger.kernel.org, hch@lst.de,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [dm-devel] [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space
Date: Fri, 24 Jul 2015 09:05:09 +1000 [thread overview]
Message-ID: <20150723230509.GD3902@dastard> (raw)
In-Reply-To: <alpine.LRH.2.02.1507231306160.16526@file01.intranet.prod.int.rdu2.redhat.com>
On Thu, Jul 23, 2015 at 01:08:36PM -0400, Mikulas Patocka wrote:
> On Wed, 22 Jul 2015, Dave Chinner wrote:
> > On Wed, Jul 22, 2015 at 10:09:23AM +1000, Dave Chinner wrote:
> > > On Tue, Jul 21, 2015 at 01:47:53PM -0400, Mike Snitzer wrote:
> > > | $ cat
> > > | /sys/fs/xfs/vda/meta_write_errors/enospc/transient_fail_at_umount
> > > | 1
[...]
> You can just stop retrying the I/Os when the user attempts to unmount the
> filesystem - then, you don't need any configuration option.
See above - the default will do that, but there are users who do not
want that unmount behaviour....
-Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-07-23 23:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 15:18 [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space Mike Snitzer
2015-07-20 22:36 ` Dave Chinner
2015-07-20 23:20 ` Mike Snitzer
2015-07-21 0:36 ` Dave Chinner
2015-07-21 15:34 ` Eric Sandeen
2015-07-21 17:47 ` Mike Snitzer
2015-07-22 0:09 ` Dave Chinner
2015-07-22 1:00 ` Dave Chinner
2015-07-22 1:40 ` Mike Snitzer
2015-07-22 2:37 ` Dave Chinner
2015-07-22 13:34 ` Mike Snitzer
2015-07-22 16:28 ` Eric Sandeen
2015-07-22 16:51 ` Mike Snitzer
2015-07-23 5:10 ` Dave Chinner
2015-07-23 14:33 ` Mike Snitzer
2015-07-23 15:50 ` [RFC PATCH] block: dm thin: export how block device handles -ENOSPC Mike Snitzer
2015-07-23 16:43 ` [RFC PATCH] block: xfs: dm thin: train XFS to give up on retrying IO if thinp is out of space Vivek Goyal
2015-07-23 23:00 ` Dave Chinner
2015-07-24 2:34 ` Vivek Goyal
2015-07-23 17:08 ` [dm-devel] " Mikulas Patocka
2015-07-23 23:05 ` Dave Chinner [this message]
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=20150723230509.GD3902@dastard \
--to=david@fromorbit.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=sandeen@redhat.com \
--cc=snitzer@redhat.com \
--cc=vgoyal@redhat.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;
as well as URLs for NNTP newsgroup(s).