kern/52916: vinum causes panic after start/stop/... cycle, easy
to reproduce
Greg 'groggy' Lehey
grog at FreeBSD.org
Mon Jun 23 15:30:14 PDT 2003
The following reply was made to PR kern/52916; it has been noted by GNATS.
From: Greg 'groggy' Lehey <grog at FreeBSD.org>
To: Pawel Malachowski <pawmal at unia.3lo.lublin.pl>
Cc: Freebsd-gnats-submit at FreeBSD.org
Subject: Re: kern/52916: vinum causes panic after start/stop/... cycle, easy to reproduce
Date: Tue, 24 Jun 2003 07:52:35 +0930
--fRqxu2t+6O910vVH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Monday, 23 June 2003 at 23:40:36 +0200, Pawel Malachowski wrote:
> On 6 Jun 2003 at 14:52, Greg 'groggy' Lehey wrote:
>
>> I'm guessing this has something to do with md devices. Do you use
>> any? I don't, and every 'vinum start' created one. I've committed a
>> fix to vinum(8) (revision 1.31.2.6 of src/sbin/vinum/commands.c).
>> Please try it and tell me if it fixes the problem.
>
> Problem appears when we call (f)sync() while `vinum start' command is working.
> After killing syslogd (which was using fsync(), I have both /var/log and /dev
> on / fs with SoftUpdates enabled), stability increased.
>
> I was running /bin/sync frequently during vinum start/stop loop and sometimes I
> can see `rm' (and other commands called from make_devices(), src/sbin/vinum/v.c)
> complaining it was not possible to remove/recreate device files in /dev/vinum.
> Panic happened within few seconds.
I'd appreciate answers to my questions. Also a backtrace would help.
Greg
--
See complete headers for address and phone numbers
--fRqxu2t+6O910vVH
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)
iD8DBQE+932rIubykFB6QiMRAvJGAJ4jWOMeTnptkF2MSO0Zx3mtOdZWEgCfXJPI
oVQLrEW0qedWFi22JXRhd4g=
=RXj2
-----END PGP SIGNATURE-----
--fRqxu2t+6O910vVH--
More information about the freebsd-bugs
mailing list