On Sat, 9 Feb 2013, Andy Bradford wrote:
Thus said Joel Sing on Sat, 09 Feb 2013 16:44:11 +1100:
umount via DUID does not work currently - this will be fixed shortly
after the next release freeze has ended.
Will that also include shutdown of softraid via DUID? e.g.,
bioctl -d DUID
On 02/10/13 08:13, Scott McEachern wrote:
I could have sworn the man page for fsck(8) said something about rule #1
being don't panic, but I couldn't find it in there. Must be somewhere
else. So I didn't panic, watched a bit of TV and thought about it...
I'm pretty sure you're thinking about
On 02/10/13 14:17, Alexander Hall wrote:
On 02/10/13 08:13, Scott McEachern wrote:
I could have sworn the man page for fsck(8) said something about rule #1
being don't panic, but I couldn't find it in there. Must be somewhere
else. So I didn't panic, watched a bit of TV and thought about
Thus said Joel Sing on Sat, 09 Feb 2013 16:44:11 +1100:
umount via DUID does not work currently - this will be fixed shortly
after the next release freeze has ended.
Will that also include shutdown of softraid via DUID? e.g.,
bioctl -d DUID
Or is this not even possible?
Thanks,
Andy
On 02/09/13 03:09, Andy Bradford wrote:
Thus said Joel Sing on Sat, 09 Feb 2013 16:44:11 +1100:
umount via DUID does not work currently - this will be fixed shortly
after the next release freeze has ended.
Will that also include shutdown of softraid via DUID? e.g.,
bioctl -d DUID
Or is
On Sat, Feb 09, 2013 at 03:52:12AM -0500, Scott McEachern wrote:
On 02/09/13 03:09, Andy Bradford wrote:
Thus said Joel Sing on Sat, 09 Feb 2013 16:44:11 +1100:
umount via DUID does not work currently - this will be fixed shortly
after the next release freeze has ended.
Will that also
On 02/09/13 15:06, Stefan Sperling wrote:
On Sat, Feb 09, 2013 at 03:52:12AM -0500, Scott McEachern wrote:
On 02/09/13 03:09, Andy Bradford wrote:
Thus said Joel Sing on Sat, 09 Feb 2013 16:44:11 +1100:
umount via DUID does not work currently - this will be fixed shortly
after the next
On 02/09/13 15:06, Stefan Sperling wrote:
On Sat, Feb 09, 2013 at 03:52:12AM -0500, Scott McEachern wrote:
On 02/09/13 03:09, Andy Bradford wrote:
Thus said Joel Sing on Sat, 09 Feb 2013 16:44:11 +1100:
umount via DUID does not work currently - this will be fixed shortly
after the next
On 02/09/13 22:16, Scott McEachern wrote:
I didn't know what to wipe first, the sweat off my forehead or ...
well, you get the idea.
I'm tempted to try to use bioctl -c 1 -l /dev/sd0,/dev/sd1 softraid0
and bioctl -c 1 -l /dev/sd2,/dev/sd3 softraid0 to recreate the
volumes (just like how I
On Fri, 8 Feb 2013, Scott McEachern wrote:
I get a rather curious error when shutting down a machine with a RAID 1
setup that contains a crypto partition and a normal partition:
syncing disks... done
sd3 detached
softraid0: I/O error 5 on dev 0x433 at block 16
softraid0: could not write
On Sat, Feb 09, 2013 at 02:56:47AM +1100, Joel Sing wrote:
While stacked softraid volumes generally work, they are not officially
supported (for a variety of reasons). The problem that you mention above is
due to the way that softraid volumes are shutdown - the shutdown order is
On Sat, 9 Feb 2013, Jiri B wrote:
On Sat, Feb 09, 2013 at 02:56:47AM +1100, Joel Sing wrote:
While stacked softraid volumes generally work, they are not officially
supported (for a variety of reasons). The problem that you mention above
is due to the way that softraid volumes are shutdown -
On Sat, Feb 09, 2013 at 03:26:33AM +1100, Joel Sing wrote:
Would stackable softraid volumes work in near future or is it big
problem as how softraid was designed?
Generally speaking they already work - there are just some caveats,
primarily relating to assembly and shutdown. Most of the
On 02/08/13 11:26, Joel Sing wrote:
On Sat, 9 Feb 2013, Jiri B wrote:
On Sat, Feb 09, 2013 at 02:56:47AM +1100, Joel Sing wrote:
While stacked softraid volumes generally work, they are not officially
supported (for a variety of reasons). The problem that you mention above
is due to the way
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:
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
On Fri, Feb 08, 2013 at 12:52:00PM -0500, Scott McEachern wrote:
| Either way, it sounds fantastic and having smooth RAID (esp.
| crypto) operations, l think, would be a huge feather in OpenBSD's
| cap. I haven't tried full disk encryption yet, maybe on a test box
| one day, because I just don't
On Fri, Feb 08, 2013 at 07:32:49PM +0100, Paul de Weerd wrote:
On Fri, Feb 08, 2013 at 12:52:00PM -0500, Scott McEachern wrote:
| Either way, it sounds fantastic and having smooth RAID (esp.
| crypto) operations, l think, would be a huge feather in OpenBSD's
| cap. I haven't tried full disk
On 02/08/13 13:32, Paul de Weerd wrote:
On Fri, Feb 08, 2013 at 12:52:00PM -0500, Scott McEachern wrote:
| Either way, it sounds fantastic and having smooth RAID (esp.
| crypto) operations, l think, would be a huge feather in OpenBSD's
| cap. I haven't tried full disk encryption yet, maybe on a
On Fri, Feb 08, 2013 at 01:54:27PM -0500, Scott McEachern wrote:
| What kind of hardware do you have powering those machines? Besides,
| I don't use the crypto partition too often and I really should make
| it smaller (it's only at 17% capacity out of 1.4TB).
Admittedly, these are pretty
On 02/08/13 15:19, Paul de Weerd wrote:
Admittedly, these are pretty powerful machines. And Antoine was
right, it's amd64 (I don't have i386 in real day-to-day use anymore).
I have a couple of P4s (no HT) running i386 (firewall, and my web/db
server), but otherwise everything is amd64.
On 2013-02-08, Paul de Weerd we...@weirdnet.nl wrote:
On Fri, Feb 08, 2013 at 01:54:27PM -0500, Scott McEachern wrote:
| What kind of hardware do you have powering those machines? Besides,
| I don't use the crypto partition too often and I really should make
| it smaller (it's only at 17%
On Sat, 9 Feb 2013, Stuart Henderson wrote:
On 2013-02-08, Paul de Weerd we...@weirdnet.nl wrote:
On Fri, Feb 08, 2013 at 01:54:27PM -0500, Scott McEachern wrote:
| What kind of hardware do you have powering those machines? Besides,
| I don't use the crypto partition too often and I really
On Sat, 9 Feb 2013, Scott McEachern wrote:
On 02/08/13 11:26, Joel Sing wrote:
On Sat, 9 Feb 2013, Jiri B wrote:
On Sat, Feb 09, 2013 at 02:56:47AM +1100, Joel Sing wrote:
While stacked softraid volumes generally work, they are not officially
supported (for a variety of reasons). The
I get a rather curious error when shutting down a machine with a RAID 1
setup that contains a crypto partition and a normal partition:
syncing disks... done
sd3 detached
softraid0: I/O error 5 on dev 0x433 at block 16
softraid0: could not write metadata to sd3d
sd4 detached
rebooting...
When
25 matches
Mail list logo
