Kamp" <[EMAIL PROTECTED]>
To: "Aaron Wohl" <[EMAIL PROTECTED]>
Date: Fri, 08 Aug 2003 15:24:09 +0200
Subject: Re: vinum lock panic at startup -current
In message <[EMAIL PROTECTED]>, "Aaron Wohl"
writes:
> Panicstring: mutex Giant owned at /usr/src/sy
In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
> Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198
Ok, then I think I know what it is.
Vinum appearantly does not go through SPECFS but rather calls into
the disk device drivers directly. That is a pretty wrong thing to
do,
In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
>I just cvsuped -current this afternoon to get about 1 weeks updates.
>After that the kernel panics booting starting vinum. I removed the one
>vinum volume (reformated as UFS2) I had for testing. And it still panics.
> I changed the /etc/rc.con
I just cvsuped -current this afternoon to get about 1 weeks updates.
After that the kernel panics booting starting vinum. I removed the one
vinum volume (reformated as UFS2) I had for testing. And it still panics.
I changed the /etc/rc.conf
start_vinum="YES" to NO and can start ok now.
Anyone
On Fri, Aug 08, 2003 at 10:22:06AM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
> >I just cvsuped -current this afternoon to get about 1 weeks updates.
> >After that the kernel panics booting starting vinum. I removed the one
> >vinum volume (reformated a
On Thursday, 7 August 2003 at 18:23:10 -0600, Aaron Wohl wrote:
> I just cvsuped -current this afternoon to get about 1 weeks updates.
> After that the kernel panics booting starting vinum. I removed the one
> vinum volume (reformated as UFS2) I had for testing. And it still panics.
> I changed
On Sat, Aug 09, 2003 at 06:38:51AM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey"
> writes:
>
> >> and it seems that vinum does not respect the D_NOGIANT flag which
> >> GEOM recently started setting.
> >
> >Probably because it didn't know about it. As I'
On Friday, 8 August 2003 at 15:24:09 +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
>
>> Panicstring: mutex Giant owned at /usr/src/sys/geom/geom_dev.c:198
>
> Ok, then I think I know what it is.
>
> Vinum appearantly does not go through SPECFS but rather c
I tried it this morning on different systems. So far the two AMD systems
panic with vinum start and the intel/p4 works ok. All systems have no
vinum volumes currently.
Good dump found on device /dev/ad0s1b
Architecture: i386
Architecture version: 1
Dump length: 1073676288B (1023 MB)
Bloc
In message <[EMAIL PROTECTED]>, "Greg 'groggy' Lehey"
writes:
>> and it seems that vinum does not respect the D_NOGIANT flag which
>> GEOM recently started setting.
>
>Probably because it didn't know about it. As I've said before, it
>would be nice to be informed about the changes you're making,
On Friday, 8 August 2003 at 10:27:31 +0200, Erwin Lansing wrote:
> On Fri, Aug 08, 2003 at 10:22:06AM +0200, Poul-Henning Kamp wrote:
>> In message <[EMAIL PROTECTED]>, "Aaron Wohl" writes:
>>> I just cvsuped -current this afternoon to get about 1 weeks updates.
>>> After that the kernel panics bo
11 matches
Mail list logo
