Re: Packet-corruption with re(4)

On Tue, 2008-04-29 at 22:58 +0200, Torfinn Ingolfsen wrote: > On Tue, 29 Apr 2008 05:08:34 -0700 > Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > > > I'd recommend staying away from Realtek NICs. Pick up an Intel > > Pro/1000 GT or PT. Realtek has a well-known history of issues. > > I hear that s

restore issues "Header with wrong dumpdate." and "getfile: lost data"

We have upgraded our AMANDA server from FreeBSD 4.x to FreeBSD 7.0-RELEASE. We still have several 4.x boxes and are having issues when we try to restore files on the AMANDA server for any of the 4.x servers. We see the following errors running amrecover: Header with wrong dumpdate. Header with w

Re: reboot after panic

On Thu, May 01, 2008 at 03:15:51PM -0400, Stephen Clark wrote: > Matthew X. Economou wrote: > >Steve, > > > >I recall having to set dumpdev in /etc/rc.conf before I could get > >FreeBSD to reboot automatically after a panic. I have dumpdev=AUTO > >set on all of my headless servers. If you are fee

Re: reboot after panic

Matthew X. Economou wrote: Steve, I recall having to set dumpdev in /etc/rc.conf before I could get FreeBSD to reboot automatically after a panic. I have dumpdev=AUTO set on all of my headless servers. If you are feeling especially brave, you can also set fsck_y_enable=YES and background_fsck=

Re: nfs-server silent data corruption

Hello, > [ .. stuff deleted .. ] > > I have recompiled the kernel with ULE, and it seems fine as well. I > > ran 160 iterations of a 300MB file and there was no corruption. Same > > process - copy a junk random file over nfs mount, unmount the nfs > > mount, remount it copy it back, compare t

Re: What does system do after "Uptime: "?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So I think it was 1.141.2.4 of sys/netinet/tcp_output.c. The change on tcp_var.h was reverted after this as it is no longer necessary. Cheers, - -- Xin LI <[EMAIL PROTECTED]>http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PG

Re: What does system do after "Uptime: "?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan Lambrev wrote: | Xin LI wrote: |> -BEGIN PGP SIGNED MESSAGE- |> Hash: SHA1 |> |> Gavin Atkinson wrote: |> | FWIW, there have been probably around 10 PRs in in the last few months |> | about this behaviour. I'd vote for it as an errata

Re: What does system do after "Uptime: "?

Xin LI wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gavin Atkinson wrote: | FWIW, there have been probably around 10 PRs in in the last few months | about this behaviour. I'd vote for it as an errata candidate. FWIW I have written to re@ indicating some changes I wanted for RELENG_7_0

Re: What does system do after "Uptime: "?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gavin Atkinson wrote: | FWIW, there have been probably around 10 PRs in in the last few months | about this behaviour. I'd vote for it as an errata candidate. FWIW I have written to re@ indicating some changes I wanted for RELENG_7_0 as candidates.

Re: What does system do after "Uptime: "?

On Wed, 2008-04-30 at 15:44 -0400, John Baldwin wrote: > On Wednesday 30 April 2008 02:49:11 pm Xin LI wrote: > > Gavin Atkinson wrote: > > | On Sun, 2008-04-27 at 22:29 -0700, Xin LI wrote: > > |> Hi, > > |> > > |> Just wonder what the system would do after Uptime: during reboot? Will > > |> ther

Re: Some odd behaviour of vmstat and vmtotal...

Alfred Perlstein wrote: * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [080430 18:13] wrote: Howdy, In deploying 7.0 at work we were finding a persistent problem when running "vmstat 1" on systems. The problem shows up as a 10ms "pause" in processing, usually packet stamping and forwarding by a us

RE: reboot after panic

Steve, I recall having to set dumpdev in /etc/rc.conf before I could get FreeBSD to reboot automatically after a panic. I have dumpdev=AUTO set on all of my headless servers. If you are feeling especially brave, you can also set fsck_y_enable=YES and background_fsck=NO. Good luck! ;) -- "I s

Re: samba build failure on 6-STABLE

Greg Byshenk wrote: > I'm posting this to freebsd-stable even though it is a problem with a port, > because the port itself has not changed, but a rebuild fails (on a system > and with a configuration that worked before my most recent system updates). > > Basically my problem is that the current

samba build failure on 6-STABLE

I'm posting this to freebsd-stable even though it is a problem with a port, because the port itself has not changed, but a rebuild fails (on a system and with a configuration that worked before my most recent system updates). Basically my problem is that the current Samba3 (samba-3.0.28,1) won't b

Re: reboot after panic

Quoting Stephen Clark, who wrote on Thu, May 01, 2008 at 08:44:42AM -0400 .. > Hello List > > How do I get my freebsd 6.1 box to automatically reboot after a panic? It should do that automatically? > Thanks, > Steve > -- > > "They that give up essential liberty to obtain temporary safety, > de

reboot after panic

Hello List How do I get my freebsd 6.1 box to automatically reboot after a panic? Thanks, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases."

is there driver for (Bearlake) HECI Controller for releng_7 (or 7_0_0)

Hello lists Intel G33 motherboard (Intel DG33FB) with FreeBSD 7 AMD64 (7.0-RELEASE-p1) one thing is missing: [EMAIL PROTECTED] ~]# pciconf -lv | grep -A3 none [EMAIL PROTECTED]:0:3:0: class=0x078000 card=0x50448086 chip=0x29c48086 rev=0x02 hdr=0x00 vendor

Re: error in src/etc/rc.d/mountcritlocal

Mike Makonnen wrote: > Please try the attached patch. > Thanks! I cannot really test the patch because this involves rebooting the system which is not that easy as it sounds ;) You can just test it yourself. Put some garbage in /etc/fstab reboot w/o your patch - see the strange error message - ap