Matthias Scheler <[email protected]> wrote: > I remember an issue like that with "rump_smbfs" a while ago. The problem > was that a VOP_SETATTR() on PUFFS sets the file-size. And in this case > the backend in SMBFS used 32-bit file offset and therefore truncated > the file.
That is not something like this: it occurs at offsets as low as 16384, and there is always valid data after the zeroed chunk. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz [email protected]
