Hello Is it a risk to attempt using your recommedation ? Am I risking the integrity of my cryptofile container ? It is 90GB big and I dont have any auxiliary backup medium so big, taking a backup of it is almost out of hope.
I can't loose the data from this cryptofile, so please tell me if I risk using your method of repair. Thank you in advance. Juha Erkkila <[EMAIL PROTECTED]> wrote: On Sun, Jun 04, 2006 at 02:07:22AM -0700, Rott_En wrote: > # Important Note: Under OpenBSD's current encrypted vnd filesystem > # implementation, when a system with a mounted, encrypted vnd filesystem > # is shutdown uncleanly, the encrypted vnd filesystem's structures get > # damaged and, since OpenBSD's fsck will not acknowledge vnd filesystems, > # these damaged structures can not reasonably be repaired. i don't think this is true. just use vnconfig to attach a file to svnd0, and then do fsck /dev/rsvnd0c (maybe take a backup first?) OTOH, whether that works may depend on the disklabel on /dev/rsvnd0c, but at least i do this routinely in a similar script as yours, before mounting /dev/svnd0c, and it appears to work fine for me Juha Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
