Mel Flynn wrote:
[1] In order to get this working I had to put a statically compiled ps in the
jail
This is a pretty standard practice. I always put these statically built
into any jails that don't match the outside system. I use the following
crunchgen config to accomplish that.
Cheers,
It seems that FreeBSD has an ABI compatibility policy where major
versions remain ABI and API compatible throughout minor point versions.
That is to say that the kernel interfaces and libraries for (eg)
7-STABLE, 7.1-RELEASE, 7.2-RELEASE are not supposed to change.
Is this a policy of the
Stef Walter wrote:
I've been trying to track down a deadlock on some newish production
servers running FreeBSD 6.3-RELEASE-p2. The deadlock occurs on a
specific (although mundane) hardware configuration, and each of several
servers running this hardware deadlock about once per week
at ata4-master
ar1: disk1 READY (mirror) using ad10 at ata5-master
In any case, this is water under the bridge for me now.
Cheers,
Stef Walter
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
is degraded, the FreeBSD driver thinks it's business as usual. In
my case this resulted in file system corruption. Relevant output below.
FreeBSD version: 6.3-RELEASE-p2
Cheers,
Stef Walter
BIOS OUTPUT:
Copyright(C) 2003-06 Intel Corporation. All Rights Reserved.
RAID Volumes:
ID NameLevel
the Intel
MatrixRAID items:
http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues
Yes, I reported several of those as well as provided patches for them.
That was back when I had relevant hardware in my lab.
Cheers,
Stef Walter
___
freebsd
) whenever the status changes, regardless
of whether that change takes place when the machine is off or not.
Without testing, I can't be sure whether this solves the problem on
other ataraid devices.
Cheers,
Stef Walter
___
freebsd-hackers@freebsd.org mailing
specific problem reports and issues are outlined below.
Cheers,
Stef Walter
Fix an early boot panic if you reboot with all drives present when your
RAID is marked DEGRADED. This can happen if a drive has an unreadable
block and the drive gets detached from the RAID. Rebooting at this point
reattached
Open PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/108924
FWIW, kern/108924 seems to be a duplicate of kern/102211
Cheers,
Stef Walter
Jeremy Chadwick wrote:
On Thu, Mar 20, 2008 at 01:16:39PM +, Stef Walter wrote:
Here's some vital patches for the ataraid driver when using
not
seeing?
Reasoning:
I'm using devfs in jails, and I'd like anything written (by user space
programs, syslogd, etc...) to /dev/console to go to a file in the jail.
So at jail startup I'd like to put a symlink over /dev/console to a
normal file.
Cheers,
Stef Walter
10 matches
Mail list logo
