Swapping from a zvol results in a deadman panic
My FreeBSD 10.3-RELEASE-p16 server crashes in the middle of a Poudriere bulk run (see below). This crash happens even if I lower vfs.zfs.arc_max or tweak vm.v_free_min/target/reserved/severe. I'm looking for configuration advice in case I missed something obvious, since this seems to work on Illumos- and Linux-derived O/Ses, but failing that, I'd like to get some advice as to how to go about debugging this. I doubt the deadman timer causes the system to stop responding. It's more likely a race condition elsewhere. The pool itself uses 4k sectors and is geli-encrypted. I configured the swap zvol based on root-on-ZFS install instructions found in the FreeBSD wiki: zfs create -V 6G -o org.freebsd:swap=on -o checksum=off -o compression=off -o dedup=off -o sync=disabled -o primarycache=none zroot/swap The ZoL wiki recommends a slightly different zvol configuration: zfs create -V 4G -b $(getconf PAGESIZE) -o logbias=throughput -o sync=always -o primarycache=metadata -o com.sun:auto-snapshot=false rpool/swap I'm not sure how much of this applies to FreeBSD due to differences in kernel design/implementation. Does anyone have an idea of what might be going on and how I might get this working? last pid: 35097; load averages: 0.54, 4.38, 5.99 up 0+05:23:35 03:27:19 94 processes: 1 running, 89 sleeping, 4 waiting CPU: 0.1% user, 0.0% nice, 0.0% system, 0.0% interrupt, 99.9% idle Mem: 911M Active, 1983M Inact, 979M Wired, 772K Cache, 320K Buf, 14M Free ARC: 220M Total, 12M MFU, 45M MRU, 34M Anon, 6645K Header, 122M Other Swap: 6144M Total, 574M Used, 5570M Free, 9% Inuse panic: I/O to pool 'zroot' appears to be hung on vdev guid 13314812526404996608 at '/dev/da0p3.eli'. cpuid = 0 KDB: stack backtrace: #0 0x8098e3e0 at kdb_backtrace+0x60 #1 0x809510b6 at vpanic+0x126 #2 0x80950f83 at panic+0x43 #3 0x81a3ddd3 at vdev_deadman+0x123 #4 0x81a3dce0 at vdev_deadman+0x30 #5 0x81a3dce0 at vdev_deadman+0x30 #6 0x81a325a5 at spa_deadman+0x85 #7 0x80966c2b at softclock_call_cc+0x17b #8 0x80967054 at softclock+0x94 #9 0x8091c9eb at intr_event_execute_handlers+0xab #10 0x8091ce36 at ithread_loop+0x96 #11 0x8091a53a at fork_exit+0x9a #12 0x80d3be0e at fork_trampoline+0xe Uptime: 1h8m24s -- "The lyf so short, the craft so longe to lerne." ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD and IPMI how-to (was Re: su problem)
Daniel Braniss writes: > just for the record, serial on 8.x works fine! the device naming > has changed from sio to uart, and maybe some features. We use it > on all our servers, even redirecting it where possible via > ILO,IMPI,DRAC. and is great for debuging or saving long trips :-) Would some kind soul point me to a howto for configuring IPMI on FreeBSD? I have a Dell PowerEdge 840 that supports IPMI, but I have no idea how to set it up - either in the BIOS or in FreeBSD. I've messed around with ipmitools a little, but I haven't gotten it to work. Best wishes, Matthew -- I FIGHT FOR THE USERS smime.p7s Description: S/MIME cryptographic signature
RE: FreeBSD root on a geli-encrypted ZFS pool
Fabian Keil writes: > In my opinion protecting ZFS's default checksums (which cover > non-metadata as well) with GEOM_ELI is sufficient. I don't see > what advantage additionally enabling GEOM_ELI's integrity > verification offers. I follow you now. You may be right about the extra integrity checking being redundant with ZFS. > Anyway, it's a test without file system so the ZFS overhead isn't > measured. I wasn't entirely clear about it, but my assumption was > that the ZFS overhead might be big enough to make the difference > between HMAC/MD5 and HMAC/SHA256 a lot less significant. Got it. That also makes sense. I'll put this on my to-test list. > I'm currently using sector sizes between 512 and 8192 so I'm not > actually expecting technical problems, it's just not clear to me > how much the sector size matters and if 4096 is actually the best > value when using ZFS. The geli(8) manual page claims that larger sector sizes lower the overhead of GEOM_ELI keying initialization and encryption/decryption steps by requiring fewer of these compute-intensive setup operations per block. You can think of it in terms of networking, where it makes sense to re-use a TCP connection for multiple HTTP requests, because for small HTTP requests, the bandwidth and latency caused by the TCP three-way handshake overshadows the actual data transfer. -- I FIGHT FOR THE USERS smime.p7s Description: S/MIME cryptographic signature
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: PXE booting issues
Morgan, I had much better luck using PXELINUX to chain-load FreeBSD. I wrote up an article on the subject (http://web.irtnog.org/doc/how-to/freebsd-install-pxe-wds), but the corresponding blog entry might make for a shorter read (http://web.irtnog.org/~xenophon/blog/archive/2007/04/22/struggling-to -boot-freebsd-from-pxelinux). Obviously, you aren't using WDS or RIS, but the principle is the same. Best wishes, Matthew -- "Rogues are very keen in their profession, and know already much more than we can teach them respecting their several kinds of roguery." - A. C. Hobbs in _Locks and Safes_ (1853) smime.p7s Description: S/MIME cryptographic signature
Creating one's own installer/mfsroot
Could anyone recommend a good guide for developing one's own mfsroot images suitable for recovery or scripted installation (not using sysinstall)? It appears that one could develop a simplified network-based installation process based around fdisk, disklabel, newfs, mount_ufs, fetch, and pax, perhaps tied together with the usual scripting tools (maybe miniperl or sh/sed/awk). (sysinstall requires too specific a configuration for my needs, which are focused on en masse - and zero touch - workstation and server deployment.) Best wishes, Matthew -- "Rogues are very keen in their profession, and know already much more than we can teach them respecting their several kinds of roguery." - A. C. Hobbs in _Locks and Safes_ (1853) smime.p7s Description: S/MIME cryptographic signature
Alternate installers for FreeBSD for unattended installation
I'm having a difficult time developing a scripted install using sysinstall, as my target hardware is not sufficiently uniform, hostnames vary, etc. The sysinstall documentation implies that alternatives are available, and that sysinstall is not really supported any more. Where can I find these alternate installers? Do they have better support for scripted installations? Is it possible to perform the installation manually from the mfsroot image? If so, I guess I could develop a shell script that performs the installation steps. Best wishes, Matthew -- "Rogues are very keen in their profession, and know already much more than we can teach them respecting their several kinds of roguery." - A. C. Hobbs in _Locks and Safes_ (1853) smime.p7s Description: S/MIME cryptographic signature
RE: tcpdump, rl, sis, fxp and multicast problems
> not very important but wouldn't it be better to set the checksum > to 0 instead of some arbitrary (?) and confusing value then ? No, as not setting the checksum is a (minor) optimization. Setting that field to any arbitrary constant means at least one completely unnecessary CPU instruction per datagram. Best wishes, Matthew -- "Rogues are very keen in their profession, and know already much more than we can teach them respecting their several kinds of roguery." - A. C. Hobbs in _Locks and Safes_ (1853) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: gmirror disks vs partitions
> Apart from potentially avoiding a whole disk from being copied > during a resync after a crash, are there any other advantages to > using partition level mirroring instead of drive level mirroring? Joe, Partition-level software RAID plus LVM is how the following Slashdot poster manages extendable (and inequally sized disk) arrays on Linux: http://ask.slashdot.org/comments.pl?sid=169386&cid=14117414 Best wishes, Matthew -- "Rogues are very keen in their profession, and know already much more than we can teach them respecting their several kinds of roguery." - A. C. Hobbs in _Locks and Safes_ (1853) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
