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@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
