From: 7v5w7go9ub0o <7v5w7go9ub0o@gmail.com>
To: for list <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Re: Fast checksumming of whole partitions
Date: Sun, 06 Jun 2010 19:06:16 -0400 [thread overview]
Message-ID: <4C0C29E8.8010008@gmail.com> (raw)
In-Reply-To: <4C0C08F0.1060007@alyf.net>
On 06/06/10 16:45, Andrea Conti wrote:
>>> 1- if the root partition is [part of] what you're copying, you
>>> *must* mount it read-only (mount -o ro /dev/sdc /work)
>>
>> Not from my experience; I simply mount, exec, and go - Works fine
>
> Let's say you are 50% done copying a partition, when something
> writes to it. If the write only affects the first half, which has
> alredy been copied, the target will consistently reflect the "old"
> state; if on the other hand the write only affects the second half,
> which has not been copied yet, the target will consistently reflect
> the "new" state. The problem is that with any write affecting both
> halves your copy will contain a mix of the two states and thus will
> be inconsistent.
Should that happen, I certainly agree that the copies would be
inconsistent... but I don't know what would cause the live OS to write
anything to it (other than update the last access date/time - which
occurs early on).
At any rate, should that happen, the hashes would disagree and I'd
reject the copy. Thus far the whole-disk hashes have always agreed
Now, if this were a forensic investigation, then you're absolutely right
- even updating an access time would be unacceptable; regardless that
the changed source and copied destination hash the same.
prev parent reply other threads:[~2010-06-06 23:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 6:39 [gentoo-user] Fast checksumming of whole partitions meino.cramer
2010-06-05 7:19 ` [gentoo-user] " Nikos Chantziaras
2010-06-07 15:48 ` meino.cramer
2010-06-07 17:10 ` walt
2010-06-07 18:47 ` meino.cramer
2010-06-07 17:31 ` Andrea Conti
2010-06-07 18:54 ` meino.cramer
2010-06-11 22:41 ` Mick
2010-06-05 7:32 ` [gentoo-user] " Andrea Conti
2010-06-05 17:39 ` [gentoo-user] " 7v5w7go9ub0o
2010-06-05 19:23 ` meino.cramer
2010-06-05 20:11 ` Manuel Klemenz
2010-06-06 19:02 ` 7v5w7go9ub0o
2010-06-06 19:47 ` Joerg Schilling
2010-06-06 22:43 ` 7v5w7go9ub0o
2010-06-06 23:12 ` Joerg Schilling
2010-06-06 22:46 ` Neil Bothwick
2010-06-07 1:04 ` 7v5w7go9ub0o
2010-06-05 23:44 ` 7v5w7go9ub0o
2010-06-06 10:19 ` Andrea Conti
2010-06-06 16:55 ` Mick
2010-06-06 18:55 ` 7v5w7go9ub0o
2010-06-06 20:00 ` Mick
2010-06-06 20:45 ` Andrea Conti
2010-06-06 23:06 ` 7v5w7go9ub0o [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=4C0C29E8.8010008@gmail.com \
--to=7v5w7go9ub0o@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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