On Tue, Dec 12, 2017 at 10:03:42PM -0800, Darrick J. Wong wrote: > From: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > > We're removing from XFS the ability to perform no-allocation file > creation. This was added years ago because someone at SGI demanded that > we still be able to create (empty?) files with zero free blocks Just to correct the record, it wasn't SGI that demanded this - it was implemented by SGI a long, long time ago (~1998) in response to customer demands. > remaining so long as there were free inodes and space in existing > directory blocks. This came at an unacceptable risk of ENOSPC'ing > midway through a transaction and shutting down the fs, so we're removing > it for the create case. Well, 20 years later we consider it an unacceptible risk. :P > However, some tests fail as a result, so fix them to be more flexible > about not failing when a dir/file creation fails due to ENOSPC. > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> Looks fine. Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx> -- Dave Chinner david@xxxxxxxxxxxxx -- 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
