Date: Fri, 25 Oct 2013 11:38:24 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Matthias Apitz <guru@unixarea.de> Cc: freebsd-questions@freebsd.org Subject: Re: tool for checking integrity of a file system DUMP Message-ID: <alpine.BSF.2.00.1310251135520.70337@wonkity.com> In-Reply-To: <20131025130419.GA1969@tiny.Sisis.de> References: <20131025082352.GA15369@sh4-5.1blu.de> <alpine.BSF.2.00.1310250655090.68059@wonkity.com> <20131025130419.GA1969@tiny.Sisis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3512871622-1514343918-1382722704=:70337 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Fri, 25 Oct 2013, Matthias Apitz wrote: > El día Friday, October 25, 2013 a las 06:59:56AM -0600, Warren Block escribió: > >> On Fri, 25 Oct 2013, Matthias Apitz wrote: >> >>> I'm using dump(8) for backups. Is there some tool to check the integrity >>> of the produced dump? A 'restore -t -f ....' seems to look only into the >>> header of the dump and not reading the full file... >>> >>> Ideally would be a binary comparisation of the files in the dump with >>> the original files on disk, ofc directly after the dump done in single >>> user mode. >> >> It may be possible to use mtree(8)'s cksum to compare the original files >> with those in the backup. > > Sorry for not beeing precise enough: I did not want to restore the files > to disk, just reading the dump and comparing with the original. Would be > nice if restore would have an option for this; -N is not strong enough I > think. I was thinking the output of restore could be piped into mtree, and that could be compared to the mtree output on the actual filesystem. --3512871622-1514343918-1382722704=:70337--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1310251135520.70337>