On Tue, Jan 24, 2017 at 08:48:37AM -0800, Darrick J. Wong wrote:
> I'd just print out:
>
> "Per-AG reservation for AG ${agno} failed. Filesystem may run out of space."
Sure, I can do that.
>
> if any of the (now three) invocations of __xfs_ag_resv_init() returns
> ENOSPC, since the AG is more than 98% full. Some day, a sysadmin could
> then use the fsmap data to identify which inodes are using the most
> space in that AG and arrange to migrate/remove/etc the data to another
> AG.
But for all but the reflink one this can't happen as the reservations
have been there since the beginning. And if they fail neverless we fail
the mount. Or am I missing something here?
--
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
