From: Brian Foster <bfoster@redhat.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: Gionatan Danti <g.danti@assyoma.it>, linux-xfs@vger.kernel.org
Subject: Re: Shutdown filesystem when a thin pool become full
Date: Tue, 20 Jun 2017 13:01:29 -0400 [thread overview]
Message-ID: <20170620170127.GB3348@bfoster.bfoster> (raw)
In-Reply-To: <20170620153444.GM21846@wotan.suse.de>
On Tue, Jun 20, 2017 at 05:34:44PM +0200, Luis R. Rodriguez wrote:
> On Tue, Jun 20, 2017 at 11:28:58AM -0400, Brian Foster wrote:
> > On Tue, Jun 20, 2017 at 05:03:42PM +0200, Gionatan Danti wrote:
> > > Il 20-06-2017 13:05 Carlos Maiolino ha scritto:
> > > >
> > ...
> > > > Surely this can be improved, but at the end, the application will always
> > > > need to
> > > > check for its own data.
> > >
> > > I think the key improvement would be to let the filesystem know about the
> > > full thin pool - ie: returing ENOSPC at some convenient time (a wild guess:
> > > can we return ENOSPC during delayed block allocation?)
> > >
> >
> > FWIW, I played with something like this a while ago. See the following
> > (and its predecessor for a more detailed cover letter):
> >
> > http://oss.sgi.com/pipermail/xfs/2016-April/048166.html
>
> Any chance this is up in a tree somewhere?
>
No, I don't have an upstream tree hosted anywhere unfortunately.
Brian
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-20 17:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 14:25 Shutdown filesystem when a thin pool become full Gionatan Danti
2017-05-22 23:09 ` Carlos Maiolino
2017-05-23 10:56 ` Gionatan Danti
2017-05-23 11:01 ` Gionatan Danti
2017-05-23 12:27 ` Carlos Maiolino
2017-05-23 20:05 ` Gionatan Danti
2017-05-23 21:33 ` Eric Sandeen
2017-05-24 17:52 ` Gionatan Danti
2017-06-13 9:09 ` Gionatan Danti
2017-06-15 11:51 ` Gionatan Danti
2017-06-15 13:14 ` Carlos Maiolino
2017-06-15 14:10 ` Carlos Maiolino
2017-06-15 15:04 ` Gionatan Danti
2017-06-20 10:19 ` Gionatan Danti
2017-06-20 11:05 ` Carlos Maiolino
2017-06-20 15:03 ` Gionatan Danti
2017-06-20 15:28 ` Brian Foster
2017-06-20 15:34 ` Luis R. Rodriguez
2017-06-20 17:01 ` Brian Foster [this message]
2017-06-20 15:55 ` Gionatan Danti
2017-06-20 17:02 ` Brian Foster
2017-06-20 18:43 ` Gionatan Danti
2017-06-21 9:44 ` Carlos Maiolino
2017-06-21 10:39 ` Gionatan Danti
2017-06-21 9:53 ` Brian Foster
2017-05-23 12:11 ` Carlos Maiolino
2017-05-23 13:24 ` Eric Sandeen
2017-05-23 20:23 ` Gionatan Danti
2017-05-24 7:38 ` Carlos Maiolino
2017-05-24 17:50 ` Gionatan Danti
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=20170620170127.GB3348@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=g.danti@assyoma.it \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@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