Geli in a Jail? geli: Cannot lock memory: Operation not permitted.
Rudy
crapsh at monkeybrains.net
Tue Mar 31 00:00:17 PDT 2009
I could't init a geli in a jail. Anyone know how?
Here is what I tried
jail# geli init -s 4096 -K /root/gelitest.key /dev/zvol/tank/testgeli
geli: Cannot lock memory: Operation not permitted.
[1] In the host, I created the volume:
host# zfs create -V 4g tank/gelijar
[2] made a custom devfs to show the zvol in the jail...
[devfsrules_gelitest=5]
add include $devfsrules_hide_all
add include $devfsrules_unhide_basic
add include $devfsrules_unhide_login
add path zvol unhide
add path tank unhide
add path *gelijar unhide
[3] tried to add the geli in the jail and failed. :(
For now, I init/attach/newfs/mount the filesystem from the host into the jail, but I want to leave the attach to the customer in the jail...
host# geli init -s 4096 -K /root/gelitest.key /dev/zvol/tank/testgeli
host# geli attach -k /root/gelitest.key /dev/zvol/tank/testgeli
host# newfs /dev/zvol/tank/testgeli.eli
host# mount /dev/zvol/tank/testgeli.eli /tank/gelijar.monkeybrains.net/crypt
host# df < -- I see it!
jail# df <-- I don't see /crypt. :( Any way to fix that as well?
Thanks,
Rudy
More information about the freebsd-current
mailing list