Kernel - Completely remove DFLTPHYS * There is no need to have two different macros define the maximum allowed IO size for low-level operations; replace DFLTPHYS by MAXPHYS in the entire kernel. * Old drivers typically used DFLTPHYS without a second thought, assuming it would always be the same value; they may have hard limitations and break if bigger I/O sizes are suddenly used. Be sure to explicitely limit their maximum allowed I/O size to 64KB and keep them working.
md(4) - Several fixes to make the module loading/unloading work properly. Previously, md(4) crashed the system. It produced inconsistencies due it wasn't registered as a module, thus allowing to be kldloaded even when it was compiled in on kernel. Reported-by : Sascha Wildner and many people Lots-of-help : Alex Hornung Dragonfly-bug: <http://bugs.dragonflybsd.org/issue174>
md - when setdiskinfo, also set no of blocks * Before calling disk_setdiskinfo, make sure that the number of blocks is also set or no probing will be triggered at that point. * Also disable setdiskinfo on open, as it shouldn't be needed. * Fix nomenclature md0c -> md0s0. * This also fixes root mount from md disk image. Reported By: Alexander Polakov Dragonfly-bug: http://bugs.dragonflybsd.org/issue1522
Continue untangling the disklabel. Have most disk device drivers fill out and install a generic disk_info structure instead of filling out random fields in the disklabel. The generic disk_info structure uses a 64 bit integer to represent the media size in bytes or total sector count.