I've just moved our school's library database from a Windows NT machine
to
a FreeBSD 3.4-STABLE machine running Samba 2.0.6 installed from the port.
I've had a lot of files become corrupted since then. The support house
that has had to repair these files, said that the beginning and end of the
file are there, but there's a big gap of nulls in the middle. I'm using
log level = 2 and the following is a sample from our log file. There are
many of these in our log.
[2000/01/24 13:36:19, 0] lib/util_sock.c:write_socket_data(540)
write_socket_data: write failure. Error = Broken pipe
[2000/01/24 13:38:27, 0] lib/util_sock.c:write_socket_data(540)
write_socket_data: write failure. Error = Broken pipe
Has anyone seen this problem or know what can be causing it?
I would assume that if the problem was hardware, the software should be
able to recover the situation.
Regards
John Ryan
Systems Manager
King George V School
Hong Kong
