From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] caught by replica
Date: Tue, 18 Mar 2003 19:21:25 +0100 [thread overview]
Message-ID: <f467c7b4c783bfeecc757d5dfa7c179b@plan9.escet.urjc.es> (raw)
In-Reply-To: <8842bdd8e931605322b284d9f00a61f3@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
It could be I was running a pull -c for a subset of the files.
Do you know the effect of a network disconnection while doing that?
Could it affect the status of files not being pulled -c that are
in the same batch?
After thinking it twice, I think I agree that it cannot happen,
so I think it all had to be a mistake on my side, sic.
thanks a lot
[-- Attachment #2: Type: message/rfc822, Size: 1930 bytes --]
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] caught by replica
Date: Tue, 18 Mar 2003 13:14:47 -0500
Message-ID: <8842bdd8e931605322b284d9f00a61f3@plan9.bell-labs.com>
> It seems that the reason why we're not getting the scheduler fix is
> that apparently we already have it, sic.
>
> What happen was that in a pull we got a disconnection from the network.
> It seems that the files got added to the log, and not to the data base.
> Since plan9.time was updated, replica is no longer pulling them.
I can't figure out how that could happen.
If you got disconnected then the copy operations
should have failed. If they fail, then the time is
not updated.
Are you sure you didn't run pull -c to ignore the changes?
prev parent reply other threads:[~2003-03-18 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 18:04 Fco.J.Ballesteros
2003-03-18 18:14 ` Russ Cox
2003-03-18 18:21 ` Fco.J.Ballesteros [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=f467c7b4c783bfeecc757d5dfa7c179b@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).