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 Illu
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
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 che
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 s
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-
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, perh
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 al
> 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
> 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 extendab
