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 - apply your patch and reboot once more... -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 = 'Intel Corporation' device = '(Bearlake) HECI Controller' class = simple comms Actually I dont know if I really need this (machine will be used for asterisk voip solution), but for completeness is there a driver for this piece of hardware? 10x in advance ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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." (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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, > deserve neither liberty nor safety." (Ben Franklin) > > "The course of history shows that as a government grows, liberty > decreases." (Thomas Jefferson) > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" --- end of quoted text --- -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 build on a recent 6-STABLE system (I noticed it with sources csup'd 24 April, and it continues with sources csup'd today, 1 May). The strange thing is that this is a version of samba that has previously built successfully, on the machine and with the configuration that is now failing. (I was attempting to rebuild because I saw some strange library errors.) This at least suggests to me that the problem is _not_ due to something changing with Samba, but to some other change that is being reflected in the Samba build. The system in question is built from sources csup'd today (1 May 2008), with all installed ports current as of today. The same Samba did build successfully with a source and ports tree csup'd on 7 March 2008. As a test to see if there is some problem with the ports dependencies, I've tried a 'portupgrade -fR samba'; all of the dependencies built fine, but then I got the same error when attempting to build Samba itself. It is not definitive, but this suggests to me that this is not a ports problem (per se), but a kernel/world problem. This latter is highlighted by the fact that Samba builds without error on a system with sources csup'd on 17 April. That is, if I take the exact same system on which the build fails, revert my world/kernel to a build from 17 April (leaving everything else exactly the same), then the error disappears and Samba builds successfully. The actual error is below. Any ideas are welcome. I have a machine that I can play with if someone would like me to try anything. -greg Compiling smbd/oplock_linux.c smbd/oplock_linux.c: In function `signal_handler': smbd/oplock_linux.c:73: error: structure has no member named `si_fd' The following command failed: cc -I. -I/usr/ports/net/samba3/work/samba-3.0.28/source -O2 -fno-strict-aliasing -pipe -D_SAMBA_BUILD_=3 -I/usr/local/include -I/usr/ports/net/samba3/work/samba-3.0.28/source/iniparser/src -Iinclude -I./include -I. -I. -I./lib/replace -I./lib/talloc -I./tdb/include -I./libaddns -I./librpc -DHAVE_CONFIG_H -I/usr/local/include -DLDAP_DEPRECATED -I/usr/ports/net/samba3/work/samba-3.0.28/source/lib -D_SAMBA_BUILD_=3 -fPIC -DPIC -c smbd/oplock_linux.c -o smbd/oplock_linux.o *** Error code 1 Stop in /usr/ports/net/samba3/work/samba-3.0.28/source. *** Error code 1 Stop in /usr/ports/net/samba3. *** Error code 1 Stop in /usr/ports/net/samba3. -- greg byshenk - [EMAIL PROTECTED] - Leiden, NL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 Samba3 (samba-3.0.28,1) won't build > on a recent 6-STABLE system (I noticed it with sources csup'd 24 April, and > it continues with sources csup'd today, 1 May). The strange thing is that > this is a version of samba that has previously built successfully, on the > machine and with the configuration that is now failing. (I was attempting > to rebuild because I saw some strange library errors.) This at least > suggests to me that the problem is _not_ due to something changing with Samba, > but to some other change that is being reflected in the Samba build. > > > The system in question is built from sources csup'd today (1 May 2008), with > all installed ports current as of today. The same Samba did build > successfully > with a source and ports tree csup'd on 7 March 2008. > > As a test to see if there is some problem with the ports dependencies, I've > tried a 'portupgrade -fR samba'; all of the dependencies built fine, but then > I got the same error when attempting to build Samba itself. It is not > definitive, but this suggests to me that this is not a ports problem (per se), > but a kernel/world problem. > > This latter is highlighted by the fact that Samba builds without error on a > system with sources csup'd on 17 April. That is, if I take the exact same > system on which the build fails, revert my world/kernel to a build from > 17 April (leaving everything else exactly the same), then the error > disappears and Samba builds successfully. > > > The actual error is below. Any ideas are welcome. I have a machine that I can > play with if someone would like me to try anything. > > -greg > > > Compiling smbd/oplock_linux.c > smbd/oplock_linux.c: In function `signal_handler': > smbd/oplock_linux.c:73: error: structure has no member named `si_fd' > The following command failed: > cc -I. -I/usr/ports/net/samba3/work/samba-3.0.28/source -O2 > -fno-strict-aliasing -pipe -D_SAMBA_BUILD_=3 -I/usr/local/include > -I/usr/ports/net/samba3/work/samba-3.0.28/source/iniparser/src -Iinclude > -I./include -I. -I. -I./lib/replace -I./lib/talloc -I./tdb/include > -I./libaddns -I./librpc -DHAVE_CONFIG_H -I/usr/local/include > -DLDAP_DEPRECATED-I/usr/ports/net/samba3/work/samba-3.0.28/source/lib > -D_SAMBA_BUILD_=3 -fPIC -DPIC -c smbd/oplock_linux.c -o smbd/oplock_linux.o > *** Error code 1 > > Stop in /usr/ports/net/samba3/work/samba-3.0.28/source. > *** Error code 1 > > Stop in /usr/ports/net/samba3. > *** Error code 1 > > Stop in /usr/ports/net/samba3. > I can confirm this on a 6-STABLE system last SUPed (kernel and world rebuilt) to 20080428 11:23 EDT. samba-3.0.28,1 built fine on this box when it was 6.3-RELEASE, and now fails in exactly the same place when trying to rebuild on 6-STABLE. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 slashread your textcast about jargon and nodnodnod with your cyber-sentiment." - gad_zuki! smime.p7s Description: S/MIME cryptographic signature
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 user level process. This is due to the fact that vmstat calls the vmtotal() routine which in turn does a whole lot of locking. The vmtotal call locks and walks the VM object list twice in a mark and sweep operation. So, the question is, "What is the right way to fix this?" I could remove the locking since the O_ACTIVE bit is not used by any other routine besides vmtotal, but I'm not too happy about that. The relevant code can be found in src/sys/vm/vm_meter.c in vmtotal(). Thoughts? Can you _really_ remove the locking? I don't think that would be safe if the list is being manipulated, but I haven't checked. Typically one uses a sentinal to get around such problems. Basically insert a dummy object that no one should touch other than you, then drop the lock periodically and insert it into the list, then resume. net80211 uses a scan generation # to walk it's node lists. No sentinel. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 > > |> there be any callbacks be called? I have received some report regarding > > |> hangs after this, and IIRC the only operation is to IPI BSP to do reboot? > > | > > | Several callbacks are called after that message. Anything that > > | registers with the shutdown_post_sync or shutdown_final event handler, > > | for example, and the dump routine if you are using "reboot -d". > > | > > | Before trying to diagnose this, however, make sure you are running with > > | sys/dev/usb/ehci_pci.c 1.30 (which has also been MFC'd to 6/7), as that > > | seems to have been the cause of most of the recently reported "hangs > > | after printing uptime" PRs. > > > > I see... It seems that this is the culprit. > > > > To John: Do you think it's worthy to make this an errata to the > > supported RELENG_6_X and RELENG_7_0 branches? > > If someone wants to push re@ to do that they can, but my experience with > getting re@ to actually get errata fixes has me skeptical (I think I had > patches for about 6 or 7 panics or kernel deadlocks for 6.2 that never got > pushed as errata patches). 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. Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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. Could you please let me know if I have missed something important? http://www.delphij.net/errata-20080430.xml Cheers, - -- Xin LI <[EMAIL PROTECTED]>http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgZ9tIACgkQi+vbBBjt66AHvgCdEVoZPONbOw15G1dpN2oP2coy JIYAn2l4UlwNFNGUGd9cX+J749+L+FEs =cA5t -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 as candidates. Could you please let me know if I have missed something important? http://www.delphij.net/errata-20080430.xml Please look at this thread in -net : TCP options order changed in FreeBSD 7,incompatible with some routers I think problem mention there should go in errata as it's quite serious. src/sys/netinet/tcp_output.c Revision 1.141.2.4 (not sure that this is the fix ..) P.S. When can we expect 7.0p1 ? :) -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 candidate. |> |> FWIW I have written to re@ indicating some changes I wanted for |> RELENG_7_0 as candidates. Could you please let me know if I have missed |> something important? |> |> http://www.delphij.net/errata-20080430.xml | | Please look at this thread in -net : | TCP options order changed in FreeBSD 7,incompatible with some routers | I think problem mention there should go in errata as it's quite serious. | | src/sys/netinet/tcp_output.c Revision 1.141.2.4 (not sure that this is | the fix ..) I see, I will take a look at it. IIRC at least two files were involved. | P.S. When can we expect 7.0p1 ? :) Actually there is already 7.0-R-p1 for the SSH vulnerability, note that this is not a kernel vulnerability so if you use binary update then the version number would not show up :) [EMAIL PROTECTED] ~> uname -sr FreeBSD 7.0-RELEASE-p1 Cheers, - -- Xin LI <[EMAIL PROTECTED]>http://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgaBZ4ACgkQi+vbBBjt66BWAQCeP/j4VGsHL458f5/LG2pXoPju 0qUAoJdJBCp5jIw8pGxpp2B4I24uVJ4E =JWjo -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgaCI4ACgkQi+vbBBjt66APqgCeJxDEzOoXeX0WNVpBywbiCuh7 bOoAoIfJHdrqKnIkWEWR954XOXu0fj5s =ZJ/C -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 the files.
>
>
> Let me summarise my investigations till now :
> [ .. more stuff deleted .. ]
> - it does *not* seem to depend on :
>
>- the interface : I could produce it using nfe0, nfe1 and
> re0 using some netgear pci-card
>
>- the distribution of the 4Gig memory : installing 4G at
> CPU1 or 1G at CPU1 and 2G at CPU2 produces same results
> (NB, all memory passed memtest.iso in both situtations
> for complete run)
>
>- the frequency control method : easier to produce with
> cpufreq/powerd, but finally I can reproduce the cooruption
> as well using acpi_ppc
>
>- the nfs-client and options (not exhaustively tested, but different
> test include i386-releng6, amd64-releng6 and linux, and quite
> a set of different try and see mounf_nfs options
>
> I am testing right now with a fixed frequency of 1Ghz.
I cannot reproduce it at fixed cpu-frequency with cpufreq loaded (I
ran my test for three days without prob, normally a couple of hours
was enough).
But I looked again at the corrupted copies :
# for i in raid5/xps/SAVE/1 raid5/pxe/SAVE/1 raid5/pxe/SAVE/2 raid5/pxe/SAVE/3
raid5/blockhead/SAVE/1 scsi/pxe/SAVE/1 scsi/blockhead/SAVE/1
scsi/blockhead/SAVE/2 scsi/blockhead/SAVE/3 scsi/blockhead/SAVE/4; do
ls -l $i/BIG; cmp -x $i/BIG $i/BIG2; echo; done
-rw-r--r-- 1 root wheel 144703488 Apr 26 16:06 raid5/xps/SAVE/1/BIG
004fd908 18 00
02c9e6c8 11 00
034ab6c8 90 00
037e4648 09 00
039e85c8 91 01
04484408 00 09
06115cc8 00 81
06e5d148 01 91
07016048 18 00
074307c8 08 19
07aa45c8 29 20
080bfb88 00 11
-rw-r--r-- 1 root wheel 144703488 Apr 20 14:07 raid5/pxe/SAVE/1/BIG
03869a48 09 00
-rw-r--r-- 1 root wheel 144703488 Apr 20 14:47 raid5/pxe/SAVE/2/BIG
05209d88 09 00
-rw-r--r-- 1 root wheel 39845888 Apr 20 15:17 raid5/pxe/SAVE/3/BIG
01777148 09 00
-rw-r--r-- 1 root wheel 144703488 Apr 20 14:54 raid5/blockhead/SAVE/1/BIG
00f10f88 09 00
-rw-r--r-- 1 root wheel 39845888 Apr 20 16:08 scsi/pxe/SAVE/1/BIG
01f4c4c8 11 00
-rw-r--r-- 1 root wheel 144703488 Apr 20 15:38 scsi/blockhead/SAVE/1/BIG
06c3d6c8 11 00
-rw-r--r-- 1 root wheel 144703488 Apr 20 16:11 scsi/blockhead/SAVE/2/BIG
0725ca48 18 00
-rw-r--r-- 1 root wheel 144703488 Apr 20 17:32 scsi/blockhead/SAVE/3/BIG
01608008 09 00
-rw-r--r-- 1 root wheel 144703488 Apr 23 19:26 scsi/blockhead/SAVE/4/BIG
00f3b888 18 00
The output from raid5/xps/SAVE/1/BIG is after installing at a lab with
without doubt more sophisticated switches than I use and the first I was
able to produce with more that just one byte corrupted, but still with
the same pattern :
it looks like the position always is 2^3 * 'somethin without power of two'
(e.g. factor(hex2dec('00f10f88')) = 2 2 2 809 2441
factor(hex2dec('01f4c4c8')) = 2 2 2 317 12941 )
and the corruption is one out of the following half-byte transitions :
1 -> 0
8 -> 0
9 -> 0
0 -> 1
0 -> 8
0 -> 9
8 -> 9
Maybe this gives a hint to someone ...
Best, Arno
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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=NO. Good luck! ;) Hmmm... I have that set. It only seems to not reboot on one system I have. 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." (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 feeling especially > >brave, you can also set fsck_y_enable=YES and background_fsck=NO. > > > >Good luck! ;) > > > Hmmm... I have that set. It only seems to not reboot on one > system I have. FWIW, I've had problems with 6.2 not rebooting reliably on several SMP P4 Xeon systems; the problem seems to be that sometimes while dumping it either freezes completely or double-faults and hangs at that point until physically reset. This problem appeared simultaneously on several SMP servers when they were upgraded to 6.2, after they had run reliably for years on FreeBSD 4.x. Adding insult to injury, when it does dump successfully, I don't reliably get an image saved in /var/crash. (And if I did, it doesn't appear that it would do me any good as nobody is interested any longer in problems with 6.2.) Thankfully, via a combination of adding RAM and tuning kernel parameters I eventually got them to where they'll reliably stay up for reasonably long stretches, certainly more than the 20 days uptime I was getting when I first upgraded them. -- Clifton -- Clifton Royston -- [EMAIL PROTECTED] / [EMAIL PROTECTED] President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 wrong dumpdate. getfile: lost data abort? [yn] n Header with wrong dumpdate. Header with wrong dumpdate. Header with wrong dumpdate. Header with wrong dumpdate. getfile: lost data abort? [yn] n Header with wrong dumpdate. Header with wrong dumpdate. Header with wrong dumpdate. Header with wrong dumpdate. Header with wrong dumpdate. Header with wrong dumpdate. Header with wrong dumpdate. Header with wrong dumpdate. getfile: lost data abort? [yn] y So long as I keep saying no to the amanda abort prompt, the files are successfully restored. I've seen http://www.freebsd.org/cgi/query-pr.cgi?pr=120881 which seems to apply to the "getfile: lost data" lines. There is also http://www.FreeBSD.org/cgi/query-pr.cgi?pr=bin/118087 which seems to apply to "Header with wrong dumpdate." 118087 seems to have been applied to CVS in rev 1.51 of tape.c by mckusick a couple of weeks ago. I don't think it has been merged to 7-STABLE yet. 120881 seems not to have been applied to CVS just yet. Does anyone have a guess as to when restore will be fixed in -STABLE? -- Scott LambertKC5MLE Unix SysAdmin [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 story very often, so often that I almost think it's a fairy > tale. :-) > Most of the times the "RealTek NIC" story is told, it isn't backed up > with any references to evidence. Draw your own conclusions. Well, my latest encounter with "Netgear GA311 Rev. A1 (RTL8169S-32) Gigabit Ethernet" falls neatly into the "fairy tale" category -- it has jittery bit in the chip ID register and will advertise itself as 8129 or 8169 depending on the phase of the moon. While it is not fair to judge the whole product line based on the single specimen, it took me some time to figure it out, and, on top of that, I have wasted time of some people, valuable to the FreeBSD project, who were kind enough to review submitted PR and close it. I am not planning on buying more of these to get representative statistics, though ;) The card in question was purchased as the replacement for the 'fxp', which was sitting in that system for a long while, so I think I am in my right to blame the card and not the system. -- Alexandre "Sunny" Kovalenko (Олександр Коваленко) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
