. I'll deploy it and
keep the list posted.
Stef
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
John Baldwin wrote:
> On Sunday 15 June 2008 07:23:19 am 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 configur
http://www.freebsd.org/cgi/query-pr.cgi?pr=114057
And there are one or two other patches on some deployed systems (eg:
'multi ip jail patches'). I used to be in the
no-patches-on-my-production-servers camp, but I've found that it was
unrealistic and result
t I'm 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 f
Stef Walter wrote:
> After deleting a device in devfs, any symlink placed over it results in
> ENOENT.
>
> I'd like to fix this behavior. Or is there a reason for it that I'm not
> seeing?
Filed a bug report with a patch that solves the issue:
http://www.freebsd.org/c
rious 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 +0000, Stef Walter wrote:
>> Here's some vital patches for the ataraid dri
ing the generation) 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
___
free
a
RAID 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 Na
t;ATA (SATA, PATA, ATAPI)" section, specifically 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 r
er
ar1: 476937MB status: READY
ar1: disk0 READY (master) using ad8 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
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 ab
? If so, is it documented anywhere? Or is
it just a convention?
Cheers,
Stef
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
at.
Cheers,
Stef
# Commands to build in
progs ps ipcs netstat pkill top w killall
progs systat iostat
progs jkill
progs kldstat
# Link these programs to each other
ln pkill pgrep
ln w uptime
# Libraries which we need
libs -lutil -lkvm -ldevstat -lncurses -ldevstat -lm -lnetgraph -lme
14 matches
Mail list logo
