I've got the current system running on software RAID1, and I've got plenty of (unpartitioned) diskspace left. The System was set up 2 days ago, to everything is really current.
I used evmsn and followed the gentoo evms wiki, everything seemed to work fine, till it came to quit & save, then I encountered the following error:
Engine: FSIM plug-in Ext2/3 returned error code 1 when called to mkfs volume /dev/evms/condor
I tried this several times (different file-systems, rebooted in between, ..). Then I checked the logfile /var/log/evms-engine.log and found loads of error messages likeSave failed. No such device.
I checked /dev/emvs/ to find .. not much. the only devices/files there areNov 30 18:24:48 Xen-Master _5_ Engine: is_object_change_pending: Change pending: Object lvm2/raid1md1/condor needs to be activated.
Nov 30 18:24:48 Xen-Master _5_ Engine: is_object_change_pending: Change pending: Object md/md1 needs to be activated.
Nov 30 18:24:48 Xen-Master _5_ Engine: is_volume_change_pending: Change pending: Volume /dev/evms/condor needs to be activated.
Nov 30 18:24:48 Xen-Master _5_ Engine: is_volume_change_pending: Change pending: Volume /dev/evms/condor needs to have the Ext2/3 file system put on it.
Nov 30 18:24:48 Xen-Master _2_ Engine: run_command_v4: Error returned from ioctl call: 22: Invalid argument.
Nov 30 18:24:48 Xen-Master _3_ Engine: activate_object: Error code 19 activating object sda7: No such device
Nov 30 18:24:48 Xen-Master _2_ Engine: run_command_v4: Error returned from ioctl call: 22: Invalid argument.
Nov 30 18:24:48 Xen-Master _3_ Engine: activate_object: Error code 19 activating object sdb7: No such device
Nov 30 18:24:48 Xen-Master _3_ Engine: activate_object: Error code 19 activating object md/md1: No such device
Nov 30 18:24:48 Xen-Master _3_ Engine: activate_object: Error code 19 activating object md/md1: No such device
Nov 30 18:24:48 Xen-Master _3_ Engine: activate: Error code 19 activating object lvm2/raid1md1/condor: No such device
Nov 30 18:24:48 Xen-Master _2_ Engine: run_command_v4: Error returned from ioctl call: 22: Invalid argument.
Nov 30 18:24:48 Xen-Master _3_ Engine: activate_object: Error code 19 activating object sda7: No such device
Nov 30 18:24:48 Xen-Master _2_ Engine: run_command_v4: Error returned from ioctl call: 22: Invalid argument.
Nov 30 18:24:48 Xen-Master _3_ Engine: activate_object: Error code 19 activating object sdb7: No such device
Nov 30 18:24:48 Xen-Master _3_ Engine: activate: Error code 19 activating object md/md1: No such device
Nov 30 18:24:48 Xen-Master _3_ Engine: evms_rediscover: activate() returned error code 19: No such device
Nov 30 18:24:48 Xen-Master _0_ Engine: engine_user_message: Message is: Engine: FSIM plug-in Ext2/3 returned error code 1 when called to mkfs on volume /dev/evms/condor
/dev/evms/dm/control
/dev/evms/.nodes/sda
/dev/evms/.nodes/sdb
/dev/evms/.nodes/md/md0
/dev/evms/md/md0
Then I tried it like described in this thread: didn't help either, just booting takes a few minutes longer with about 100times
There must be hundreds of people out there with gentoo and evms running .. please let me know what I missed, but I've spent about 5 hours to this now and got no clue where else to look for helpNov 30 18:24:48 Xen-Master kernel: device-mapper: dm-linear: Device lookup failed
Nov 30 18:24:48 Xen-Master kernel: device-mapper: error adding target to table
* ElCondor confused and a little desperate pasa *


