For my part, I'd at least like to see an error message logged. Would've saved us all some time here.
On 9/12/07, Lon Hohberger <[EMAIL PROTECTED]> wrote: > > On Wed, Sep 12, 2007 at 07:05:43AM +0200, Alain Richard wrote: > > > > Le 4 sept. 07 à 23:13, Lon Hohberger a écrit : > > > > >On Fri, Aug 31, 2007 at 12:46:50PM +0200, Alain RICHARD wrote: > > >>Perhaps a better error reporting is needed in qdiskd to shows that we > > >>have hit this problem. Also using a generic name like "qdisk device" > > >>when qdiskd is registering its node to cman is a better approach. > > > > > >What about using the label instead of the device name, and restricting > > >the label to 16 chars when advertising to cman? > > > Because when using multipath devices (for example a two paths > > device), all the paths and the multi-path device are recognized as > > having the same label, so qdisk fails to get the good device (the > > multi-path device). > > I meant implementation-wise, using the label instead of the device name > to solve or work around the 16 character limit when talking to CMAN... > > -- > Lon Hohberger - Software Engineer - Red Hat, Inc. > > -- > Linux-cluster mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/linux-cluster > -- Dave Costakos mailto:[EMAIL PROTECTED]
-- Linux-cluster mailing list [email protected] https://www.redhat.com/mailman/listinfo/linux-cluster
