public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Use split to break up a 10GB file binary?
Date: Mon, 20 Jun 2011 09:30:02 -0700	[thread overview]
Message-ID: <BANLkTi=jswbTVXy4xKfj8OJmh7vvAP+Bwg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=3Ai7xndu+sNVCxLPKD=z8qE5vJA@mail.gmail.com>

On Mon, Jun 20, 2011 at 9:21 AM, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> On Mon, Jun 20, 2011 at 10:25 AM, Mark Knecht <markknecht@gmail.com> wrote:
>> Hi,
>>   Is split an appropriate program to use to break a single 10GB file
>> into 100 100MB files to transfer over the net using rsync, and then
>> use cat to reassemble?
>
> I think it should work just fine. I've split huge files into huge
> chunks and never had any issues.
>
>>   Is there some better way to do this?
>
> I wonder if splitting is even necessary; rsync will analyze the file
> and only transmit the differences, right?. So I'd think that even if
> the transfer fails, a retry would pick up where it left off (assuming
> rsync keeps the failed copy).
>
> Also check out net-misc/unison. It seems to be designed for just this
> sort of thing.

I'll check them out Paul. Thanks for the extra ideas.

I just tried it as an experiment between two machines here. Using
split I broke the 10GB file into 100MB pieces, used rsync to get the
pieces to my laptop, and then used cat to reassemble. The size of the
results compares to the byte so that looks good.

I was unsure whether rsync would restart where it left off or whether
it would start over from the beginning. It's one huge file so it would
be painful if it did the latter. This way I know my risk is at most
100MB, or maybe 20MB if I break the original up into smaller pieces.

Cheers,
Mark



  reply	other threads:[~2011-06-20 17:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 15:25 [gentoo-user] Use split to break up a 10GB file binary? Mark Knecht
2011-06-20 16:21 ` Paul Hartman
2011-06-20 16:30   ` Mark Knecht [this message]
2011-06-20 17:51     ` Michael Hampicke
2011-06-20 17:48   ` Allan Gottlieb
2011-06-20 18:20     ` Mark Knecht
2011-06-21  7:08   ` [gentoo-user] " Francesco Talamona
2011-06-20 19:17 ` [gentoo-user] " Nils Larsson
2011-06-20 19:29   ` Mark Knecht
2011-06-20 20:51 ` Walter Dnes
2011-06-20 21:06   ` Mark Knecht
2011-06-20 21:58     ` Mick
2011-06-20 21:46 ` Indi
2011-06-21  0:28   ` Mark Knecht
2011-06-21 10:41     ` Indi
2011-06-21 15:11     ` Peter Humphrey
2011-06-21 15:20       ` Dale
2011-06-21 15:36       ` Mark Knecht
2011-06-21 17:00         ` Peter Humphrey

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='BANLkTi=jswbTVXy4xKfj8OJmh7vvAP+Bwg@mail.gmail.com' \
    --to=markknecht@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