[prev in list] [next in list] [prev in thread] [next in thread] 

List:       evms-devel
Subject:    Re: [Evms-devel] [ANNOUNCE] Highpoint-Tech Plugin 0.0.1 for EVMS
From:       Wilfried Weissmann <Wilfried.Weissmann () gmx ! at>
Date:       2004-03-21 14:03:46
Message-ID: 405DA0C2.7030305 () gmx ! at
[Download RAW message or body]

Simon Farnsworth wrote:
> OK. Have been playing more now that the excitement of actually running 2.6 has 
> worn off.
> 
> Every second attempt to activate EVMS with this plugin installed fails to 
> detect the HPT RAID; the following section of log shows the problem:

Hmm, right I have to detect if a volume as already been activated. I 
will look how the other plugins are handeling this situation...

> 
> Mar 20 13:26:29 lister Engine: run_command_v4: Enter.
> Mar 20 13:26:29 lister Engine: run_command_v4: Issuing DM ioctl 3 for device 
> hptraid0p.
> Mar 20 13:26:29 lister Engine: run_command_v4: Error returned from ioctl call: 
> 16: Device or resource busy.
> Mar 20 13:26:29 lister Engine: run_command_v4: Exit.  Return value is 16.
> Mar 20 13:26:29 lister Engine: put_ioctl_packet: Enter.
> Mar 20 13:26:29 lister Engine: put_ioctl_packet: Exit.
> Mar 20 13:26:29 lister Engine: dm_create_v4: Exit.  Return value is 16.
> Mar 20 13:26:29 lister Engine: dm_activate_v4: Exit.  Return value is 16.
> Mar 20 13:26:29 lister Engine: deallocate_target_type_params: Enter.
> Mar 20 13:26:29 lister Engine: put_string: Enter.
> Mar 20 13:26:29 lister Engine: put_string: Exit.
> Mar 20 13:26:29 lister Engine: deallocate_target_type_params: Exit.
> Mar 20 13:26:29 lister Engine: dm_activate: Exit.  Return value is 16.
> Mar 20 13:26:29 lister BIOSDskMgr: hptRAIDInit: Failed to activate hptraid0p.
> Mar 20 13:26:29 lister Engine: engine_free_logical_disk: Enter.
> 
> Because I use an initrd, I do discovery twice; once to find my root volume to 
> get on the road, and once after the system has mounted my real root to fill 
> in the evms devices on disc.
> 
> I'm working around by running evms_activate twice once my real root is found.
> 
> It looks like the plugin needs to detect if it's already got EVMS objects 
> created before, and do something differently. I'm not quite sure what to do; 
> should it transfer over the old objects, or should it delete and recreate 
> them?
> 
> The problem with delete and recreate is what to do if there are users of them 
> already; how do we force the kernel to drop the devices?
> 
> The problem with transfer over is what happens if the device configuration has 
> changed. I think this is unlikely, so I'm leaning towards transferring over 
> existing devices.

It would be great to discover configuration changes and apply them to 
the device (if it is not used). I guess the MD plugin does this already 
so we are not breaking new grounds here. What I need is to find a way to 
  store the former configuration in a way that I can recall and compare 
it when evms_activate is rerun.

Thanks,
Wilfried


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Evms-devel mailing list
Evms-devel@lists.sourceforge.net
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel
[prev in list] [next in list] [prev in thread] [next in thread]