2011/7/16 Gregory Youngblood :
>> Which means: forget about using openindiana instead of Nexenta for backups.
>
> It would be interesting to find what the difference is between them.
I'm re-trying with OI 148 (stable) and it seems not to have this
problems (at least it's been going for a few hours
On Jul 15, 2011, at 1:12 PM, Frank Van Damme wrote:
> 2011/7/15 Frank Van Damme :
>> It's not too flat. Actually I managed to rsync the same dataset to
>> Nexenta (well, I also had a failure, but later in the copy and not
>> consistant) which has an rsync version 3.0.7 while OI has 3.0.6 - I
>> no
2011/7/15 Frank Van Damme :
> It's not too flat. Actually I managed to rsync the same dataset to
> Nexenta (well, I also had a failure, but later in the copy and not
> consistant) which has an rsync version 3.0.7 while OI has 3.0.6 - I
> now compiled 3.0.8 on OI so we'll see if 2 minor versions wil
2011/7/15 Richard L. Hamilton :
> I've seen that happen to other people too.
>
> If your directory is really "flat" (millions of files in one directory, no
> subdirectories), you're out of luck unless you rearrange it. If your
> directory is not flat, then break up the job into multiple rsyncs t
I've seen that happen to other people too.
If your directory is really "flat" (millions of files in one directory, no
subdirectories), you're out of luck unless you rearrange it. If your directory
is not flat, then break up the job into multiple rsyncs that don't overlap. As
I recall, their s
I have a problem when rsyncing a directory with a *lot* of files in it
to an openindiana system (it's an 151-dev installation). It failed when
I issued the command on the sender side (linux box), this is the error
when you try the command on the receiver side:
ERROR: out of memory in flist_expand
