On Wed, Aug 23, 2017 at 01:22:13PM -0700, Darrick J. Wong wrote: > Looks ok... but is there a xfstest somewhere that can be coaxed into > reproducing this? The QA team that reported this to me required multiple hours to reproduce it. I think the key is heavy metadata ops in a full fs, but all my simple attempts to reproduce it failed. > I'm looking at what this code does and have been > wondering why it even tries this weird workaround in the first place? I think this dates to the time where we weren't very strict about transaction space reservations - it basically plays lose when near enospc at the cost of rarely shutting down the whole file system due to a dirty transaction. -- 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
