Just hit what I'm fairly sure is the same bug. Same errors logged.
Was attempting to use ' perl -pi -e "s!--!---!" ' to update some files on a Windows 2000 server from a Sarge desktop. Attempts to workaround by using cifs immediately after the problem occurred (I did reboot, but otherwise I was immediately into trying it with CIFS) results in "input/output" errors logged against files that had previously been operated on. So this may not be a suitable workaround, or it may be necessary to fix data corruption issues before using CIFS. At some point in the procedure the files were truncated to size 0. Data is now restored from a known good source. I will try a kernel from backports so I can get on with my work. Was this error introduced into Sarge since release, as I'm fairly sure this had worked in the past? The whole of Samba/SMB support in Sarge is very problematic, but this is the first time I've had it eat data. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]