linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: urgrue <urgrue@bulbous.org>
To: Prosenjit Kundu <pkundu.kernel@gmail.com>
Cc: "hansel@hansel.mnstate.edu" <hansel@hansel.mnstate.edu>,
	linux-admin@vger.kernel.org
Subject: Re: "resume" cp/mv
Date: Tue, 07 Feb 2006 17:50:16 +0200	[thread overview]
Message-ID: <43E8C1B8.1070601@bulbous.org> (raw)
In-Reply-To: <42c5b570602062328k353945f7hc53d1448e939e718@mail.gmail.com>

rsync certainly helps with large directories, so thats at least a 
partial solution, but it doesnt resume an interrupted transfer of an 
individual file, does it?

Prosenjit Kundu wrote:
> I have also used 'cp -u'.......but rsync is better match for it.
> 
> PK
> 
> On 2/6/06, hansel@hansel.mnstate.edu <hansel@hansel.mnstate.edu> wrote:
>> I've used 'cp -u' for a similar problem (where I really am updating
>> parallel --backup-- directories of huge graphics files).
>>
>> Mark Hansel
>>
>> On Mon, 6 Feb 2006, urgrue wrote:
>>
>>> Anyone know of any trick to make mv/cp support some form of crash-recovery?
>>>
>>> The problem is, if I'm moving a huge directory/file, and the transfer
>>> fails, there is absolutely no way to continue where I left off. This is
>>> awfully primitive.
>>>
>>> The only way I can think of is to zssh into my own localhost and use
>>> rz/sz, or the same via ftp, but this seems like a pathetic kludge, and
>>> even those dont work very well with large directories full of files.
>>> -
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> 
> --
> Regards,
> Prosenjit Kundu
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2006-02-07 15:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 15:28 "resume" cp/mv urgrue
2006-02-06 15:40 ` Thornton Prime
2006-02-06 15:42 ` Tim Walberg
2006-02-06 15:46 ` Scott Taylor
2006-02-06 15:57 ` hansel
2006-02-07  7:28   ` Prosenjit Kundu
2006-02-07 15:50     ` urgrue [this message]
2006-02-08  6:07       ` Jeff Woods

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=43E8C1B8.1070601@bulbous.org \
    --to=urgrue@bulbous.org \
    --cc=hansel@hansel.mnstate.edu \
    --cc=linux-admin@vger.kernel.org \
    --cc=pkundu.kernel@gmail.com \
    /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).