Re: System deadlock when using mksnap_ffs

On Thu, Nov 13, 2008 at 05:08:10PM +0100, Greg Byshenk wrote: On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote: The rest of the below information is good -- but I'm confused about something: is there anyone out there who can use mksnap_ffs on a filesystem (/usr is a good

Re: ZFS crashes on heavy threaded environment

Xin LI wrote: Xin LI wrote: Hi, Pawel, We can still reproduce the ZFS crash (threading+heavy I/O load) on a fresh 7.1-STABLE build, in a few minutes: /usr/local/bin/iozone -M -e -+u -T -t 128 -S 4096 -L 64 -r 4k -s 30g -i 0 -i 1 -i 2 -i 8 -+p 70 -C Yes, this is known. I have included

Re: RELENG_7 build failure in rescue/ (iconv?)

Ignore this, turned out that PEBCAK. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FreeBSD 6.3 gre and traceroute

Stephen Clark wrote: Robert Noland wrote: On Thu, 2008-11-13 at 07:48 -0500, Stephen Clark wrote: Julian Elischer wrote: Stephen Clark wrote: Julian Elischer wrote: you will need to define the setup and question better. thanks.. cleaning it up a bit more... 10.0.129.1 FreeBSD workstation

FreeBSD 6.3 ipsec and traceroute doesn't work as good as Linux -why?

10.0.129.1 FreeBSD workstation ^ | | ethernet | v 10.0.128.1 Freebsd FW A ^ | | ipsec | v 192.168.2.1 Linux FW B ^ | | ethernet | v 192.168.2.20 linux workstation from 192.168.2.20 Linux-ipsec-FreeBSD traceroute -I 10.0.129.1 traceroute to 10.0.129.1

Re: Multiple panics with 7.1-PRERELEASE amd64/i386 and varnish

Le 06/11/2008 16:05, Herve Boulouis a ?crit: Le 06/11/2008 11:29, Herve Boulouis a ?crit: I just tried to reboot one of the boxes without kern.ipc.maxpipekva=104857600 to check for kva problems but crashes persists, though the stack is completely different now. This time I included all

Re: FreeBSD 6.3 ipsec and traceroute doesn't work as good as Linux -why?

On Fri, Nov 14, 2008 at 09:31:24AM -0500, Stephen Clark wrote: Dear Stephen, I don't want to be rude, but looking at your description I don't see what's wrong with the behaviour, but it seems you don't understand what '* * *' really means. How does traceroute work? Well, it sends out a packet

Re: FreeBSD 6.3 ipsec and traceroute doesn't work as good as Linux -why?

Holger Kipp wrote: On Fri, Nov 14, 2008 at 09:31:24AM -0500, Stephen Clark wrote: Dear Stephen, I don't want to be rude, but looking at your description I don't see what's wrong with the behaviour, but it seems you don't understand what '* * *' really means. How does traceroute work? Well, it

Re: FreeBSD 6.3 gre and traceroute

Julian Elischer wrote: Stephen Clark wrote: Stephen Clark wrote: 10.0.129.1 FreeBSD workstation ^ | | ethernet | v 10.0.128.1 Freebsd FW A ^ | | gre / ipsec | v 192.168.3.1 FreeBSD FW B ^ | | ethernet | v 192.168.3.86 linux workstation Also just using gre's without the

Re: FreeBSD 6.3 gre and traceroute

Stephen Clark wrote: Stephen Clark wrote: 10.0.129.1 FreeBSD workstation ^ | | ethernet | v 10.0.128.1 Freebsd FW A ^ | | gre / ipsec | v 192.168.3.1 FreeBSD FW B ^ | | ethernet | v 192.168.3.86 linux workstation Also just using gre's without the underlying ipsec tunnels

Re: FreeBSD 6.3 gre and traceroute

On Fri, 2008-11-14 at 10:25 -0800, Julian Elischer wrote: Stephen Clark wrote: Stephen Clark wrote: 10.0.129.1 FreeBSD workstation ^ | | ethernet | v 10.0.128.1 Freebsd FW A ^ | | gre / ipsec | v 192.168.3.1 FreeBSD FW B ^ | | ethernet | v

diskless+pxe notes

Hi, i finally decided to try and use pxeboot to replace the etherboot method I was using so far for diskless setups. The goal is to fully share the server's root and /usr directories, as documented in diskless(8). I'd like to share the following notes, hopefully to go in the manpage.