Contributed by Dengue on from the howto dept.
(Comments are closed)
OpenBSD Journal
Contributed by Dengue on from the howto dept.
(Comments are closed)
Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]
By Darren () darren@dazdaz.NOSPAM.org on mailto:darren@dazdaz.NOSPAM.org
Should'nt there be some kind of rc.local initialisation of the RAID for when the system is rebooted? And some form of RAID detection state beforehand to see if it's in a mountable?
How about clarifying the differences between the RAID levels. perhaps a RAID 0, 1 and 5 menu, click on those and then see the steps required for ultimate clarity.
Regards
Comments
By Andreas F. Bobak () on http://my.abstrakt.ch/blog
By Mikee () mkoc@info-trade.pl on mailto:mkoc@info-trade.pl
Comments
By sickness () s i c k n e s s -AT- s i c k n e s s -DOT- i t on http://www.sickness.it
A few time it was rebooted uncleanly, because the UPS battery life anded, I needed to do an fsck -b 32 in order to boot, but beyond this no problems at all :)
By Wim () wim@kd85.com on http://kd85.com
on two RAID 1 disks, it's stable. Load or no load, I have a very loaded system that run on two 75 GB disks and the only downside is that if something goes wrong, like an unclean shutdown, it means hours of downtime due to the rebuild of the stripes. Or if you run it in background, a lagged system.
And the RAID bit does work just fine, it saved my ass at least 3 times, even last Saturday:
wd0g: uncorrectable data error reading fsbn 1589507 of 1589504-1589519 (wd0 bn 29687507; cn 29451 tn 14 sn 17)
raid3: IO Error. Marking /dev/wd0g as failed.
raid3: node (Rmir) returned fail, rolling backward
raid3: DAG failure: r addr 0x1840c0 (1589440) nblk 0x10 (16) buf 0xd6c39000
Comments
By Mikee () mkoc@info-trade.pl on mailto:mkoc@info-trade.pl
I've also had a production machine running RAID5 array, OpenBSD 3.0. It was crushing twice a week, what was unacceptable.
Comments
By ansible () ansible atty xnet dotty com on mailto:ansible atty xnet dotty com
Never tried 3.0. I've had a 3.1 system with RAID-1 using RAIDFrame running for about 7 months without any crashes or problems. Very stable.
Ran into major problems with OBSD 3.2. For example, it would crash when you tried to unconfigure an array. This was on the exact same H/W as the 3.1 machine. Ended up going back to 3.1.
Just set up my first 3.3 machine with RAIDFrame. Clean and smooth installation, no problems so far. But this is an unloaded machine, and it has only been a week.
A guy in the other thread wanted an explaination of RAID levels.
By Wim () wim@kd85.com on http://kd85.com
Is that a partial conclusion? ;)
RAID 1 has proven rock solid over here, if you don't mind your pciide0 to shoot over 380 interups per second while doing 4 GB/s dowloads from a stripe ;-)
Comments
By Anonymous Coward () on
I have 12 disks split into 3 RAID5 sets and then a RAID0 across those 3 sets. While it's no speed demon it hasn't crashed either (it is the backup/rsync server for a bunch of machines). All disks are scsi same size, make and model. This is on OpenBSD 3.3.
Comments
By Mikee () mkoc@info-trade.pl on mailto:mkoc@info-trade.pl
By Fabio Shingu.H () tshingujp@yahoo.co.jp on mailto:tshingujp@yahoo.co.jp
By Stephen Foster () sfoster@argogroup.com on http://www.argogroup.com
Raid 1 on a system with load average >1 in normal use and >5 in heavy use.
No evidence of any instability in 18 months, it works.
By mirabile () mirabile@bsdcow.net on http://templeofhate.com/tglaser/mbsd5/
two days ago? It has native support for installing
on a RAID set (marked -A yes or -A root) in bsd.rd,
and bsd.rd also comes with raidctl, NTFS, NFS, PPP,
PPPoE, PPPoA, ISDN support.
Note: I have heard the cdrom33.fs is broken; if
you can confirm this, please email me or post
a reply. I can guarantee bsd, bsd.rd and
floppyM33.fs are fine.
Comments
By mirabile () mirabile@bsdcow.net on https://mirbsd.bsdadvocacy.org:8890/active/cvsweb.
out of kernels which have DDB support (yet), must
be some error in ddb_init() though.
I'm now stripping all but one symbol, and have
uploaded new checksum files and cdrom33.fs/cd33.iso
files.
On the ekkoBSD topic: I stick closer to OpenBSD
than Rick plans, but we're in mail contact.
By C. Tran () obsduser@yahoo.com on mailto:obsduser@yahoo.com
One question:
In the section
Creating Partions:
# create partitions
disklabel -E raid0
I tried to create /, /home, /tmp, /usr and /var
after creating swap, but never got prompted for mount points....
thx
charles