Just tried it with 1GB metadata file, and that works and finishes quickly. 
Bigger sizes just cause rdsinit to go away forever at 100% CPU without 
ever writing the file. Bug?

Gordan

On Wed, 30 Jan 2008, coda_at_bobich.net wrote:

> On a related note vice-setup seems to take a rather long time when it gets to 
> this point:
>
> Proceed, and wipe out old data? [y/n] y
>
> LOG file has been initialized!
>
> Rdsinit will initialize data and log.
> This takes a while.
> rvm_initialize succeeded.
> Going to initialize data file to zero, could take awhile.
> done.
>
> ...... and then it stops. This process is running at 100% CPU:
>
> /usr/sbin/rdsinit -f /usr/coda/data/log /usr/coda/data/data 4294967296 
> 0x50000000 4293853184 1048576 80 64
>
> It doesn't appear to be griding onto the disk, and the /usr/coda/data/data is 
> 0 bytes.
>
> Would I be correct in guessing this is not what is supposed to happen?
>
> Gordan
>
> On Wed, 30 Jan 2008, coda_at_bobich.net wrote:
>
>> Is there an official limit on RVM log and metadata file sizes? I set my log 
>> size to 2GB in order to be able to handle files up to 2GB. Ideally, I 
>> wanted to be able to handle a FS up to 0.5TB, so I wanted to make a 
>> metadata file of about 16GB. The biggest I've managed to get to work is 
>> 4GB, otherwise things fail with an error. Does this sound about right?
>> 
>> I am using a file, rather than a partition. Am I correct in guessing that 
>> mmapping the file only maps it into virtual memory without actually 
>> requiring that much RAM+swap in the system (unlike when using a partition)?
>> 
>> On a related note, are any of these limits (file/log/metadata) architecture 
>> dependant? If so are there any issues with having an x86-64 and an IA32 
>> node in the same replicated cluster?
>
>