From: Roman Mamedov <roman@rm.pp.ru>
To: Robin Hill <robin@robinhill.me.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: integrity verification on raid-5?
Date: Sat, 18 Dec 2010 15:30:35 +0500 [thread overview]
Message-ID: <20101218153035.5c134e06@natsu> (raw)
In-Reply-To: <20101217212436.GA11425@cthulhu.home.robinhill.me.uk>
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
On Fri, 17 Dec 2010 21:24:37 +0000
Robin Hill <robin@robinhill.me.uk> wrote:
> Currently, there's no easy way to find out what file(s) are affected by
> the mismatches though.
That's why it is also a good idea to keep around file-level checksums in each
directory (especially if you store a lot of files which shouldn't ever change,
like audio or video collections), using CFV - http://cfv.sourceforge.net/
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-12-18 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 21:08 integrity verification on raid-5? Patrick H.
2010-12-17 21:17 ` Neil Brown
2010-12-17 21:25 ` Patrick H.
2010-12-17 21:24 ` Robin Hill
2010-12-17 22:20 ` Patrick H.
2010-12-18 10:25 ` Piergiorgio Sartor
2010-12-18 10:30 ` Roman Mamedov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101218153035.5c134e06@natsu \
--to=roman@rm.pp.ru \
--cc=linux-raid@vger.kernel.org \
--cc=robin@robinhill.me.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox