Not sure yet whether this is in the filesystem or block device driver or something else, but I just had my ProLiant DL360p Gen8 running 11.0 + fixes hang/panic while trying to create a “v0” (4.3) FFS filesystem (only, no disklabel) in an empty file mounted at vnd0.
I created one such filesystem of 32MB on vnd0 and it just worked. Then I tried to create a 500MB filesystem on vnd1 and newfs hung, but control-C got out of it. Then I detached vnd1, created a new empty 384MB file, attached that as vnd1, and tried to newfs that and the whole system hung and then panicked. Since this system has an extreme amount of RAM I disabled dumps, and I reset the system right before I realized I could screenshot the remote web console to get a backtrace. Obviously if this reproduces I’ll grab one; I plan to try again once the fsck on my storage array finishes, but I figured I’d post in case this rings any bells for anyone else. -- Chris PS - Why I’m doing this: I managed to fully boot the MacMach install/rescue RAM disk in an emulated Mac IIx in MAME (now that A/UX works in it), but there’s no straightforward way to actually perform an installation without some sort of media image. MacMach uses Apple rather than BSD partitioning, but still uses the 4.3 Tahoe filesystem. So my plan was to make 4.3-compatible root and usr filesystems (with no disklabel), untar MacMach into them with full permissions, device nodes, etc., and then create a couple Apple-partitioned disk images containing those filesystems from which to fully boot MacMach.
