panic: rtqkill route really not free on freebsd 8.0-release update
Hi, all We add kdb/ddb and extra panic info printing into kernel and catch this panic again. We have instrumented the kernel and found that this panic happens when draining == 1, but seems to be confused with the fact that all access to radix trees are protected by locks. Can anyone familiar with these code shed us some light on this? below is url to screenshot in ddb: http://www.delphij.net/zhao/1.png http://www.delphij.net/zhao/2.png -- The Power to Serve ___ 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: panic: rtqkill route really not free on freebsd 8.0-release
I worte: Hi all, I have four heavy load mysql database servers which system is 8.0-release got "panic: rtqkill route really not free" this week. We have a gateway set up by OpenBSD have a icmp route redirect function between two subnets, I suspect the FreeBSD panic at trying to delete routes sent from that gateway. So I set sysctl net.inet.icmp.drop_redirect=1, no more panic in past 24 hours. I guess maybe miss some locks or wrong delete route path in 8.0-release. Did any one meet this problem before? After four days research we think the problem is between function in_matroute and in_rtqkill. This two functions' conflicted at processing RTPRF_OURS flag routes. In my opinion, it is a design problem, so I have no idea about how to resolve it. The simple way I think is change the panic assert in in_rtqkill, treat it as a normal state not assert a panic. -- The Power to Serve ___ 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"
panic: rtqkill route really not free on freebsd 8.0-release
Hi all, I have four heavy load mysql database servers which system is 8.0-release got "panic: rtqkill route really not free" this week. We have a gateway set up by OpenBSD have a icmp route redirect function between two subnets, I suspect the FreeBSD panic at trying to delete routes sent from that gateway. So I set sysctl net.inet.icmp.drop_redirect=1, no more panic in past 24 hours. I guess maybe miss some locks or wrong delete route path in 8.0-release. Did any one meet this problem before? -- The Power to Serve ___ 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"
The USB flash driver can't mount as root on 8.1-prerelease boot
Hi, all I have a box with a Intel DG45FC motherboard. I use a usb stick as root of freebsd 8-stable, but I found it can not mount root in most interface of my box after kernel initialized. There is only way I can use it: plug usb stick and my usb keyboard into two front usb socket at same time. Any other way for example plug keyboard at back socket or plug usb stick at back socket, will stop at mountroot> prompt. I wonder is that can't mount usb root problem still unresolved on 8.1-prerelease? -- The Power to Serve ___ 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: 8.0-RC3 Available
在 Fri, 13 Nov 2009 16:42:44 +0800，Chao Shin 写道: Hi All, Is sysinstall can work now? After I set Label in sysinstall it has message come out said "Unable to find device node for /dev/ad4s1b in /dev! The creation of filesystems will be aborted." and installation aborted. I have installed freebsd with sysinstall ten years, that is first time I meet that I found the reason of that. I've fdisk that disk with dd mode before, the sysinstall can't overwrite the partition record, so can't label on it. If I want to install 8.0-rc3 on that disk, I have to erase the partition record with "dd if=/dev/zero of=/dev/ad4 bs=1M count=1" before installation. -- The Power to Serve ___ 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: 8.0-RC3 Available
Hi All, Is sysinstall can work now? After I set Label in sysinstall it has message come out said "Unable to find device node for /dev/ad4s1b in /dev! The creation of filesystems will be aborted." and installation aborted. I have installed freebsd with sysinstall ten years, that is first time I meet that my box is dell's optiplex 745, I've installed 7.2R on it without any problem before. The third and hopefully last of the Release Candidates for the FreeBSD 8.0 release cycle is now available. Unless something catastrophic comes up within the next couple of days we will begin the final builds for 8.0-RELEASE. There is one known issue with the igb(4) driver we are still deciding whether or not to fix as part of 8.0-RELEASE versus doing an Errata Notice for it some time after the release is out. It has been patched in head, and the SVN commit for it is r199192. If any of you are able to give that patch a try on a machine with the igb(4) NIC it would be appreciated. If you notice problems you can report them through the normal Gnats PR system or on the freebsd-current mailing list. I do cross-post announcements to freebsd-stable because this particular release is "about to become a stable branch" but when it comes to watching for issues related to the release most of the developers pay more attention to the freebsd-current list. ISO images for all supported architectures are available on the FTP sites, and a "memory stick" image is available for amd64/i386 architectures. For amd64/i386 architectures the cdrom and memstick images include the documentation packages but no other packages. The DVD image includes the packages that will probably be available on the official release media but is subject to change between now and release. For sparc64 there is now a livefs cdrom, disc1 includes the documentation packages, and the DVD image has the set of packages that currently build for sparc64 (which is a sub-set of the set provided for amd64/i386). If you are using csup/cvsup methods to update an older system the branch tag to use is RELENG_8_0. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, 7.1-RELEASE, 7.2-RELEASE, 8.0-BETA1, 8.0-BETA2, 8.0-BETA3, 8.0-BETA4, 8.0-RC1 or 8.0-RC2 can upgrade as follows: # freebsd-update upgrade -r 8.0-RC3 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. Systems running 8.0-BETA3 may print the warning INDEX-OLD.all: Invalid arguments when downloading updates; this warning is a harmless bug (fixed in 8.0-BETA4) and can be safely ignored. # 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: # freebsd-update install At this point, users of systems being upgraded from FreeBSD 8.0-BETA2 or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. See: http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html for mode details. After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries: # freebsd-update install Finally, reboot into 8.0-RC3: # shutdown -r now MD5/SHA256 checksums for the image files: MD5 (8.0-RC3-amd64-bootonly.iso) = 641881caa82ea85c118bc15fff12fce6 MD5 (8.0-RC3-amd64-disc1.iso) = 854c273b89792cd0366d5399df1034eb MD5 (8.0-RC3-amd64-dvd1.iso) = 9bd1bb2507bc2a3037bc321bb2724bd6 MD5 (8.0-RC3-amd64-livefs.iso) = c5f427c8bf823e10a5348935cec2d7ee MD5 (8.0-RC3-amd64-memstick.img) = 6af9e213914a58a5779715ae5882bd25 MD5 (8.0-RC3-i386-bootonly.iso) = dfaec92ae358ab780d317aa66482ca9e MD5 (8.0-RC3-i386-disc1.iso) = 460f6cfddaebee6ae59a7d5f73695246 MD5 (8.0-RC3-i386-dvd1.iso) = 98d3f65f2444a8745f787df5ce9e1f0c MD5 (8.0-RC3-i386-livefs.iso) = 5184b7f6403d1d24991533bde0e580ff MD5 (8.0-RC3-i386-memstick.img) = 8774ef1d6bdf541e440f2f8ed22a2493 MD5 (8.0-RC3-ia64-bootonly.iso) = fd0af8f34937cf7fc78ea0063252afb7 MD5 (8.0-RC3-ia64-disc1.iso) = 96313c25e53fc333c258ed675007f3d7 MD5 (8.0-RC3-ia64-disc2.iso) = 235714607a2805c396ece829839405be MD5 (8.0-RC3-ia64-disc3.iso) = 53fca9243ccc788190ca58d24f363cbe MD5 (8.0-RC3-ia64-dvd1.iso) = 4e24736ab50bc2227c72dbeab6869266 MD5 (8.0-RC3-ia64-livefs.iso) = b6d76cf77ed714631bf714ff78b8e950 MD5 (8.0-RC3-pc98-bootonly.iso) = 137d17ec3830b6ae831b6fb48adf86e0 MD5 (8.0-RC3-pc98-disc1.iso) = 3624b1f7b3a659a7454718e38b9a1ee0 MD5 (8.0-RC3-pc98-livefs.iso) = 29ed3786b2df1c2e72e45d1187f3e788 MD5 (8.0-RC3-powerpc-bootonly.iso) = e7d8508639dee4aed5e52a24d6e27
Re: 8.0-RC3 Available
Hi All, Is sysinstall can work now? After I set Label in sysinstall it has message come out said "Unable to find device node for /dev/ad4s1b in /dev! The creation of filesystems will be aborted." and installation aborted. I have installed freebsd with sysinstall ten years, that is first time I meet that The third and hopefully last of the Release Candidates for the FreeBSD 8.0 release cycle is now available. Unless something catastrophic comes up within the next couple of days we will begin the final builds for 8.0-RELEASE. There is one known issue with the igb(4) driver we are still deciding whether or not to fix as part of 8.0-RELEASE versus doing an Errata Notice for it some time after the release is out. It has been patched in head, and the SVN commit for it is r199192. If any of you are able to give that patch a try on a machine with the igb(4) NIC it would be appreciated. If you notice problems you can report them through the normal Gnats PR system or on the freebsd-current mailing list. I do cross-post announcements to freebsd-stable because this particular release is "about to become a stable branch" but when it comes to watching for issues related to the release most of the developers pay more attention to the freebsd-current list. ISO images for all supported architectures are available on the FTP sites, and a "memory stick" image is available for amd64/i386 architectures. For amd64/i386 architectures the cdrom and memstick images include the documentation packages but no other packages. The DVD image includes the packages that will probably be available on the official release media but is subject to change between now and release. For sparc64 there is now a livefs cdrom, disc1 includes the documentation packages, and the DVD image has the set of packages that currently build for sparc64 (which is a sub-set of the set provided for amd64/i386). If you are using csup/cvsup methods to update an older system the branch tag to use is RELENG_8_0. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, 7.1-RELEASE, 7.2-RELEASE, 8.0-BETA1, 8.0-BETA2, 8.0-BETA3, 8.0-BETA4, 8.0-RC1 or 8.0-RC2 can upgrade as follows: # freebsd-update upgrade -r 8.0-RC3 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. Systems running 8.0-BETA3 may print the warning INDEX-OLD.all: Invalid arguments when downloading updates; this warning is a harmless bug (fixed in 8.0-BETA4) and can be safely ignored. # 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: # freebsd-update install At this point, users of systems being upgraded from FreeBSD 8.0-BETA2 or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. See: http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html for mode details. After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries: # freebsd-update install Finally, reboot into 8.0-RC3: # shutdown -r now MD5/SHA256 checksums for the image files: MD5 (8.0-RC3-amd64-bootonly.iso) = 641881caa82ea85c118bc15fff12fce6 MD5 (8.0-RC3-amd64-disc1.iso) = 854c273b89792cd0366d5399df1034eb MD5 (8.0-RC3-amd64-dvd1.iso) = 9bd1bb2507bc2a3037bc321bb2724bd6 MD5 (8.0-RC3-amd64-livefs.iso) = c5f427c8bf823e10a5348935cec2d7ee MD5 (8.0-RC3-amd64-memstick.img) = 6af9e213914a58a5779715ae5882bd25 MD5 (8.0-RC3-i386-bootonly.iso) = dfaec92ae358ab780d317aa66482ca9e MD5 (8.0-RC3-i386-disc1.iso) = 460f6cfddaebee6ae59a7d5f73695246 MD5 (8.0-RC3-i386-dvd1.iso) = 98d3f65f2444a8745f787df5ce9e1f0c MD5 (8.0-RC3-i386-livefs.iso) = 5184b7f6403d1d24991533bde0e580ff MD5 (8.0-RC3-i386-memstick.img) = 8774ef1d6bdf541e440f2f8ed22a2493 MD5 (8.0-RC3-ia64-bootonly.iso) = fd0af8f34937cf7fc78ea0063252afb7 MD5 (8.0-RC3-ia64-disc1.iso) = 96313c25e53fc333c258ed675007f3d7 MD5 (8.0-RC3-ia64-disc2.iso) = 235714607a2805c396ece829839405be MD5 (8.0-RC3-ia64-disc3.iso) = 53fca9243ccc788190ca58d24f363cbe MD5 (8.0-RC3-ia64-dvd1.iso) = 4e24736ab50bc2227c72dbeab6869266 MD5 (8.0-RC3-ia64-livefs.iso) = b6d76cf77ed714631bf714ff78b8e950 MD5 (8.0-RC3-pc98-bootonly.iso) = 137d17ec3830b6ae831b6fb48adf86e0 MD5 (8.0-RC3-pc98-disc1.iso) = 3624b1f7b3a659a7454718e38b9a1ee0 MD5 (8.0-RC3-pc98-livefs.iso) = 29ed3786b2df1c2e72e45d1187f3e788 MD5 (8.0-RC3-powerpc-bootonly.iso) = e7d8508639dee4aed5e52a24d6e27b69 MD5 (8.0-RC3-powerpc-disc1.iso) = 1016ae7753db153b7be0f5d167f595b9 MD5 (8.0-RC3-power
Re: 8.0-RC1 Available
The first of the Release Candidates for the FreeBSD 8.0 release cycle is now available. How many RC's we have will depend on how well 8.0-RC1 does. At the moment only one more RC is on the schedule but odds are fairly high we will wind up inserting at least one more RC. Between BETA4 and RC1 a lot of work has gone into IPv6 issues as well as many other issues that have been brought up from the public testing. And a patch set was committed by the people who handle porting ZFS to FreeBSD that they felt makes ZFS production-ready. Details about the current target schedule along with much more detail about the current status of the release is available here: http://wiki.freebsd.org/8.0TODO There are two known problems with 8.0-RC1. One known issue with the 8.0-RC1 build was discovered after the builds got started so is not part of the ISO images or FreeBSD-Update builds. The issue is that local IPv6 link-local addresses are not reachable. A fix for it has been committed to RELENG_8 so if you install from the 8.0-RC1 media or update using FreeBSD-Update you will then need to update using csup/cvsup mechanisms if you need that fix for your environment. It should only impact people using IPv6. The other known issue is that the flowtable may direct packets to the wrong interface under certain routing conditions. We feel confident that this bug will be fixed so the flowtable is enabled in RC1 to maximize testing. If you experience routing problems, please temporarily disable the flowtable using the sysctl =0 and report the results to the freebsd-current@ mailing list. If we are unable to resolve this issue by RC2, we will disable the flowtable in 8.0-RELEASE. If you notice problems you can report them through the normal Gnats PR system or on the freebsd-current mailing list. I do cross-post announcements to freebsd-stable because this particular release is "about to become a stable branch" but when it comes to watching for issues related to the release most of the developers pay more attention to the freebsd-current list. ISO images for all supported architectures are available on the FTP sites, and a "memory stick" image is available for amd64/i386 architectures. For amd64/i386 architectures the cdrom and memstick images include the documentation packages this time but no other packages. The DVD image includes a rough pass at what packages will be available on the official release media but is subject to change between now and release. For sparc64 the DVD image has the set of packages that currently build for sparc64, which is a sub-set of the set provided for amd64/i386. The sparc64 disc1 does not have any packages on it because I noticed a little too late that adding the doc packages to disc1 caused it to overflow the target size. For 8.0-RC2 sparc64 will have the livefs bits split out to a separate image (which is the way all the other architectures have been for a while now) and the doc packages will be provided on disc1. None of the other images include packages. If you are using csup/cvsup methods to update an older system the branch tag to use is RELENG_8. The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.0-RELEASE, 7.1-RELEASE, 7.2-RELEASE, 8.0-BETA1, 8.0-BETA2, 8.0-BETA3, or 8.0-BETA4 can upgrade as follows: # freebsd-update upgrade -r 8.0-RC1 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. Systems running 8.0-BETA3 may print the warning INDEX-OLD.all: Invalid arguments when downloading updates; this warning is a harmless bug (fixed in 8.0-BETA4) and can be safely ignored. # 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: # freebsd-update install At this point, users of systems being upgraded from FreeBSD 8.0-BETA2 or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. See: http://www.daemonology.net/blog/2009-07-11-freebsd-update-to-8.0-beta1.html for mode details. After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries: # freebsd-update install Finally, reboot into 8.0-RC1: # shutdown -r now MD5/SHA256 checksums for the image files: MD5 (8.0-RC1-amd64-bootonly.iso) = a84d43c8adaba3fee9a618098668154e MD5 (8.0-RC1-amd64-disc1.iso) = fb4f75c74144239b4994dc3ad040af33 MD5 (8.0-RC1-amd64-dvd1.iso) = 5da3097634fbe049dd01ad4127d0f396 MD5 (8.0-RC1-amd64-livefs.iso) = 43a483ea73cbbe80f0ef068502594363 MD5 (8.0-R
weird sata DMA error
Hi all, I have a dell optiplex 755 box. I plug a second disk on it for backup logs. It always report error message like below when heavy read load. ad9: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1511796863 ad9: TIMEOUT - READ_DMA48 retrying (0 retries left) LBA=1511796863 ad9: FAILURE - READ_DMA48 timed out LBA=1511796863 g_vfs_done():ad9s1d[READ(offset=774039961600, length=16384)]error = 5 ad9: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=1513678143 ad9: TIMEOUT - READ_DMA48 retrying (0 retries left) LBA=1513678143 ad9: FAILURE - READ_DMA48 timed out LBA=1513678143 g_vfs_done():ad9s1d[READ(offset=775003176960, length=16384)]error = 5 We had changed another disk, sata cable, box and upgrade freebsd from 7.1-RELEASE-p5 to 7.2-RELEASE. but error message still come out. I have tried smartctl to send self-test command to disk, but it didn't start test, I have no idea about that now. There is smart message and dmesg below: # smartctl -a /dev/ad9 smartctl version 5.38 [amd64-portbld-freebsd7.2] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD15EADS-00R6B0 Serial Number:WD-WCAVY0256398 Firmware Version: 01.00A01 User Capacity:1,500,301,910,016 bytes Device is:Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is:Thu Jul 9 13:42:22 2009 CST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x85)Offline data collection activity was aborted by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 249)Self-test routine in progress... 90% of test remaining. Total time to complete Offline data collection: (32400) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003)Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01)Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities:(0x303f)SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 198 195 051Pre-fail Always - 20340 3 Spin_Up_Time0x0027 155 144 021Pre-fail Always - 9250 4 Start_Stop_Count0x0032 100 100 000Old_age Always - 22 5 Reallocated_Sector_Ct 0x0033 193 193 140Pre-fail Always - 52 7 Seek_Error_Rate 0x002e 200 200 000Old_age Always - 0 9 Power_On_Hours 0x0032 099 099 000Old_age Always - 904 10 Spin_Retry_Count0x0032 100 253 000Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000Old_age Always - 20 192 Power-Off_Retract_Count 0x0032 200 200 000Old_age Always - 4 193 Load_Cycle_Count0x0032 200 200 000Old_age Always - 18 194 Temperature_Celsius 0x0022 115 100 000Old_age Always - 37 196 Reallocated_Event_Count 0x0032 149 149 000Old_age Always - 51 197 Current_Pending_Sector 0x0032 196 195 000Old_age Always - 1213 198 Offline_Uncorrectable 0x0030 200 196 000Old_age Offline - 0 199 UDMA_CRC_Error_Count0x0032 200 200 000Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 006 006 000Old_age Offline - 38929 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number
Re: ZFS crashes on heavy threaded environment
On Mon, 17 Nov 2008 23:58:35 +0800，Pawel Jakub Dawidek <[EMAIL PROTECTED]> wrote: On Thu, Nov 13, 2008 at 06:53:41PM -0800, Xin LI wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 > > I have included a backtrace output from my colleague who has his hands > on the test environment. Should there is more information necessary > please let us know and we wish to provide help on this. Further datapoint. The system used to run with untuned loader.conf, and my colleague just reported that with the following loader.conf, the problem can be triggered sooner: vm.kmem_size_max=838860800 vm.kmem_size_scale="2" The system is running FreeBSD/amd64 7.1-PRERELEASE equipped with 8GB of RAM with GENERIC kernel. With new ZFS I get: Memory allocation failed:: Cannot allocate memory Is this expected? At first, Congratulations to you, thanks to your works, well done! I used this command on a FreeBSD 7.1-PRERELEASE amd64 box with 8GB mem, isn't got output like that, but kernel panic. Maybe you should lower the threads and file size, for example: /usr/local/bin/iozone -M -e -+u -T -t 64 -S 4096 -L 64 -r 4k -s 2g -i 0 -i 1 -i 2 -i 8 -+p 70 -C Actually, we had used this command to test a 8-current with zfs v12 patch on July, there is no more panic. So we hope zfs v13 can MFC as soon as possible, because we really need it now. -- The Power to Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
