Re: vinum start -current doesn't work as expected

2003-02-08 Thread Michael Reifenberger
On Fri, 7 Feb 2003, Michael Reifenberger wrote: ... As a workaround, you can try setting vinum_load=YES vinum.autostart=YES in your /boot/loader.conf, /and/ remove the start_vinum line from rc.conf. Please tell me whether this gives different results. Bad things happen when doing

Re: vinum start -current doesn't work as expected

2003-02-08 Thread Joerg Wunsch
As Greg 'groggy' Lehey wrote: I guess it's time to dump the old vinum start code from vinum(8) completely, and use the in-kernel scan now. This sounds like a good idea. Not after looking a bit closer. ;-) The only difference ist that the userland vinum start uses devstat, while the

Re: vinum start -current doesn't work as expected

2003-02-08 Thread Greg 'groggy' Lehey
On Saturday, 8 February 2003 at 21:42:27 +0100, Joerg Wunsch wrote: As Greg 'groggy' Lehey wrote: I guess it's time to dump the old vinum start code from vinum(8) completely, and use the in-kernel scan now. This sounds like a good idea. Not after looking a bit closer. ;-) The only

Re: vinum start -current doesn't work as expected

2003-02-08 Thread Greg 'groggy' Lehey
On Saturday, 8 February 2003 at 18:34:04 +0100, Michael Reifenberger wrote: On Fri, 7 Feb 2003, Michael Reifenberger wrote: ... As a workaround, you can try setting vinum_load=YES vinum.autostart=YES in your /boot/loader.conf, /and/ remove the start_vinum line from rc.conf. Please tell

vinum start -current doesn't work as expected

2003-02-07 Thread Michael Reifenberger
Hi, me using -current as of today. I have two firewire disks as: ... da0 at sbp0 bus 0 target 0 lun 0 da0: Oxford S OXFORD IDE Devic 4133 Fixed Simplified Direct Access SCSI-4 device da0: 50.000MB/s transfers da0: 194481MB (398297088 512 byte sectors: 255H 63S/T 24792C) da1 at sbp0 bus 0 target 1

Re: vinum start -current doesn't work as expected

2003-02-07 Thread Joerg Wunsch
Michael Reifenberger [EMAIL PROTECTED] wrote: After reboot, a `vinum start` gives me: ** no drives found: No such file or directory Do you perchance have a kernel without GEOM? vinum start has now been changed to use sysctl kern.disks as the list of devices to scan. Hmm. No, maybe not...

Re: vinum start -current doesn't work as expected

2003-02-07 Thread Michael Reifenberger
On Fri, 7 Feb 2003, Joerg Wunsch wrote: Date: Fri, 7 Feb 2003 21:56:45 +0100 (MET) From: Joerg Wunsch [EMAIL PROTECTED] Reply-To: Joerg Wunsch [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: Michael Reifenberger [EMAIL PROTECTED] Subject: Re: vinum start -current doesn't work as expected

Re: vinum start -current doesn't work as expected

2003-02-07 Thread Joerg Wunsch
As Michael Reifenberger wrote: What does your sysctl kern.disks say? (nihil)(root) # sysctl -a kern.disks kern.disks: da1 da0 ad1 ad0 That's OK. I guess it's time to dump the old vinum start code from vinum(8) completely, and use the in-kernel scan now. -- cheers, Jorg

Re: vinum start -current doesn't work as expected

2003-02-07 Thread Greg 'groggy' Lehey
On Saturday, 8 February 2003 at 0:00:45 +0100, Joerg Wunsch wrote: As Michael Reifenberger wrote: What does your sysctl kern.disks say? (nihil)(root) # sysctl -a kern.disks kern.disks: da1 da0 ad1 ad0 That's OK. I guess it's time to dump the old vinum start code from vinum(8)