On Sun, 4 Jun 2006, Rott_En wrote:
> Hello
>
> I had a power failure yesterday morning and because of that my server went
> down because of no battery present.
> When trying to mount the crypto partitions, I have figured out its not
> possible anymore because a set of 2 errors, as follows:
>
> # sh cryptfs -m -p /home -f /crypto/home/cryptofile -d /dev/svnd0c
> Encryption key:
> mount_ffs: /dev/svnd0c on /home: specified device does not match mounted
> device
> #
>
> and then, when trying again :
>
> # 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
> #
>
>
> For further reference , cryptfs script is the following:
>
> #!/bin/sh
> #
> # cryptfs
> #
> # mount/unmount blowfish encrypted filesystem
> #
> # 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.
Sigh...
I asked the author of these script repeatedly to shut his site down or
update his stuff, but he did not do that and this keeps coming back on
[EMAIL PROTECTED]
Let me repeat this ex cathedra as an OpenBSD developer: there's no
fundamental reason fsck does not work on svnd devices. There are also
no known bugs. This means that you can run fsck on them like on any
block devcie containing a file system.
-Otto
