Re: Maximum memory allocation per process
On Thu, 22 May 2008 06:38:19 -0700, Jeremy Chadwick wrote: > You need to modify some kernel settings via /boot/loader.conf and > reboot. Here's what we use on our production RELENG_6 and RELENG_7 > boxes: > > # Increase maximum allocatable memory on a process to 2GB. > # (We don't choose 3GB (our max RAM) since that would > # exhaust all memory, and result in a kernel panic.) > # Set default memory size as 768MB. > # Maximum stack size is 256MB. > # > kern.maxdsiz="2048M" > kern.dfldsiz="768M" > kern.maxssiz="256MB" for those of us who're booting off a stripped down freebsd and are not using the 4th routines, are the above to be set before 'load /kernel' or after 'load /kernel' ? currently, loader.rc contains, --- cut here --- set console=comconsole set hw.ata.atapi_dma="0" set hw.ata.ata_dma="0" set hw.ata.wc="0" load /kernel load -t mfs_root /mfsroot boot --- cut here --- -- Regards, /\_/\ "All dogs go to heaven." [EMAIL PROTECTED](0 0) http://www.openmalaysiablog.com/ +==oOO--(_)--OOo==+ | for a in past present future; do| | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=+ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Maximum memory allocation per process
On Fri, May 30, 2008 at 01:58:14PM +0800, Dinesh Nair wrote: > On Thu, 22 May 2008 06:38:19 -0700, Jeremy Chadwick wrote: > > You need to modify some kernel settings via /boot/loader.conf and > > reboot. Here's what we use on our production RELENG_6 and RELENG_7 > > boxes: > > > > # Increase maximum allocatable memory on a process to 2GB. > > # (We don't choose 3GB (our max RAM) since that would > > # exhaust all memory, and result in a kernel panic.) > > # Set default memory size as 768MB. > > # Maximum stack size is 256MB. > > # > > kern.maxdsiz="2048M" > > kern.dfldsiz="768M" > > kern.maxssiz="256MB" > > for those of us who're booting off a stripped down freebsd and are not > using the 4th routines, are the above to be set before 'load /kernel' or > after 'load /kernel' ? > > currently, loader.rc contains, > > --- cut here --- > set console=comconsole > set hw.ata.atapi_dma="0" > set hw.ata.ata_dma="0" > set hw.ata.wc="0" > load /kernel > load -t mfs_root /mfsroot > boot > --- cut here --- I believe these would either need to be set *before* loading the kernel, or, possibly it doesn't matter at all (they might be passed to the kernel itself during "boot"). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Pahole on freebsd
Hello Hackers, I have searched online to find the pahole utility for freebsd. Do we have a pahole utility for freebsd? If yes, can some one point me to the correct location from where i can download. Thanks, Vasanth ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Maximum memory allocation per process
Dinesh Nair wrote: > for those of us who're booting off a stripped down freebsd and are not > using the 4th routines, are the above to be set before 'load /kernel' or > after 'load /kernel' ? It doesn't matter. The tunables are passed to the kernel when it is booted. In fact, the standard beastie.4th stuff loads the kernel before displaying the menu, so the settings happen after the kernel is loaded. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Being really good at C++ is like being really good at using rocks to sharpen sticks." -- Thant Tessman ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CFT: adding configuration file support to pkg_install
This adds support for /etc/pkg.conf configuration file. Also, this adds support for naive multi-site package fetching. Any comment welcome (and appreciated). Patch is here: http://people.freebsd.org/~flz/local/ports/pkg-install-config.diff Tarball is here: http://people.freebsd.org/~flz/local/ports/pkg-install-0a553aac.tar.bz2 -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RAID status issues with Intel MatrixRAID ataraid
This isn't a bug report, just a heads up to anyone using the same setup. This occurred in production, and I don't currently have a non-production hardware on which to investigate this bug and/or create a patch. In certain conditions, even though the Firmware RAID BIOS, says that a RAID is degraded, the FreeBSD driver thinks it's business as usual. In my case this resulted in file system corruption. Relevant output below. FreeBSD version: 6.3-RELEASE-p2 Cheers, Stef Walter BIOS OUTPUT: Copyright(C) 2003-06 Intel Corporation. All Rights Reserved. RAID Volumes: ID NameLevel Strip Size StatusBootable 0RAID Set 1 RAID1(Mirror) N/A465.8GB Degraded Yes 1RAID1(Mirror) N/A465.8GB NormalYes Physical Disks: Port Drive Model Serial # Size Type/Status(Vol ID) 0WDC WD5000ABYS-0 WD-WCAPW5637184 465.8GB Member Disk(0) 1ST3500320NS 5QM09E6F 465.8GB Error Occurred(0) 2WDC WD5000ABYS-0 WD-WCAPW5548822 465.8GB Member Disk(1) 3ST3500320NS 5QM0991D 465.8GB Member Disk(1) Press to enter Configuration Utility... RELEVANT SNIPPET FROM DMESG: ar0: 476937MB status: READY ar0: disk0 READY (master) using ad4 at ata2-master ar0: disk1 READY (mirror) using ad6 at ata3-master ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RAID status issues with Intel MatrixRAID ataraid
On Fri, May 30, 2008 at 09:03:48PM +, Stef Walter wrote: > This isn't a bug report, just a heads up to anyone using the same setup. > This occurred in production, and I don't currently have a non-production > hardware on which to investigate this bug and/or create a patch. > > In certain conditions, even though the Firmware RAID BIOS, says that a > RAID is degraded, the FreeBSD driver thinks it's business as usual. In > my case this resulted in file system corruption. Relevant output below. See the "ATA (SATA, PATA, ATAPI)" section, specifically the Intel MatrixRAID items: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RAID status issues with Intel MatrixRAID ataraid
On Friday 30 May 2008 05:03:48 pm Stef Walter wrote: > This isn't a bug report, just a heads up to anyone using the same setup. > This occurred in production, and I don't currently have a non-production > hardware on which to investigate this bug and/or create a patch. > > In certain conditions, even though the Firmware RAID BIOS, says that a > RAID is degraded, the FreeBSD driver thinks it's business as usual. In > my case this resulted in file system corruption. Relevant output below. > > FreeBSD version: 6.3-RELEASE-p2 > > Cheers, > Stef Walter > > > > BIOS OUTPUT: > > Copyright(C) 2003-06 Intel Corporation. All Rights Reserved. > > RAID Volumes: > ID NameLevel Strip Size StatusBootable > 0RAID Set 1 RAID1(Mirror) N/A465.8GB Degraded Yes > 1RAID1(Mirror) N/A465.8GB NormalYes > > Physical Disks: > Port Drive Model Serial # Size Type/Status(Vol ID) > 0WDC WD5000ABYS-0 WD-WCAPW5637184 465.8GB Member Disk(0) > 1ST3500320NS 5QM09E6F 465.8GB Error Occurred(0) > 2WDC WD5000ABYS-0 WD-WCAPW5548822 465.8GB Member Disk(1) > 3ST3500320NS 5QM0991D 465.8GB Member Disk(1) > Press to enter Configuration Utility... > > > > RELEVANT SNIPPET FROM DMESG: > > ar0: 476937MB status: READY > ar0: disk0 READY (master) using ad4 at ata2-master > ar0: disk1 READY (mirror) using ad6 at ata3-master Err, you have two RAID volumes, one degraded, and one ok. ar0 is apparently the one that is ok (drives 2 and 3). What is more odd is that it isn't seeing a RAID config at all for ad0 and ad2 (drives 0 and 1). -- John Baldwin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RAID status issues with Intel MatrixRAID ataraid
Jeremy Chadwick wrote: >> In certain conditions, even though the Firmware RAID BIOS, says that a >> RAID is degraded, the FreeBSD driver thinks it's business as usual. In >> my case this resulted in file system corruption. Relevant output below. > > See the "ATA (SATA, PATA, ATAPI)" section, specifically the Intel > MatrixRAID items: > > http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Yes, I reported several of those as well as provided patches for them. That was back when I had relevant hardware in my lab. Cheers, Stef Walter ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Is there any way to increase the KVM?
Hi, Our nfs server is running 7-stable/amd64 with 8G ram, the size of zfs pool is 12T. We have set vm.kmem_size and vm.kmem_size_max to 1.5G, but the kernel still panics by "kmem_map too small" often. According to [1], the limitation is not only by the loader (is it fixed now?) but also by the default layout of KVM. [2] points a way to increase the KVM, but we get the similar linking error. Is there any standard way to modify the layout of KVM? For example, we may want to set KVM to 6G and leave the 2G for user space usage. Thanks, Tz-Huan [1] http://lists.freebsd.org/pipermail/freebsd-current/2007-October/077964.html [2] http://lists.freebsd.org/pipermail/freebsd-current/2008-March/084325.html ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
