raid1 does not seem faster

Hello list, normally, I'd think that combining drives into a raid1 array would give me at least a little improvement in read speed. In my setup however, this does not seem to be the case. 14:16 opteron:/var/log # hdparm -t /dev/sda Timing buffered disk reads: 170 MB in 3.01 seconds =

Re: raid1 does not seem faster

Jan Engelhardt wrote: normally, I'd think that combining drives into a raid1 array would give me at least a little improvement in read speed. In my setup however, this does not seem to be the case. 14:16 opteron:/var/log # hdparm -t /dev/sda Timing buffered disk reads: 170 MB in 3.01

Re: raid1 does not seem faster

On Sun, 2007-04-01 at 14:19 +0200, Jan Engelhardt wrote: Hello list, normally, I'd think that combining drives into a raid1 array would give me at least a little improvement in read speed. In my setup however, this does not seem to be the case. 14:16 opteron:/var/log # hdparm -t

raidtools to mdadm

ok so i am trying to recover some data for a friend. what i am wanting to do is forcibly set up /dev/mdN to be a raid0 of /dev/sda and /dev/sdb i do not want to actually change any of the contents of these drives, just mount very simply as a raid0. the raid was originally created using an

Re: raidtools to mdadm

On Sunday April 1, [EMAIL PROTECTED] wrote: as best i can tell i am using the correct commands for what i want but i pretty much get nothing but errors: [EMAIL PROTECTED]:/media# mdadm --build /dev/md1 --chunk=128 --level=0 --raid-devices=2 /dev/sda /dev/sdb mdadm: error opening /dev/md1:

raid10 kernel panic on sparc64

Hi, just when I did # mdadm -C /dev/md2 -b internal -e 1.0 -l 10 -n 4 /dev/sd[cdef]4 (created) # mdadm -D /dev/md2 Killed dmesg filled up with a kernel oops. A few seconds later, the box locked solid. Since I was only in by ssh and there is not (yet) any possibility to reset it remotely, this

Re: raid10 kernel panic on sparc64

From: Jan Engelhardt [EMAIL PROTECTED] Date: Mon, 2 Apr 2007 02:15:57 +0200 (MEST) just when I did # mdadm -C /dev/md2 -b internal -e 1.0 -l 10 -n 4 /dev/sd[cdef]4 (created) # mdadm -D /dev/md2 Killed dmesg filled up with a kernel oops. A few seconds later, the box locked solid. Since I

Desperate plea for help

I've recently had a raid 5 array fail on me - 2 drives suddenly just up and showed a failure. Of course this means that the metadata is stuffed. I've had a look at the howto and found the mdadm --assemble --force command but it's not working in this case. The 2 drives show up as spares. A friend