DragonFly bugs List (threaded) for 2008-09
Re: hammer-inodes: malloc limit exceeded
On Sun, Aug 31, 2008 at 03:12:52PM -0700, Matthew Dillon wrote:
> :This is 2.0 + patches (current DragonFly_RELEASE_2_0_Slip)
> :> And tell me what it says. If the value is greater then 70000, set it
> :> to 70000.
> :There is no such sysctl. I used kern.maxvnodes instead; the original value
> :was 129055.
> Yah, I mistyped that. its kern.maxvnodes. The fix I had made was
> MFC'd to 2.0_Slip so the calculation must still be off. Reducing
> maxvnodes should solve the panic. The basic problem is that HAMMER's
> struct hammer_inode is larger then struct vnode so the vnode limit
> calculations wind up being off.
The panic occurred again with kern.maxvnodes set to 70000.
I have reduced it to 35000; we will see if the system is still stable in a
> You don't need to use the hardlink trick if backing up to a HAMMER
> filesystem. I still need to write utility support to streamline
> the user interface but basically all you have to do is use rdist, rsync,
> or cpdup (without the hardlink trick) to overwrite the same destination
> directory on the HAMMER backup system, then generate a snapshot
> softlink. Repeat each day.
I agree this is a better way with Hammer. I just don't want to use something
too different from my other backup servers for the time being...