On 02/08/13 13:00, Stefan Sperling wrote:
On Fri, Feb 08, 2013 at 12:52:00PM -0500, Scott McEachern wrote:
Shit, I forgot to mention that I already gave that a whirl by putting:
umount -f /st3 <-- the mount point of the crypto volume
in /etc/rc.shutdown. It makes no difference; I still get that
warning/error.
I also tried:
umount -f 6c6e53ab843ef6c8.a <-- the DUID of the crypto volume
and, curiously, it says that it's not currently mounted. (Yet
that's exactly how I mount it with bioctl in rc.securelevel, where
it prompts me for the password.) I've also tried doing it by hand
(vs. rc.shutdown) and it still doesn't matter.
Any other suggestions?
You have to destroy the softraid volume, too, in addition to unmounting
the filesystem. Running 'bioctl -d sd4' should do the trick.
You want to see 'sd4 detached' in dmesg before 'sd3 detached'.
Aha! I gave that a shot and everything works *perfectly*. No more
"ugly" messages and I feel much better about the integrity of my data.
Thanks very much Joel and Stefan, your work and help has been invaluable!
Now, the fun begins: I have two 3TB RAID1 volumes, with no encryption,
on another machine (acting like an OpenBSD NAS box, really) at 65% and
40% capacity (do the math..) Because I was unsure of the crypto
volume's integrity on this machine, stuff is rsynced to that machine.
Now that I know to destroy the crypto volumes I get to do some juggling
in order to create crypto partitions on those volumes. This is gonna
take a while. *laughs*
--
Scott McEachern
https://www.blackstaff.ca
