On Fri, Feb 07, 2020 at 12:04:20PM -0500, Jeff Layton wrote: > You're probably wondering -- Where are v1 and v2 sets? > > I did the first couple of versions of this set back in 2018, and then > got dragged off to work on other things. I'd like to resurrect this set > though, as I think it's valuable overall, and I have need of it for some > other work I'm doing. > > Currently, syncfs does not return errors when one of the inodes fails to > be written back. It will return errors based on the legacy AS_EIO and > AS_ENOSPC flags when syncing out the block device fails, but that's not > particularly helpful for filesystems that aren't backed by a blockdev. > It's also possible for a stray sync to lose those errors. > > The basic idea is to track writeback errors at the superblock level, > so that we can quickly and easily check whether something bad happened > without having to fsync each file individually. syncfs is then changed > to reliably report writeback errors, and a new ioctl is added to allow > userland to get at the current errseq_t value w/o having to sync out > anything. So what, exactly, can userspace do with this error? It has no idea at all what file the writeback failure occurred on or even what files syncfs() even acted on so there's no obvious error recovery that it could perform on reception of such an error. > I do have a xfstest for this. I do not yet have manpage patches, but > I'm happy to roll some once there is consensus on the interface. > > Caveats: > > - Having different behavior for an O_PATH descriptor in syncfs is > a bit odd, but it means that we don't have to grow struct file. Is > that acceptable from an API standpoint? It's an ugly wart, IMO. But because we suck at APIs, I'm betting that we'll decide this is OK or do something even worse... > - This adds a new generic fs ioctl to allow userland to scrape the > current superblock's errseq_t value. It may be best to present this > to userland via fsinfo() instead (once that's merged). I'm fine with > dropping the last patch for now and reworking it for fsinfo if so. What, exactly, is this useful for? Why would we consider exposing an internal implementation detail to userspace like this? Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx
