This error handling was the biggest obstacle last time we tried it, so let's remove it for now. However: On Wed, Aug 12, 2015 at 08:49:43AM +1000, Dave Chinner wrote: > Remove the nonblocking optimisation done for mapping lookups during > writeback. It's not clear that leaving a hole in the writeback range > just because we couldn't get a lock is really a win, as it makes us > do another small random IO later on rather than a large sequential > IO now. The fs-writeback.c will usually move to a different inode, so I don't think it's actually that bad. _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
