Re: [Evms-devel] (no subject)

[Kevin C. <co...@us...>]

Don,

My first suggestion would be to make sure the LVM region manager is turned on 
in the EVMS menu in the kernel configuration.

If that is turned on, the next thing I would suggest is to run this test 
again (all the way through commit), and then run the "dmesg" command to see 
if there are any interesting kernel messages from EVMS.

My gut feeling is that something in the kernel discovery process is not 
finding the LVM volume correctly.

Are there any nodes at all in /dev/evms (block_device in particular)?

-Kevin

On Friday 14 December 2001 16:45, Donald W Watson wrote:
> Hi,
>
> I am using evms-0.2.4 with the 2.4.16 kernel.
>
> Without devfs, using evmsgui and the LVM region manager, I have created
> a segment, a container, a region, and a volume.  After  committing the
> changes,
> the volume node (which should be in /dev/evms) does not exist.
>
> I have debugged this to the extent that I have discovered that in the call
> to
> ForEachItem() in evms_update_evms_dev_tree(), VolumeDataList->ItemCount
> is zero, thus causing ForEachItem() to fail to call ensure_dev_node().
>
> An additional problem is that Actions->Commit can be called repeatedly
> without the gui recognizing that a commit has been successfully performed.
>
> As Ram said, the node also fails to appear while using devfs.  The commit
> problem outlined in the previous paragraph does not exist while using
> devfs.
>
>      Thanks,
>           Don
>