---- Original message ---- >Date: Mon, 5 Jun 2006 04:47:28 -0700 (PDT) >From: Rott_En <[EMAIL PROTECTED]> >Subject: Re: Crypto Partition Problem >To: misc@openbsd.org > >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 have a few encrypted disk images on my machines and i only keep shady, non-vital stuff in them right now. any time you're serious about your data, you should be backing it up on a regular basis. is the whole 90GB full? do read http://openbsdsupport.org/BackupScriptExample.html to see a good script for keeping backups. this leads me to ask a related question (if anyone feels this is hijacking, respond in a new thread): if you have a large encrypted disk image that you usually mount with vnconfig, will backing up the partition on which the encrypted image resides be sufficient to get a good backup? what if the encrypted image is written to on a regular basis and cannot be relied upon to be unmodified during the time it takes to dump it to a backup server? will the backed up image be corrupted? i could try this myself, but am hella busy this week and someone here likely knows the answer. >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
