Vmalloc problem wihle initializing File-IO

[the_nipper]

Does this happen when you create a small FILE IO w/ init. lets say 10GB? Also update to 3518 before you start the Auto Failover. Send in the logs to support@open-e.com maybe something else could be happening that engineers can find out. Show the screen shot as well.

No, 10 GB succeed. But, as I said, with an identical system, 3328 GB succeeded as well before.

As I found out now, replication flag can be enabled on File-I/O volumes after creation. The GUI is misleading a bit: when I choose 'modify lv...' , the replication-checkbox is grayed, but can be activated by deselecting the default initializing checkbox. I'll try to create the volume without replication, and add the replication thereafter.

What about Auto failover and new release? These systems are yet working with some other volumes. I would not be great to disconnect and reboot...

Best,

Robert

[the_nipper]

As I found out now, replication flag can be enabled on File-I/O volumes after creation. The GUI is misleading a bit: when I choose 'modify lv...' , the replication-checkbox is grayed, but can be activated by deselecting the default initializing checkbox. I'll try to create the volume without replication, and add the replication thereafter.

No effect. When trying to enable the replication flag:

2009/07/30 11:25:49 Unable to initialize volume replication for the following logical volume: lvdaten15k00. Please increase the Vmalloc size in console tools: CTRL-ALT-W --> Tuning options --> Vmalloc size



Robert

[the_nipper]

After a reboot, I can set the replication flag now.

Unconvincingly, for a central backend component... :-( Mind that this system provided no operational service than one NFS-share before => no load on a system with many CPUs and cores and 16 GB of RAM.

Regards,

Robert