Bill Davidsen [EMAIL PROTECTED] writes:
Goswin von Brederlow wrote:
Hi,
I would welcome if someone could work on a new feature for raid5/6
that would allow replacing a disk in a raid5/6 with a new one without
having to degrade the array.
Consider the following situation:
raid5 md0 : sda
BERTRAND Joël [EMAIL PROTECTED] writes:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
5426 root 15 -5 000 R 100 0.0 46:32.54
md_d0_raid5
First: You can tune the stripe cache.
Secondly: You might want the raid speedup patches that implement
Konstantin Sharlaimov [EMAIL PROTECTED] writes:
This patch adds RAID1 read balancing to device mapper. A read operation
that is close (in terms of sectors) to a previous read or write goes to
the same mirror.
I wonder if there shouldn't be a way to turn this off (or if there
already is one).
Janek Kozicki [EMAIL PROTECTED] writes:
Hi,
I finished copying all data from old disc hdc to my shiny new
RAID5 array (/dev/hda3 /dev/sda3 missing). Next step is to create a
partition on hdc and add it to the array. And so I did this:
# mdadm --add /dev/md1 /dev/hdc3
But then I had a
Bill Davidsen [EMAIL PROTECTED] writes:
Janek Kozicki wrote:
Hello,
My three HHDs have following speeds:
hda - speed 70 MB/sec
hdc - speed 27 MB/sec
sda - speed 60 MB/sec
They create a raid1 /dev/md0 and raid5 /dev/md1 arrays. I wanted to
ask if mdadm is trying to pick the
Neil Brown [EMAIL PROTECTED] writes:
On Thursday November 1, [EMAIL PROTECTED] wrote:
Hello,
I have raid5 /dev/md1, --chunk=128 --metadata=1.1. On it I have
created LVM volume called 'raid5', and finally a logical volume
'backup'.
Then I formatted it with command:
mkfs.ext3 -b
Janek Kozicki [EMAIL PROTECTED] writes:
Doug Ledford said: (by the date of Sat, 03 Nov 2007 14:40:48 -0400)
so you really only need to align the
lvm superblock so that data starts at 128K offset into the raid array.
Sorry, I thought that it will be easier to figure this out
Lyle Schlueter [EMAIL PROTECTED] writes:
Hello,
I just started looking into software raid with linux a few weeks ago. I
am outgrowing the commercial NAS product that I bought a while back.
I've been learning as much as I can, suscribing to this mailing list,
reading man pages, experimenting
Lyle Schlueter [EMAIL PROTECTED] writes:
Do you know of any concerns of using all the ports on a motherboard?
Slowdowns or anything like that?
More likely the opposite. But it depends on how the chips are
connected.
On desktop boards the onboard chip is in the north and/or southbridge
and has
Dan Williams wrote:
On Tue, 2007-11-06 at 03:19 -0700, BERTRAND Joël wrote:
Done. Here is obtained ouput :
Much appreciated.
[ 1260.969314] handling stripe 7629696, state=0x14 cnt=1, pd_idx=2 ops=0:0:0
[ 1260.980606] check 5: state 0x6 toread read
Chuck Ebbert wrote:
On 11/05/2007 03:36 AM, BERTRAND Joël wrote:
Neil Brown wrote:
On Sunday November 4, [EMAIL PROTECTED] wrote:
# ps auxww | grep D
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root 273 0.0 0.0 0 0 ?DOct21 14:40
Janek Kozicki wrote:
Goswin von Brederlow said: (by the date of Wed, 07 Nov 2007 10:17:51 +0100)
Strange. That is exactly how I always do it and it always just worked.
mdadm should start syncing on any spare as soon as a disk fails or you
add the spare to a degraded array afaik. No
Goswin von Brederlow said: (by the date of Wed, 07 Nov 2007 10:17:51 +0100)
Strange. That is exactly how I always do it and it always just worked.
mdadm should start syncing on any spare as soon as a disk fails or you
add the spare to a degraded array afaik. No special start now
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
So I was able to get the Adaptec kernel module uncompiled (YES! :)). I
followed the instructions and now when I run 'make menuconfig' I see
that I can make the ADPAHCI a module of the kernel under Device Drivers
- - SCSI (I belive) - Low-level -
On 11/05/2007 03:36 AM, BERTRAND Joël wrote:
Neil Brown wrote:
On Sunday November 4, [EMAIL PROTECTED] wrote:
# ps auxww | grep D
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
root 273 0.0 0.0 0 0 ?DOct21 14:40
[pdflush]
root
Hi,
While on vacation I had one SATA port/cable fail, and then four hours later a
second one fail. After fixing/moving the SATA ports, I can reboot and all
drives seem to be OK now, but when assembled it won't recognize the filesystem.
After futzing around with assemble options like --force
16 matches
Mail list logo
