Re: vinum broken by devstat changes?
On Tue, 25 Mar 2003, Kenneth D. Merry wrote: KDMOn Wed, Mar 26, 2003 at 11:06:52 +1030, Greg 'groggy' Lehey wrote: KDM On Tuesday, 25 March 2003 at 18:44:03 +0100, Hartmut Brandt wrote: KDM KDM Hi, KDM KDM when calling 'vinum start' it responds with KDM KDM usage: read drive [drive ...] KDM KDM from looking at the code, it appears that it cannot find the disk drives KDM to read the configuration from. KDM KDM vinum read da0 da1 KDM KDM just works. KDM KDM So what's the problem? (kernel and user land from today) KDM KDM Check vinum(8), function vinum_start (in KDM /usr/src/sbin/vinum/commands.c). It's possible that the changes have KDM broken some of the tests, probably of stat-device_type. I can't KDM think it's too difficult to fix. KDM KDMdisk_create() now creates the devstat entry for disks, but defaults KDMeverything to be a direct access (with no interface type). KDM KDMI've got patches in progress to fix that, but it looks like things should KDMwork with the current state of affairs. KDM KDMHave you rebuilt world? That was just a fresh world and kernel. It took me some time to get it up again - the vinum partition holds the ports for my other machines. I just have no time to work on this... KDMIt looks like vinum(8) doesn't include a call to devstat_checkversion(), so KDMit's possible you've got a version mismatch but no way to know it. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
vinum broken by devstat changes?
Hi, when calling 'vinum start' it responds with usage: read drive [drive ...] from looking at the code, it appears that it cannot find the disk drives to read the configuration from. vinum read da0 da1 just works. So what's the problem? (kernel and user land from today) harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private [EMAIL PROTECTED], [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vinum broken by devstat changes?
On Tuesday, 25 March 2003 at 18:44:03 +0100, Hartmut Brandt wrote: Hi, when calling 'vinum start' it responds with usage: read drive [drive ...] from looking at the code, it appears that it cannot find the disk drives to read the configuration from. vinum read da0 da1 just works. So what's the problem? (kernel and user land from today) Check vinum(8), function vinum_start (in /usr/src/sbin/vinum/commands.c). It's possible that the changes have broken some of the tests, probably of stat-device_type. I can't think it's too difficult to fix. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
[Re: vinum broken by devstat changes?
On Wed, Mar 26, 2003 at 11:06:52 +1030, Greg 'groggy' Lehey wrote: On Tuesday, 25 March 2003 at 18:44:03 +0100, Hartmut Brandt wrote: Hi, when calling 'vinum start' it responds with usage: read drive [drive ...] from looking at the code, it appears that it cannot find the disk drives to read the configuration from. vinum read da0 da1 just works. So what's the problem? (kernel and user land from today) Check vinum(8), function vinum_start (in /usr/src/sbin/vinum/commands.c). It's possible that the changes have broken some of the tests, probably of stat-device_type. I can't think it's too difficult to fix. disk_create() now creates the devstat entry for disks, but defaults everything to be a direct access (with no interface type). I've got patches in progress to fix that, but it looks like things should work with the current state of affairs. Have you rebuilt world? It looks like vinum(8) doesn't include a call to devstat_checkversion(), so it's possible you've got a version mismatch but no way to know it. Ken -- Kenneth Merry [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
