Alexander Bluhm wrote: > GNU dd has the conv=fsync feature which does an fsync(2) after final > write to output. I find this useful for write performance measurement > through the file system without buffer cache optimization. Others > may like the reliable storage guarantee of fsync(2). > > Do we want dd conv=fsync in OpenBSD?
What does gnu dd do if the output is stdout? Is it an error? With this patch, I get dd: fsync stdout: Invalid argument after the transfer is complete. Should there be an fstat check to make sure it's a regular file? > +.It Cm fsync > +Write output to permanent storage device before finishing. I know this wording is similar to fsync(2), but I think I'd prefer just a reference. The output may not be permanent storage. What about Call .Xr fsync 2 on the output file before exiting.
