ipfw and Hammer fixes in DragonFly

There’s an odd bug in ipfw that is now fixed in DragonFly 6.2/6.3.  If you are using ipfw and adding networks and hosts in a specific order, the netmask will be set wrong.

There’s also a problem with the overnight bulkfree cleanup in Hammer that’s had various attempts to fix it over time – it’s now really truly fixed.  It mattered only if you had an extremely large number of inodes – 100000000 or so,

Matthew Dillon wrote up an explanation for both.

HAMMER2 emergency space mode

As anyone who has been running HAMMER1 or HAMMER2 has noticed, snapshots and copy on write and infinite history can eat a lot of disk space, even if the actual file volume isn’t changing much.  There’s now an ‘emergency mode‘ for HAMMER2, where disk operations can happen even if there isn’t space for the normal history activity.  It’s dangerous, in that the normal protections against data loss if power is cut go away, and snapshots created while in this mode will be mangled.  So definitely don’t leave it on!