search for: macklem

Hi all, Setup: I'm running 2 machines (amd64, 16GB) with FreeBSD 9-STABLE (Mar 14 so far) acting as NFS servers. They each serve 3 zpools (holding a single zfs, hourly snapshots). The zpools each are 3-way mirrors of ggate devices, each 2 TB, so 2 TB per zpool. Compression is "on" (to save bandwith to the backend, compressratio around 1.05 to 1.15), atime is off. There is no

I'm running a few servers sitting on top of a NetAPP file server ? everything runs great, but periodically I'm getting: nfs_getpages: error 13 vm_fault: pager read error, pid 11355 (https) errors on my screen ? not always same pid ? the annoying part is that it seems to always affect the same jail that is running .. if I shutdown all jails on that physical server, everything shuts down

...ust be missing something pretty basic. And, yes, I''m new to shorewall, so please bear that in mind :-). I''m hoping that someone with more shorewall/iptables/networking knowledge can help me. I''ll be happy to send along any other files - just ask :-) Thanks. -- David Macklem dmacklem@netcom.ca

Two machines (NFS Server: running ZFS / Client: disk-less), both are running FreeBSD r253506. The NFS client starts to deadlock processes within a few hours. It usually gets worse from there on. The processes stay in "D" state. I haven't been able to reproduce it when I want it to happen. I only have to wait a few hours until the deadlocks occur when traffic to the client machine

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Macklem wrote: | Tom, | | As I said in a previous mail, these rules file changes work. Thanks. | | However, I''m not sure that your firewall changes to handle the GATEWAY column in the tunnels file does work. I downloaded the most recent STABLE2 release from CVS and replaced my copy of the firewa...

Hi, my FreeBSD-9/stable machine (FreeBSD freebsd-tower.goebo.site 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #2 r241044M: Sat Sep 29 12:52:01 CEST 2012 lbo@freebsd-tower.goebo.site:/usr/obj/usr/src/sys/GENERIC i386) crashes reproducibly when rsync-ing files to an NFSv4 share on the FreeBSD machine. The crash makes the system reboot. The crash creates files in /var/crash which may be obtained