Chuck Silvers 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 such ENOS
Chuck Silvers 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 such ENOS
On Sat, Oct 25, 2014 at 09:48:49AM +0200, J. Hannken-Illjes wrote:
> On 25 Oct 2014, at 06:39, Emmanuel Dreyfus 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 E
On 25 Oct 2014, at 06:39, Emmanuel Dreyfus 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 state).
>
> Pr
David Holland wrote:
> Yes but there's quotacheck. Is there something similar for extattrs?
Quotacheck oberves filesystem usage and updates usage recorded in quota
file. What similar do you imagine with extended attributes?
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
