[ Charset UTF-8 unsupported, converting... ] > On Thu, Mar 2, 2017 at 4:31 PM, Rodney W. Grimes > <freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote: > ... > > Even if that is the case file system cache effects should NOT be > > visible to a userland process. This is NOT as if your running > > 2 different processing beating on a file. Your test cases are > > serialially syncronous shell invoked commands seperated with > > && the results should be exact and predictable. > > > > When strip returns the operation from the userland perspecive > > is completed and any and all processeses started after that > > should have the view of the completed strip command. > > > > This IS a bug. > > Would the same statement necessarily apply if the filesystem was > writing things asynchronously to the backing storage?
Caching should^h^h^h^hshall be transparent to a userland process. Are you actually advocating that a userland process should be able to see that zfs is write caching meta data? The strip(1) command has completed and exited, pola dictates that anything I asked strip(1) to do be reflected in all commands or system calls executed after it. Anything else would be a bug. > Thanks, > -Ngie -- Rod Grimes rgri...@freebsd.org _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
