On 25 Oct 2014, at 06:39, Emmanuel Dreyfus m...@netbsd.org wrote:
Summary: when writing to a PUFFS filesystem through page cache, we do
not know if backend storage is really available. If it is not, cache
flush may get EDQUOT or ENOSPC and the process cannot terminate (it gets
stuck in DE
On Sat, Oct 25, 2014 at 09:48:49AM +0200, J. Hannken-Illjes wrote:
On 25 Oct 2014, at 06:39, Emmanuel Dreyfus m...@netbsd.org wrote:
Summary: when writing to a PUFFS filesystem through page cache, we do
not know if backend storage is really available. If it is not, cache
flush may get
Chuck Silvers c...@chuq.com wrote:
but more fundamentally, since puffs code cannot prevent changes to the file
in the underlying fs (ie. changes that don't go through puffs), any
preallocation done by puffs can be undone before it does any good.
the puffs code just needs to be fixed to handle
