Date: Sun, 9 Feb 2003 10:35:43 +1030 From: Greg 'groggy' Lehey <grog@FreeBSD.org> To: Michael Reifenberger <root@nihil.reifenberger.com> Cc: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>, freebsd-current@freebsd.org Subject: Re: vinum start & -current doesn't work as expected Message-ID: <20030209000543.GM99377@wantadilla.lemis.com> In-Reply-To: <20030208181905.Y664@nihil.reifenberger.com> References: <20030207105857.T2514@nihil.reifenberger.com> <200302072056.h17KujgW073866@uriah.heep.sax.de> <20030207225249.O33219@nihil.reifenberger.com> <20030208181905.Y664@nihil.reifenberger.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--um2V5WpqCyd73IVb
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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 me whether this gives different results.
>
> Bad things happen when doing the above.
> Vinum forgets his configuration on loading.
>
> I did the following:
> 1.) Configure a volume as:
> drive d0 device /dev/da0s1a
> drive d1 device /dev/da1s1a
>
> volume ablage setupstate
> plex name ablage.p0 org concat
> sd name ablage.p0.s0 drive d0 size 0b
> plex name ablage.p1 org concat
> sd name ablage.p1.s0 drive d1 size 0b
>
> 2.) Reboot
Why? What was there before?
> 3.) During startup I get now:
> ...
> (normal looking messages)
> ...
>
> 5.) ls -l /dev/vinum
> total 0
> crw------- 1 root wheel 91, 0x40000001 8 Feb 18:15 control
> crw------- 1 root wheel 91, 0x40000000 8 Feb 18:15 controld
OK, no volumes.
> 6.) Taking a look at /dev/da0s1a gives something like:
> ...
> ^@^@^@^@^@^@^@^@volume ablage state up
> plex name ablage.p0 state up org concat vol ablage
> plex name ablage.p1 state up org concat vol ablage
> sd name ablage.p0.s0 drive d0 plex ablage.p0 len 398296697s driveoffset 265s
> state up plexoffset 0s
> sd name ablage.p1.s0 drive d1 plex ablage.p1 len 398296697s driveoffset 265s
> state up plexoffset 0s
> ...
Where does that start? What does vinum dumpconfig say?
> 7.) Maybe not to late, doing a `vinum read /dev/da0s1 /dev/da1s1; vinum l`:
> ... nada ...
No, it's tried that already.
> 8.) Taking a look at /dev/da0s1a gives now something like:
> ...
> ^@^@^@^@IN
> VINO^@^@^@^A^@nihil^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@d0^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
Hmm. So it seems it has found the slices.
> 9.) `cd /etc/vinum; vinum create firewire.conf`:
> 4 drives:
4?
> D d1 State: up /dev/da1s1a A: 0/194480 MB (0%)
> D d0 State: up /dev/da0s1a A: 0/194480 MB (0%)
Hmm.
> 10.) Goto 2.)
Why? Was the data accessible?
I've never seen anything like this. Try the following:
1. After booting, at step 6 above, run vinum dumpconfig -v.
2. Do a vinum stop, then vinum start.
3. See what things look like (l, dumpconfig)
4. If it's still not working, do a vinum start and vinum create
<thatfile>
5. See what things look like (l, dumpconfig).
Greg
--
See complete headers for address and phone numbers
--um2V5WpqCyd73IVb
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)
iD8DBQE+RZtXIubykFB6QiMRAgQJAKCt2e0VyeShIxdL9neNEDr4cOiyywCeJrjk
yhnxNV6ADZo4Q1e56y2iEk0=
=vLGM
-----END PGP SIGNATURE-----
--um2V5WpqCyd73IVb--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030209000543.GM99377>