Sd3a
  Home FAQ Contact Sign in
 
Advanced search
MATCHING GROUPS



more...
POPULAR GROUPS

more...

found 20 articles for 0.303 sec
K.R. (Randy) Lewis, We were able to confirm (today) that it is the /MP kernel that has the issue defined below. The single CPU build ran the huge file copy just fine. R > Re-post in misc@ (sorry for posting wrongly before) > ----------------- > > Encountered the following: 4.3 i386 MP kernel w/Raidframe > - throws a: splassert: uvm_map_p: want 1 have 1 > > Here's what was going     

Group: mailing.openbsd.misc · Group Profile · Search for Sd3a in mailing.openbsd.misc
Author: "K.R. (Randy
Date: Jul 22, 2008 14:42

Re-post in misc@ (sorry for posting wrongly before) ----------------- Encountered the following: 4.3 i386 MP kernel w/Raidframe - throws a: splassert: uvm_map_p: want 1 have 1 Here's what was going on....... We took a USB 250GB drive and wiped it (unallocated partition) using partition magic on one of those, what do you call it.. ..oh yeah...WindowsXP thingys...(expedient, ok
Show full article (15.11Kb) · Show article thread
We took a USB 250GB drive and wiped it (unallocated partition) using partition magic on one of those, what do you call it....oh yeah...WindowsXP thingys... (expedient, ok?) Then plugged it into a 4.3 OpenBSD MacMini, did a disklabel and established a partition sd0i of type MSDOS. Then did a newfs t msdos sd0i. All of this works great, each time we do it. Then mounted it on the MacMini     

Group: mailing.openbsd.misc · Group Profile · Search for Sd3a in mailing.openbsd.misc
Author: "K.R. (Randy
Date: Jul 18, 2008 20:17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Post-Date: Sun, 6 Jul 2008 20:41:00 +0000 SPAMCOP.net-REPORT: http://www.spamcop.net/sc?id=z2049172537ze844f6c82413048dc78d925b7086458fz Spam-Date: Sun, 6 Jul 2008 20:00:18 +0000 (1215376860) Info: Copy of spam reported via SpamCop.Net Info: Country info based on zz.countries.nerd.dk Info: ASN info based on asn.routeviews.org Spam-Track: IP
Show full article (14.20Kb)
On Tue, May 27, 2008 at 07:25:19PM -0600, Duncan Patton a Campbell wrote: > Howdy? > > I've implemented a softraid 0+1 array and it's working fine. I have sooooo not thought this through yet :-) > > I had a metadata corruption incident and recovered as discussed > in <20080328133249.GA2979@www.sneaker-net.org> . > > So now I am wondering about recovery in the event of a real failure     

Group: mailing.openbsd.tech · Group Profile · Search for Sd3a in mailing.openbsd.tech
Author: "K.R. (Randy
Date: Jul 16, 2008 16:15

Howdy? I've implemented a softraid 0+1 array and it's working fine. I had a metadata corruption incident and recovered as discussed in <20080328133249.GA2979@www.sneaker-net.org> . So now I am wondering about recovery in the event of a real failure. Could this be accomplished by configuring a softraid with only 1 disk? e.g. bioctl -c 1 -C force -l /dev/sd2a softraid0 given that
Show full article (13.77Kb)
I have just had a similar incident and recovered similarly. So now I am wondering about recovery in the event of a real failure. Could this be accomplished by configuring a softraid with only 1 disk? e.g. bioctl -c 1 -C force -l /dev/sd2a softraid0 given that sd3a suffered the failure? Is there any documentation about recovery of failures in a softraid partition? Thanks, Dhu     

Group: news.admin.netabuse.sightings · Group Profile · Search for Sd3a in news.admin.netabuse.sightings
Author: Andrzej Filip
Date: Jul 6, 2008 13:41

Greetings-- I have 4 SATA disks configured as 2 raid-1 arrays on a 4.3 box (i386). # bioctl -c 1 -l /dev/sd0a,/dev/sd1a softraid0 # bioctl -c 1 -l /dev/sd2a,/dev/sd3a softraid0 sd0a and sd1a are sd4, sd2a and sd3a are sd5: # bioctl softraid0 Volume Status Size Device softraid0
Show full article (4.44Kb)
Adding misc that somehow fell off... On Fri, Mar 28, 2008 at 08:51:18AM -0500, Marco Peereboom wrote: > Assuming the drives weren't hurt you can reassemble the RAID 1 with the > -C force option. Do something along the lines of: > > bioctl -c 1 -C force -l /dev/sd2a,/dev/sd3a softraid0 > > That will overwrite the current stale metadata with new one. Make sure > you fsck the filesystem     

Group: mailing.openbsd.misc · Group Profile · Search for Sd3a in mailing.openbsd.misc
Author: Marco Peereboom
Date: May 28, 2008 03:23

Hello. When ever I've had problems with raid5, and when raid1 appears to work fine, it's always been a memory exhaustion problem. When raid5 sets are working hard, i.e. reading and writing a lot of data, they're memory hogs relative to their raid1 cousins. How much memory is in your machine? Perhaps you're riding a memory limit, which was triggered by an increase in the newer kernel size
Show full article (0.92Kb) · Show article thread
    

Group: mailing.openbsd.misc · Group Profile · Search for Sd3a in mailing.openbsd.misc
Author: Duncan Patton a Campbell
Date: May 27, 2008 18:25

Show full article (0.52Kb)
    

Group: mailing.openbsd.misc · Group Profile · Search for Sd3a in mailing.openbsd.misc
Author: Duncan Patton a Campbell
Date: May 23, 2008 14:52

Show full article (2.13Kb)
    

Group: mailing.openbsd.misc · Group Profile · Search for Sd3a in mailing.openbsd.misc
Author: Frank Garcia
Date: May 15, 2008 11:55

Show full article (2.34Kb)
    

Group: mailing.openbsd.misc · Group Profile · Search for Sd3a in mailing.openbsd.misc
Author: Marco Peereboom
Date: Mar 28, 2008 15:18

Show full article (1.58Kb)
    

Group: fa.netbsd.currentusers · Group Profile · Search for Sd3a in fa.netbsd.currentusers
Author: Brian Buhrow
Date: Mar 20, 2008 07:17

Show full article (8.22Kb)
1 · 2 · next