Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Aug 2007 15:25:44 +1000
From:      "Jan Mikkelsen" <janm@transactionware.com>
To:        "'Ivan Voras'" <ivoras@fer.hr>, <freebsd-current@freebsd.org>
Subject:   RE: Repeated UFS panics?
Message-ID:  <004f01c7e86a$b78088a0$268199e0$@com>
In-Reply-To: <fas4rs$ur$1@sea.gmane.org>
References:  <fas4rs$ur$1@sea.gmane.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Ivan Voras wrote:
> Has anyone experienced frequent UFS panics on VMWare on fresh
> current?
> I've started seeing ufs_dirbad panics almost daily. For a
> while I could
> cause them simply by running make installworld to a freshly
> newfs-ed
> file system - the panic message points to the *new* file
> system.
> Unfortunately, kgdb cannot process the generated vmcores
> (though they
> are on a separate file system that has never crashed). The
> repeatable
> panics on new file systems have stopped when I rebuilt the
> kernel, but
> now they are happening again, this time on my /usr/ports. I
> don't think
> file system options have an influence - they first happened on
> a
> "normal" UFS (noasync), and now they are happening on
> gjournaled, aync
> mounted UFS.

Is this an SMP or uniprocessor virtual machine?

I see frequent "signal 11" failures from gcc when putting an SMP
virtual machine under load.  The same load on a uniprocessor
virtual machine works fine.  This is 6.2-STABLE;  I haven't tried
-CURRENT.  VMware Server 1.0.3, AMD-X2, ECC memory, Windows XP
64-bit host.

Regards,

Jan Mikkelsen





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004f01c7e86a$b78088a0$268199e0$>