From owner-freebsd-questions@FreeBSD.ORG Mon Mar 20 11:30:19 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C78D16A420 for ; Mon, 20 Mar 2006 11:30:19 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from asmtp-out3.blueyonder.co.uk (asmtp-out3.blueyonder.co.uk [195.188.213.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9051443D45 for ; Mon, 20 Mar 2006 11:30:17 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [82.41.229.4] (helo=[192.168.0.2]) by asmtp-out3.blueyonder.co.uk with esmtp (Exim 4.52) id 1FLIaW-0004xi-Ee; Mon, 20 Mar 2006 11:30:16 +0000 Message-ID: <441E9246.6090603@dial.pipex.com> Date: Mon, 20 Mar 2006 11:30:14 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: Paolo Tealdi References: <7.0.1.0.0.20060315131135.0327a978@polito.it> <441821AD.1080605@dial.pipex.com> <7.0.1.0.0.20060315153306.02165290@polito.it> <4418344D.8080003@dial.pipex.com> <7.0.1.0.0.20060316091138.01fa4ae8@polito.it> <44194A05.4010600@dial.pipex.com> <7.0.1.0.0.20060316133119.020459c8@polito.it> <441966C6.1000001@dial.pipex.com> <7.0.1.0.0.20060320085802.01fe6100@polito.it> In-Reply-To: <7.0.1.0.0.20060320085802.01fe6100@polito.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: dump level 9 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Mar 2006 11:30:19 -0000 Paolo Tealdi wrote: > Hurra ! > I resolved! Excellent! > > Obviously newfs did not resolve. :-( > But... > i studied the problem from another point of view reading dump sources, > as you suggested. > dump thinks that file has changed if : > a) modification date has changed > b) cdate has changed : cdate is the date of inode modification > > throught stat utility (very nice) i noticed that every file under > /home had a cdate very recent. > comparing dates i got solution : sophos antivirus, that starts every > night with a complete /home scan, modifies cdate. > Unfortunately i installed sophos antivirus more or less in the same > days of the power cut ... Damn. Kicking myself for not asking you about cdate. > > I think that sophos support will receive a question in the next few > days ... :-) Shame your email can't include a big kick in the pants for whoever a) thought this was a good idea in the first place b) didn't pick up such dumb behaviour in testing. --Alex