similar to: kmem_map too small: 260046848 total allocated

While trying to speed up nanobsd builds, I mounted /usr/obj on a ramdisk and found my box crashing. Thinking it might be hardware, I tried a separate machine, but with the same results. I have 4G of ram (i386). Am I just running out of some kernel memory ? If so, is there anything I can adjust to prevent this, yet still use mfs in this way ? mdconfig -a -t malloc -s 1800M newfs /dev/md0

We have 10 SuperMicro PDSMi+ 5015M-MTs that are panic'ing every few days. This started shortly after upgrade from 6.2-RELEASE to 6.3-RELEASE with freebsd-update. Other than switching to a debugging kernel, a little sysctl tuning, and patching with freebsd-update, they are stock. The debugging kernel was built from source that is also being patched with freebsd-update. These systems are

Hi. I've recently borrowed a SuperMicro 6013P-8 from a vendor for the purposes of testing it to see if FreeBSD and these machines will make a good replacements for our current flock of 11 Netra T1s running solaris. Things are going very well with the tests, with the glaring exception of the following crash: While doing some significant disk operations: du, deleting a different part of the

I'm seeing a condition on FreeBSD 9.1 (built October 24th) where I/O seems to hang on any local zpools after several hours of hosting a large-ish Postgres database. The database occupies about 14TB of a 38TB zpool with a single SSD ZIL. The OS is on a ZFS boot disk. The system also has 24GB of physical memory. Smartmon tools reports no errors on any disks attached to the system, and IPMI

Guys, I've heard about some absurd RAM requirements for 9.1, has anybody tested it? e.g. http://forums.freebsd.org/showthread.php?t=36314 -- View this message in context: http://freebsd.1045724.n5.nabble.com/9-1-minimal-ram-requirements-tp5771583.html Sent from the freebsd-stable mailing list archive at Nabble.com.

Just trying to understand if anything might be going on with this crash dump or just faulty hardware ? dmesg at the end ---Mike # gdb -k /kernel.debug vmcore.0 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type

Did cvsup on a machine that does just mail processing (well, a lot of spam scanning) and it crashed not too much later. This kernel does not include MFC src/sys/kern/sys_process.c revisions 1.111 and 1.112: Use kmem_alloc_nofault() rather than kmem_alloc_pageable() in procfs_rwmem(). Use vm_page_hold() in place of vm_page_wire() since the page can be freed. Don't hold extra

Andre, Are you going to have time to MFC things from -current for auto-tuning -stable before 9.2? I fear (maybe unnecessarily?) that we are about to ship yet another release that can't do basic 10gigE when sufficient memory exists. If you don't have time, then let me know and I'll see what I can do. -- Alfred Perlstein VP Software Engineering, iXsystems

Hi, Running 9.2-PRERELEASE #19 r253313 I got the following panic Fatal trap 12: page fault while in kernel mode cpuid = 22; apic id = 46 fault virtual address = 0xffffff827ebca30c fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff81983055 stack pointer = 0x28:0xffffffcf75bd60a0 frame pointer = 0x28:0xffffffcf75bd68f0

Hello Ivan, 'FastCopy' has an option to revise max I/O size and works for SMB :) it is a tool for file transferring and could be installed to win10, download here: https://fastcopy.jp/ This is an example for writing, a job would write a file named '1GB.img' from a local disk 'H:' to a remote SMB mounted net disk 'Z:', open 'FastCopy' tool and specify

At office, using the internal LAN at my disposal, I'm having a go at parallel computing - to begin with - with pvm, rpvm & snow. The two boxes are as follows Remote machine uffbsd: CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz (1994.13-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 real memory = 260046848 (248 MB) This machine NbBSD: CPU: Mobile Intel(R)

Hi list, since we activated 10gbe on ixgbe cards + jumbo frames(9k) on 9.0 and now on 9.1 we recognize that after a random period of time, sometimes a week, sometimes only a day, the system doesn't send any packets out. The phenomenon is that you can't login via ssh, nfs and istgt is not operative. Yet you can login on the console and execute commands. A clean shutdown isn't possible

Hello, The Xen community is working on a new virtualization mode (or maybe I should say an extension of HVM) to be able to run PV guests inside HVM containers without requiring a device-model (Qemu). One of the advantages of this new virtualization mode is that now it is much more easier to port guests to run under it (as compared to pure PV guests). Given that FreeBSD already supports

On Wed, Aug 16, 2023 at 04:02:47PM +0100, Ivan Clayson via samba wrote: >Hello, > >We are currently running a Linux Samba gateway with a CephFS >kernel-client to allow Windows 10 clients to transfer data to and from >our Ceph storage cluster. We have been using this in production for a >while now quite successfully but we are finding that our Windows >clients are having

On Fri, Aug 18, 2023 at 04:25:28PM +0000, Jones Syue ??? wrote: >Hello Ivan, > >'FastCopy' has an option to revise max I/O size and works for SMB :) >it is a tool for file transferring and could be installed to win10, >download here: https://fastcopy.jp/ > >This is an example for writing, a job would write a file named '1GB.img' >from a local disk

Hi. Just migrated to zfs on opensolaris. I copied data to the server using rsync and got this message: Oct 10 17:24:04 zetta ^Mpanic[cpu1]/thread=ffffff0007f1bc80: Oct 10 17:24:04 zetta genunix: [ID 683410 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff0007f1b640 addr=fffffffecd873000 Oct 10 17:24:04 zetta unix: [ID 100000 kern.notice] Oct 10 17:24:04 zetta unix: [ID 839527 kern.notice]