Re: vinum problems with todays current
Greg 'groggy' Lehey wrote:
On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
Can you try this patch:
...
I noticed I had an older version of spec_vnops.c (1.205), so I
cvsupped again and build kernel, this gave me the same msgbuf error,
but with different values. Then I applied your patch and the error
messgae disapeared, but still my vinum doesn't come up.
Can I assume that this is related to GEOM, and not to Vinum?
Greg
--
See complete headers for address and phone numbers
After investigating a little further today, I found the config info on
the drives to be mangled.
--
# rm -f log
# for i in /dev/da0s1h /dev/da1s1h /dev/da2s1h /dev/da3s1h; do
(dd if=$i skip=8 count=6|tr -d '\000-\011\200-\377'; echo) log
done
# cat log
IN VINOx-server.debank.tvbCc3??Z${m5?
IN VINOx-server.debank.tvaC3?WPZ${m5?
--
I guess the drives can't be started again unless I have the parameters
which I used during install (please say I'm wrong).
Rob Evers
--
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum problems with todays current
On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote: Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Rob writes: Hi all, After cvs'upping (about 12 hours ago) and building world/kernel vinum stopped working. It does show my two disks but nothing more. I also get an error message right after the bootloader: Can you try this patch: ... I noticed I had an older version of spec_vnops.c (1.205), so I cvsupped again and build kernel, this gave me the same msgbuf error, but with different values. Then I applied your patch and the error messgae disapeared, but still my vinum doesn't come up. Can I assume that this is related to GEOM, and not to Vinum? Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: vinum problems with todays current
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
Can you try this patch:
Index: spec_vnops.c
===
RCS file: /home/ncvs/src/sys/fs/specfs/spec_vnops.c,v
retrieving revision 1.206
diff -u -r1.206 spec_vnops.c
--- spec_vnops.c5 Aug 2003 06:43:56 - 1.206
+++ spec_vnops.c5 Aug 2003 19:33:06 -
@@ -505,9 +505,9 @@
devtoname(bp-b_dev), bp));
if ((dsw-d_flags D_NOGIANT) !(bp-b_flags B_KEEPGIANT)) {
- DROP_GIANT();
+ /* DROP_GIANT(); */
DEV_STRATEGY(bp);
- PICKUP_GIANT();
+ /* PICKUP_GIANT(); */
} else
DEV_STRATEGY(bp);
Hi Poul,
I noticed I had an older version of spec_vnops.c (1.205), so I
cvsupped again and build kernel, this gave me the same msgbuf error,
but with different values. Then I applied your patch and the error
messgae disapeared, but still my vinum doesn't come up.
vinum - list
2 drives:
D b State: up /dev/ad6s1e A: 77903/77903
MB (100%)
D a State: up /dev/ad4s1e A: 77903/77903
MB (100%)
0 volumes:
0 plexes:
0 subdisks:
If you need additional info, I'll be glad to provide such.
Rob Evers
--
It is a book about a Spanish guy called Manual. You should read it.
-- Dilbert
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vinum problems with todays current
On Friday, 8 August 2003 at 16:04:05 +0200, Rob wrote:
Greg 'groggy' Lehey wrote:
On Tuesday, 5 August 2003 at 22:21:41 +0200, Rob wrote:
Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
Can you try this patch:
I noticed I had an older version of spec_vnops.c (1.205), so I
cvsupped again and build kernel, this gave me the same msgbuf error,
but with different values. Then I applied your patch and the error
messgae disapeared, but still my vinum doesn't come up.
Can I assume that this is related to GEOM, and not to Vinum?
After investigating a little further today, I found the config info
on the drives to be mangled.
--
# rm -f log
# for i in /dev/da0s1h /dev/da1s1h /dev/da2s1h /dev/da3s1h; do
(dd if=$i skip=8 count=6|tr -d '\000-\011\200-\377'; echo) log
done
# cat log
IN VINOx-server.debank.tvbCc3??Z${m5?
IN VINOx-server.debank.tvaC3?WPZ${m5?
--
I guess the drives can't be started again unless I have the
parameters which I used during install (please say I'm wrong).
Hmm. That doesn't look good. No trace of the original config?
Greg
--
See complete headers for address and phone numbers
pgp0.pgp
Description: PGP signature
Re: vinum problems with todays current
In message [EMAIL PROTECTED], Rob writes:
Hi all,
After cvs'upping (about 12 hours ago) and building world/kernel vinum
stopped working. It does show my two disks but nothing more. I also
get an error message right after the bootloader:
Can you try this patch:
Index: spec_vnops.c
===
RCS file: /home/ncvs/src/sys/fs/specfs/spec_vnops.c,v
retrieving revision 1.206
diff -u -r1.206 spec_vnops.c
--- spec_vnops.c5 Aug 2003 06:43:56 - 1.206
+++ spec_vnops.c5 Aug 2003 19:33:06 -
@@ -505,9 +505,9 @@
devtoname(bp-b_dev), bp));
if ((dsw-d_flags D_NOGIANT) !(bp-b_flags B_KEEPGIANT)) {
- DROP_GIANT();
+ /* DROP_GIANT(); */
DEV_STRATEGY(bp);
- PICKUP_GIANT();
+ /* PICKUP_GIANT(); */
} else
DEV_STRATEGY(bp);
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
