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
1) Errormessages are there to say you something. In this case, it says that there is already a device. read the vnconfig manpage. I'm sure you can figure out how to remove it or use a free vnd device... 2) vnconfig will make any file, no matter what crap it contains, available as a device. it doesn't care about how it looks. This implies that as long as there is a valid filesystem and your container is not damaged too much, fsck can correct errors like it does on a real hdd. I haven't looked at the code, but i'm 99% sure it doesn't even know the difference. Of course, the more layers something has, the more errors can appear in the various subsystems involved. Anyway, my mail is getting far to long..., Just fsck and be done with it, I do it every day on my notebook... > [tons off innocent bytes killed] Tobias
