On Mon, Jun 05, 2006 at 01:01:34PM -0700, Rott_En wrote:
> I used "fsck -n" and then tried to mount the /crypto/home/cryptofile
> partition container with no luck, same results stating:
>
> # sh cryptfs -m -p /home -f /crypto/home/cryptofile -d /dev/svnd0c
> Encryption key:
> vnconfig: VNDIOCSET: Device busy
> mount_ffs: /dev/svnd0c on /home: specified device does not match mounted
> device
> # mount -f /home
> mount: can't find fstab entry for /home.
> # mount -f /crypto/home/
> mount_ffs: /dev/wd0g on /crypto/home: Device busy
> # mount -r /crypto/home/
> mount_ffs: /dev/wd0g on /crypto/home: Device busy
> #
1. please don't top post, trim your lines under 80
2. RTFM. in this case those are: vnconfig(8), fsck(8), mount(8)
3. AFTER figuring out what these will do, try these:
$ vnconfig -k svnd0 /crypto/home/cryptfile
(type the correct key)
$ fsck /dev/rsvnd0c
$ mount /dev/svnd0c /home
don't blame me if it breaks.
4. consider not using a single, huge, encrypted vnd, for data that matters
5. toss away the cryptfs-script: it doesn't do fsck, if doesn't back out
from errors, it forces mounts even when it should not
Juha
