7.3-RC2 Available...
The third and what should be last of the test builds for the 7.3-RELEASE cycle, 7.3-RC2, is available for amd64, i386, pc98, and sparc64 architectures. The target schedule as well as the current status of the release is available here: http://wiki.freebsd.org/Releng/7.3TODO The schedule has slipped by a bit over a week so the actual target for the release announcement is really about a week and a half from now. If you notice problems you can report them through the normal Gnats PR system or on the freebsd-stable mailing list. There are known issues with the Radeon video driver that have caused some people problems. The problems have been nebulous enough that we have decided to not hold up the release due to that specific issue. At the point that driver has stabilized it will be handled as an Errata Notice. So far that is the only big problem we've been tracking as part of the release that has not been resolved in one way or another. ISO images for the architectures listed above are available on the FTP mirror sites. Packages were included for amd64 and i386 architectures that were taken from the set built for the release (packages-7.3-release) and most likely reflects the set that will be provided with the release itself. Packages were not provided for the other architectures in the ISO images. If you are using csup/cvsup methods to update an older system the branch tag to use is RELENG_7_3. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.1-RELEASE 7.2-RELEASE, 7.3-BETA1, or 7.3-RC1 can upgrade as follows: # freebsd-update upgrade -r 7.3-RC2 During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components, and the system needs to be rebooted again: # freebsd-update install # shutdown -r now Users of earlier FreeBSD releases (FreeBSD 6.x) can also use freebsd-update to upgrade to FreeBSD 7.3-RC2, but will be prompted to rebuild all third-party applications (e.g., anything installed from the ports tree) after the second invocation of freebsd-update install, in order to handle differences in the system libraries between FreeBSD 6.x and FreeBSD 7.x. Checksums: MD5 (FreeBSD-7.3-RC2-amd64-bootonly.iso) = 36c4d133526ad66e307d27447f52376e MD5 (FreeBSD-7.3-RC2-amd64-disc1.iso) = 66ea415f7c4253cfc447fd279f6bf178 MD5 (FreeBSD-7.3-RC2-amd64-disc2.iso) = d5756876ec48e30e674076d5379ba1cd MD5 (FreeBSD-7.3-RC2-amd64-disc3.iso) = bfb22e2f44a65d47101f176bf3775950 MD5 (FreeBSD-7.3-RC2-amd64-docs.iso) = 825213e43710a84f85821bbf58742538 MD5 (FreeBSD-7.3-RC2-amd64-dvd1.iso) = 91bcd1ce77f2388e3ea8ad2309fa229f MD5 (FreeBSD-7.3-RC2-amd64-livefs.iso) = f9b71b20c17646e3cf230e8deeb34e02 MD5 (FreeBSD-7.3-RC2-i386-bootonly.iso) = 74b648f7018aa35ac8d8b08e5296d2bc MD5 (FreeBSD-7.3-RC2-i386-disc1.iso) = f47158c8a6265213d43652edf2e0314d MD5 (FreeBSD-7.3-RC2-i386-disc2.iso) = 8535cf1ea75b75aa65b3b3a6f1d451f1 MD5 (FreeBSD-7.3-RC2-i386-disc3.iso) = 9c8e3e71a046690bee8c67061f7dbd05 MD5 (FreeBSD-7.3-RC2-i386-docs.iso) = 2be6491f0d19eff64110cb6e34bc10d8 MD5 (FreeBSD-7.3-RC2-i386-dvd1.iso) = 97647b3f0232a0cdaa0d11f88552132d MD5 (FreeBSD-7.3-RC2-i386-livefs.iso) = 7cc44a0cd63af59215fd23ce8123103e MD5 (FreeBSD-7.3-RC2-pc98-bootonly.iso) = 0a7fa094fdade9855e420c55d93cb3d8 MD5 (FreeBSD-7.3-RC2-pc98-disc1.iso) = bf2ac28c5bb28a7881cb53dd2f8640a5 MD5 (FreeBSD-7.3-RC2-pc98-livefs.iso) = 6b1b4ead5f552690c626871bb04c5002 MD5 (FreeBSD-7.3-RC2-sparc64-bootonly.iso) = f844c766bac4473b3477edda06828d5f MD5 (FreeBSD-7.3-RC2-sparc64-disc1.iso) = 0af0227bb90f7faa23b39e66d3b89ecf MD5 (FreeBSD-7.3-RC2-sparc64-disc2.iso) = 637fb946b3d7cbb72b82a1d469d5735c MD5 (FreeBSD-7.3-RC2-sparc64-disc3.iso) = 1224f546b78aafdce4f9352636c6b07b MD5 (FreeBSD-7.3-RC2-sparc64-docs.iso) = 738a549ee8c2d6a21b7d9cc864b07842 SHA256 (FreeBSD-7.3-RC2-amd64-bootonly.iso) = 26f2dafd7d990e1a359445b9cdcf119dfa824f493d119fa250de9ab1deac6af6 SHA256 (FreeBSD-7.3-RC2-amd64-disc1.iso) = 668687e8fe0622482d696d806acb4c867bc41d9bf4b2071d9eb15ee377672720 SHA256 (FreeBSD-7.3-RC2-amd64-disc2.iso) = 8cea908115f11eaafd1fb78f68e08cdadd11dd3617fe4750d8743c105384e386 SHA256 (FreeBSD-7.3-RC2-amd64-disc3.iso) = 2d294321812a73e26b1b7c472b84727bac2f17d334b3c69dc0419f06bf1ab83a SHA256 (FreeBSD-7.3-RC2-amd64-docs.iso) = 2a165e5b8cc66fac8e7b93cc4f62f216bc300e13f4200ba5227eeae0c65e5aee SHA256 (FreeBSD-7.3-RC2-amd64-dvd1.iso) = 63e5aa48e4e3a18b36e2b92fe840ef5d6212e3aa19aa1b290ed2edcf6ccc2779 SHA256 (FreeBSD-7.3-RC2-amd64-livefs.iso) = 8032e740d3064a0c1011182f8ce783c2bbae8c8b56fa6e9a730c5857f808e692 SHA256 (FreeBSD-7.3-RC2-i386-bootonly.iso) =
Re: 7.3-RC2 Available...
On 03/04/10 07:15, Ken Smith wrote: The third and what should be last of the test builds for the 7.3-RELEASE cycle, 7.3-RC2, is available for amd64, i386, pc98, and sparc64 architectures. The target schedule as well as the current status of the release is available here: ...snipped... Good news, certainly. Will 7.3R include the gmirror improvements that were missed by 8.0R but that are in 8-STABLE? I have a couple servers using 7.2R and having those improvements in 7.3 would let me avoid the jump to 8-STABLE. Or is a buildworld from 7.2 to 8.x straightforward and safe? Thanks also to the FreeBSD team for their continued hard work. Regards, r ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
route -cloning flag
Hi, How can I simulate 'route add -net 1.1.1.1/32 -cloning -iface fxp0' on FreeBSD 8.x because it appears that somebody has axed cloning ? And no it does NOT work without -cloning. And I don't really want to argue if it is correct or not - It worked not it doesn't ;) Regards, Iasen. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: route -cloning flag
On Thu, 2010-03-04 at 17:28 +0200, Iasen Kostov wrote: Hi, How can I simulate 'route add -net 1.1.1.1/32 -cloning -iface fxp0' on FreeBSD 8.x because it appears that somebody has axed cloning ? And no it does NOT work without -cloning. And I don't really want to argue if it is correct or not - It worked not it doesn't ;) Regards, Iasen. Hum when I actually got to the machine and added the route it worked without -cloning. I can Only guess that the on site support did something wrong but I really don't know what mistake can they make in that simple command (route add -net 1.1.1.1/32 -iface fxp0) ;) . I hope it will still works after reboot ... And the man page is wrong, It still lists -cloning as valid option, with that in mind and remote server one can easily lock himself out :( Regards, Iasen. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mbuf leakage with nfs/udp (was mbuf leakage with nfs/zfs?)
On Thu, 4 Mar 2010, Daniel Braniss wrote: correct. The interesting side effect, is that I can't see any negative issues when disabling the cash. If the client retries a non-idempotent RPC, the server will do it again, which can result in data corruption. This is likely to happen infrequently, but with potentially nasty results. (The paper that describes this was given at a late 1980s Usenix by Chet J. His name is in a comment somewhere, I think. I won't dare to try and spell it.:-) seems ok, I have been running it now on a semi production server and it's holding up quiet nicely, the cache seems not up to expectations: store-mg-03# nfsstat -se Server Info: Getattr SetattrLookup Readlink Read WriteCreateRemove 48176764262687 12582599 19732 4225907 9186574780793818837 Rename Link Symlink Mkdir Rmdir Readdir RdirPlusAccess 7623 160 27753 59551 59552118216 0 1992779 MknodFsstatFsinfo PathConfCommit LookupP SetClId SetClIdCf 097900519 0 1644267 0 0 0 Open OpenAttr OpenDwnGr OpenCfrm DelePurge DeleRet GetFH Lock 0 0 0 0 0 0 0 0 LockT LockU CloseVerify NVerify PutFH PutPubFH PutRootFH 0 0 0 0 0 0 0 0 Renew RestoreFHSaveFH Secinfo RelLckOwn V4Create 0 0 0 0 0 0 Server: RetfailedFaults Clients 0 0 0 OpenOwner Opens LockOwner LocksDelegs 0 0 0 0 0 Server Cache Stats: Inprog Idem Non-idemMisses CacheSize TCPPeak 307 0 297 80943198 0 0 If you are referring to the high miss rate, that is normal and to be expected. It's the 297 Non-idempotent hits that could have caused data corruption without the cache. When there is a hit, the RPC reply comes from the cache, so that the RPC isn't performed again on the server. (Some/many of these are not harmful. For example, a retried Remove simply fails with ENOENT, but others...) Glad to hear that the experimental server is working ok for you, rick ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mbuf leakage with nfs/zfs?
On Tue, 2 Mar 2010, Daniel Braniss wrote: just keep sending insights/pointers and enjoy life You could try this patch for sys/rpc/replay.c. Completely untested and just typed into email (so don't give it to patch, just edit the file). - try adding these 2 lines just before the end of replay_setreply() in sys/rpc/replay.c: - } + } else if (m) + m_freem(m); mtx_unlock(rc-rc_lock); } It's the only place I can see in replay.c that might leak, rick ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
History of Stats Id:8514582
Erec b tile dysfu gw nction (ED) or (male) impo l tence is a sex thp ual dysfun a ction characterized by the inability to develop or main f tain an erect pqwpz ion of the pe fsyw nis. There are various under tl lying causes, such as cardi lyqo ovascular leakage and diab yiiie etes, many of which are medi gcx cally trea pqsjeu table.3 different tablets are currently avai uf lable from the doc cm tor and these work when there is se yrniwj xual stimul q ation. Depe nmb nding on the treatment, it will need to be taken 20 minutes to 1 hour before se pm x and the period of time over which it works can vary between 3 hours and up to 36 hours.Via txeerm gra Silde aemios nafil 50/100mg $1.42 Per P qhn ill More info Cia izaorf lis Tada xd lafil 10/20mg $1.66 Per P fiemg ill More info Levi kpmszj tra Vard lkrc enafil 20mg $1.72 Per P nef ill More info Prop q ecia Finas qbshqf teride 1/5mg $0.56 Per P lueodv ill More info Cas bt odex Bical qkwfxz utamide 50mg $4.76 Per P jvys ill More info Cia ggbdos lis So xlzuiu ft Tada xjx lafil 20mg $1.72 Per P ln ill More info Eul mhzatk exin Flut yvtatm amide 250 lwyh mg $2.33 Per P bvgtk ill More info Flo tv max Tams s ulosin 0.2/0.4mg $1.00 Per P ndydh ill More info Kama vop gra Silde u nafil 100mg $2.12 Per P afoce ill More info Kama iog gra Oral Jelly Silde dfw nafil 100mg $3.44 Per P gyuwsx ill More info Kef u lex Ceph lazzdk alexin 250/500/750mg $0.81 Per P btrno ill More info Via a gra Silden cq afil 50/100mg $1.42 Per P ilvcru ill More info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: route -cloning flag
One thing is sure. the route won't survive a reboot. Guess you can add it to rc.conf but I have never tried it. On Thu, Mar 4, 2010 at 5:04 PM, Iasen Kostov tb...@otel.net wrote: On Thu, 2010-03-04 at 17:28 +0200, Iasen Kostov wrote: Hi, How can I simulate 'route add -net 1.1.1.1/32 -cloning -iface fxp0' on FreeBSD 8.x because it appears that somebody has axed cloning ? And no it does NOT work without -cloning. And I don't really want to argue if it is correct or not - It worked not it doesn't ;) Regards, Iasen. Hum when I actually got to the machine and added the route it worked without -cloning. I can Only guess that the on site support did something wrong but I really don't know what mistake can they make in that simple command (route add -net 1.1.1.1/32 -iface fxp0) ;) . I hope it will still works after reboot ... And the man page is wrong, It still lists -cloning as valid option, with that in mind and remote server one can easily lock himself out :( Regards, Iasen. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mbuf leakage with nfs/zfs?
On Tue, 2 Mar 2010, Daniel Braniss wrote:
just keep sending insights/pointers and enjoy life
You could try this patch for sys/rpc/replay.c. Completely untested and
just typed into email (so don't give it to patch, just edit the file).
- try adding these 2 lines just before the end of replay_setreply() in
sys/rpc/replay.c:
- }
+ } else if (m)
+ m_freem(m);
mtx_unlock(rc-rc_lock);
}
It's the only place I can see in replay.c that might leak, rick
this is what I did:
--- a/sys/rpc/replay.c Mon Mar 01 18:29:54 2010 +0200
+++ b/sys/rpc/replay.c Fri Mar 05 09:24:17 2010 +0200
@@ -243,6 +243,9 @@
rce-rce_repbody = m;
if (m)
rc-rc_size += m_length(m, NULL);
+ } else if (m) {
+printf(free m=%p ...\n, m);
+m_freem(m);
}
mtx_unlock(rc-rc_lock);
}
but it didn't help, it's not triggered
Thanks for the explanation on the cache, things are begining to make sense.
If I understand, the reason for this cache is to prevent re-applying an
already performed rpc, which could lead to data corruption
btw, the list of CCs is rather big, so if anyone feels he rather be removed,
please let me know.
cheers,
danny
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
