Configuring LVM volumes
Reading all physical volumes. This may take a while...
Activated Volume Groups:
Mounting new root
WARNING!!! Possibly insecure memory, missing mlockall()
No policy for mapper/temporary-cryptsetup-160 specified, or policy not found
disk scheduler: set policy of mapper/temporary-cryptsetup-16 to noop
No policy for mapper/temporary-cryptsetup-160 specified, or policy not found
disk scheduler: set policy of mapper/temporary-cryptsetup-16 to noop
No policy for mapper/root0 specified, or policy not found
disk scheduler: set policy of mapper/root to noop
HAMMER(ROOT) recovery check seqno=002374c7
HAMMER(ROOT) recovery range 30000000026b5ad0-30000000026b5ad0
HAMMER(ROOT) recovery nexto 30000000026b5ad0 endseqno=002374c8
HAMMER(ROOT) mounted clean, no recovery needed
umount:
unmount of /tmp failed
:
Device busy
Mounting devfs on new root
chroot_kernel: set new rootnch/rootvnode to /new_root
/etc/rc: WARNING: $udevd_early is not set properly - see rc.conf(5).
Configuring crypto disks.
No policy for mapper/temporary-cryptsetup-431 specified, or policy not found
seg-fault ft=0002 ff=000c addr=0 rip=0x401a90 pid=8 p_comm=udevd
disk scheduler: set policy of mapper/temporary-cryptsetup-43 to noop
Key slot 0 unlocked.
No policy for mapper/swap1 specified, or policy not found
disk scheduler: set policy of mapper/swap to noop
Loading configuration files.
Loading devfs rules:
/etc/defaults/devfs.conf
On Mon, Dec 13, 2010 at 12:32 PM, Chris Turner
<c.turner@199technologies.org> wrote:
Alex Hornung wrote:
For whatever it's worth, I've added a task to google code-in a few weeks ago to document all this dm stuff, both cryptsetup and lvm, basically.
A bit OT but shouldn't this stuff go in bugs / the wiki and then be
referenced to any "google code-in" or "foo barbaz-quux" to prevent
fragmentation?
(from someone who has had to do 'where did that note go' many a time :)
cheers