[lkml]   [2003]   [Dec]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] 2.6.0 - Watchdog patches (BK consistency checks)
On Wed, Dec 31 at 10:01, Ed Tomlinson wrote:
>I am not saying I do not want do have consistency checks done. I do want
>to control _when_ and how often they run

I don't see how it would be valid to not do a consistency check after
every network operation, which is what it does now...

Every time you are modifying your archive from a remote source, the
consistency check makes sure you don't have corruption in the transfer
that was previously undetected, or corruption in the underlying
archive which is about to accept the changes. Since you can only do
network updates at a time when your own archive is in a "checked-in"
state, if the network update fails or detects corruption, you can
clone what you'd already checked in to a new location and recover
trivially. The most work you can lose is the delta between your last
changeset and the current one, assuming you keep some sort of backups

What exactly would you do if you'd been working "offline" for 3 weeks,
went to sync, and it said that your archive was corrupted? Or should
it try to merge into a corrupt archive anyway? Should that archive
that was corrupt, and then had possibly good changes layered on top of
it, be valid for attempting a clone?

I think that limiting the consistency checking could be like opening a
*very big* can of worms.

Eric D. Mudama

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:59    [W:0.055 / U:1.260 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site