the error message was probably something like 'unsupported raid array
version'? Use the --upgrade switch in mkraid, it upgrades your array
without losing data. But the 0.90 driver is still alpha, so be careful.
-- mingo
On Mon, 9 Nov 1998, Fabio Mirotti wrote:
>
>
> Just a question:
>
MOLNAR Ingo wrote:
>
> hm, md.c line 1400 is because there is some invalid sort of chunksize in
> the superblock. what chunksize have you specified?
>
> Ingo
>
Good question, actually I don't know what the original chunksize was
prior
to changing raidtab & running "mkraid --upgrade", I
Hi,
On Fri, 06 Nov 1998 16:44:56 -0400 (EST), Dave Wreski <[EMAIL PROTECTED]>
said:
>> Me, for a start! I found it very useful to be able to combine together
>> a few scraps of spare space on a number of mounted disks to create a
>> scratch partition of useful size.
> Why not use striping inst
Hi,
On Fri, 6 Nov 1998 15:59:04 +0100, Luca Berra <[EMAIL PROTECTED]> said:
>> > freeze the log, backup, unfreeze like vxfs (Veritas) does
>>
>> A lfs does make this easier, yes, but there are other ways to do it. In
>> particular, you can achieve the same effect at the block device level if
>
From: MOLNAR Ingo <[EMAIL PROTECTED]>
> kernel 2.1.125 and 2.0.35. (a 2.1.127 port will follow as soon as 2.1.127
> gets out) Also this package contains a prototype (kernel-space and MD
I did follwing operations...
# cd /usr/src
# rm -rf ./linux
# bzip2 -cd linux-2.1.127.tar.bz2 | tar xf -
# c
Here are some stats on a 16-bit fast wide single-channel ICP Vortex PCI
RAID-5 card on a 3-drive array.
The drives are Fujitsu 9.1 Gig narrow M2949 drives (14.x Meg/sec
theoretical limit on speed). The system is a 233MHz Supermicro Pentium MMX
on Redhat Linux 5.1, with 128 Megs of RAM. When I r
Just a question:
My machine is running a patched kernel-2.1.115
and raidtools 0.50 in RAID1 configuration.
I'd like to upgrade kernel & raidtools.
I tried a to patch a kernel 2.1.124 & install
raidtools 0.90 but my system couldn't boot
I have got a '1 out of 9 hunks FAILED' when apply the raidtools patch,
will it affect anything?
Your opiniion are highly appreciated...
Kent
Quoth Mark J. Bailey.
>
>Is there any
>possible problems having BOTH a PM3334UDW and a PM2144UW controller in
>the same box?
FWIW, we've a PM3334UW running an external DPT RAID box and a PM2144UW
in out main box here (the 2144's just running a scanner though). No
conflicts.
The 3334 and ex
Hi,
I don't know if this problem got treated yet, because I just joined this
list, so here goes:
I just installed the newest raid-patches (19981106-C) into a 2.0.35
kernel, and I also use the newest tools (19981105-0.90).
I gave all my raid-partitions the 0xfd type, but the kernel only finds t
I've connected a few SCSI-disks to one of my SUN ELC's, running
Linux/SPARC 2.0.35. I've setup an /etc/mdtab with mdcreate so that;
| /dev/md0raid0,4k,0,1c2518a6 /dev/sdb3 /dev/sdc3
but whenever I run mdadd -a I get the following errors;
| beldaran:~# mdadd -a
| /dev/sdb3: Device or
11 matches
Mail list logo
