Date: Fri, 23 Jan 2004 14:10:18 +0200 From: Ian Freislich <if@hetzner.co.za> To: John Polstra <jdp@polstra.com> Cc: freebsd-current@freebsd.org Subject: Re: openssh no longer compiles (as part of make world) Message-ID: <E1Ak08g-0009ow-00@hetzner.co.za> In-Reply-To: Your message of "Thu, 22 Jan 2004 19:22:38 PST." <XFMail.20040122192238.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John Polstra wrote: > On 22-Jan-2004 Ian Freislich wrote: > > wrote: > >> Ian Freislich <if@hetzner.co.za> writes: > >> > Hmmm, very interesting. rm /home/ncvs/src/crypto/openssh/channels.c,v > >> > and re-cvsupping and then updating this file fixed that. Wierd, I > >> > would have thought cvsup would have noticed a corrupted file and > >> > transferred the whole file. > >> > >> it might not if you use the -s option. if you do, you might want to > >> run cvsup without -s once in a while just to be sure. I generally run > >> cvsup without -s every night, and with -s every hour the rest of the > >> day. > > > > I do run cvsup without -s: 'cvsup -L2 /root/supfile-cvs' > > This ought to be a FAQ. Problems like this happen when you have had > filesystem corruption on the client machine. CVSup can't detect > that kind of corruption. At the time it compared MD5 checksums, the > data was still in OS buffers and it was still intact, so the > checksums compared correctly. All of the metadata such as the > timestamps and the file size are correct, so it has no reason to > believe subsequently that there is a need to update the file. I'm sorry that I didn't keep the ,v file that was corrupted. I'm not sure that the OS buffers explain this because the machine had been rebooted several times during the period that cvsup had not refetched the corrupted file. I'm not doubting filesystem corruption though. Ian -- Ian Freislich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1Ak08g-0009ow-00>