Search results

You probably should, but in the mean time you can try remap the old libraries to the new ones with /etc/libmap.conf. eg: libz.so.5 libz.so.6 I'm assuming libz.so.6 is the file name of the new library in 9.0.

Apart from reducing your NAT rules to one line, it's probably faster too... :)

Great! Welcome. For it to work that way would violate volman's design, and probably break things. The same can be achieved by writing a client daemon that does all that with the help of volman's API, which I'll hopefully get around to documenting soon. :P I'll try hoof that into the API in...

Did you compare it while using a bitmask pool option in your PF NAT ruleset?

Usermount not needed. Type vmount. It should show you a list of devices that have been detected, and their mount status. Once you see the one you want to mount: vmount da1s1 And the same when you want to umount it. See what happens, and let us know. :)

I authored it before they modded it for PCBSD. See here for the latest development. I still need to make documentation for it. Happy hacking in the mean time. :)

I don't see that being possible. Closest would be to create another gmirror instance with the 2 new drives, and mount it to a new location in the file system, perhaps even below the directory hierarchy of your existing gmirror instance.

This one too: http://www.youtube.com/watch?v=Wp-OtbZEuEc

I'm curious why your script needs to run so often? The way I monitor disk space is to run a script once a day which tracks the trends of utilisation over time. If it predicts a disk will become full in less than 14 days, it sends an alert.

I use it in addition to C3 CPU states on my home server. I would not advise messing with CPU states on most servers though; powerd alone should be fine.

Appreciate the plug, but I don't see the relevance? My work is oriented at hot plugged devices...

FWIW, the chksetuid periodic was causing one of my ZFS systems to lock up too, but the real cause ended up being a failing SATA controller (to which our ZIL and L2ARC was attached).

It must be as fluca said. The error "Network is unreachable" is a bit of a giveaway. Enabling RC debugging might help you troubleshoot. Add to /etc/rc.conf: rc_debug=YES However, have you considered using amd instead of fstab?

It's probably one of the periodics that searches the file system: /etc/periodic/weekly/310.locate /etc/periodic/security/100.chksetuid Although if they're causing a panic, the real problem is something else...

latest developments

[reserved for documentation]

Hi, A while ago I wrote an elaborate shell script to provide HAL-style disk mounting in Openbox (still my favourite WM btw). Personally it's been really successful for my own use, and I get the impression others have liked it too. Well I've been tweaking it here and there, and it's now an...

Are you sure you need that ZAxisMapping directive? Try remove it, and if scrolling still doesn't work, use x11/xev to troubleshoot what button events your wheel is triggering, and remap them appropriately (scrolling uses buttons 4 and 5).

I've seen this a handful of times. It was always a BIOS setting, or a dodgy BIOS... Sorry to not be more specific.

ZFS v28 will remain in FreeBSD for as long as it's relevant and maintainable. If Oracle make higher versions open source, they'll presumably be ported to FreeBSD in time. If they don't, ZFS may become an official fork like OpenSolaris became, or it'll just evolve independently within FreeBSD...