1rst flush of a file on disk
At the time of the 1rst flush on disk of a file, the file does not yet
exist on the storages. When the STORCLI has to write data not align on
the rozofs block size bondary, it has to prior read the file from disk
to complement the data. Up to now the STORCLI would reject the write
request when it could not read the file. For this reason the rozofsmount
had to tell the STORCLI not to read on disk since the file is empty.
In fact it is not so simple for sure for the rozofsmount to know whether
some data exist on disk or not in a multi server environment. This may
lead to write failure or data lost.
Now the rozofsmount do not care anymore whether the file exist or not when
requesting a flush to the STORCLI. The STORCLI processes to a read
request on disk to complement the not aligned data if needed. The STORCLI
takes into account a ENOENT response from every storage to detect that
the file has never been written on disk and that there is no need to
complement the data to write.