On Tue, 28 Mar 2000, Andreas Martmann wrote:
> Hello
>
> I have to install a RAID 1 System in order to mirror all partitions (exept the
> /boot partition, I think). The Problem is that I haven´t made this before, and I
> haven´t found a documentation that gives me the answers I need.
>
> There
I've ran old MD-utils since it come out and still running it, very heavly.
I've only had major problems, when there was hardware problems, of course
there are bugs in all software. I'd say to move up tho. Use the new
raid-utils. I don't do the boot-Raid, if you're not, you should be fine,
the ne
Hello
I have to install a RAID 1 System in order to mirror all partitions (exept the
/boot partition, I think). The Problem is that I haven´t made this before, and I
haven´t found a documentation that gives me the answers I need.
There are three HowTos available the old (normal) RAID HowTo for R
[[EMAIL PROTECTED]]
> I'm in the same boat. How do you enable IO-APIC support in the
> kernel?
CONFIG_SMP implies it, and recent 2.3.x (may have been backported)
will allow a UP kernel to use IO-APIC (Ingo's work) although I
haven't seen a machine (personally) where that's helpful :)
> What is
On Tue, Mar 28, 2000 at 12:47:08PM -0500, Seth Vidal wrote:
> > I'm a bit cautious here as I've had a bad experience when experimenting
> > with disk changing and ended up with a corrupted array.
Is it just me, or should the RAID superblock include information to make disk
ordering unimportant?
> I've got a four disk RAID5 setup on one controller. I want to add
> another controller, but am unsure of what strategy I should adopt to
> maintain the RAID integrity.
You didn't mention which raid kernel code you are using.
If it is recent, each partition will have `Persistent Super Block's
> I've got a four disk RAID5 setup on one controller. I want to add
> another controller, but am unsure of what strategy I should adopt to
> maintain the RAID integrity.
>
> As the order that the disks are found and identified as sda, sdb etc.
> determines the RAID structure and depends on the
Hi
I've got a four disk RAID5 setup on one controller. I want to add
another controller, but am unsure of what strategy I should adopt to
maintain the RAID integrity.
As the order that the disks are found and identified as sda, sdb etc.
determines the RAID structure and depends on the disk ID
On Tue, Mar 28, 2000 at 03:48:44PM +0200, Bernd Burgstaller wrote:
> (scsi0:0:0:0) Synchronous at 80.0 Mbyte/sec, offset 31.
> (scsi0:0:2:0) Synchronous at 20.0 Mbyte/sec, offset 15.
> (scsi0:0:3:0) Synchronous at 10.0 Mbyte/sec, offset 32.
> (scsi0:0:13:0) Synchronous at 80.0 Mbyte/sec, offset 31
> Dear all!
>
> I am writing this mail due to hangups related to my raid devices. I am
> seeking for suggestions enabling me to locate the problem. Any suggestions
> are welcome! Below you find a description of my system as well as of the
> problems. If you need further information, please let m
this is networking bug in 2.2.11
upgrade kernel to 2.2.14, get new raid patch and raid tools from
www.redhat.com/~mingo/
allan
Bernd Burgstaller <[EMAIL PROTECTED]> said:
> Dear all!
>
> I am writing this mail due to hangups related to my raid devices. I am
> seeking for suggestions enabling
On Tue, 28 Mar 2000, octave klaba wrote:
> Hi,
>
> > >From the CPU load on the raid-1 soft IDE test, I think seems likely that you
> > didn't have DMA enabled. Could that be possible ?
>
> how can I verify it ?
hdparm -v /dev/hd[ac]
See if using_dma is 0 or 1. If it's 0, either try a kerne
On Tue, 28 Mar 2000, Mike Bilow wrote:
> On Tue, 28 Mar 2000, Jakob Østergaard wrote:
>
...
> > >From the CPU load on the raid-1 soft IDE test, I think seems likely that you
> > didn't have DMA enabled. Could that be possible ?
> >
> > It doesn't make sense to have 97% CPU load when reading wi
Bernd Burgstaller <[EMAIL PROTECTED]> writes:
[...]
> The system contains 3 SCSI disks, detected by the kernel as follows:
>
> (scsi0) found at PCI 6/0
> (scsi0) Wide Channel, SCSI ID=7, 32/255 SCBs
> (scsi0) Downloading sequencer code... 374 instructions downloaded
> scsi0 : Adaptec AHA274x/2
Mike Bilow <[EMAIL PROTECTED]> wrote:
>...snip..
>However, if you have IO-APIC support enabled in the CMOS setup
>and in the Linux kernel, there should be no need for assignment
>of shared interrupts.
>...snip...
I'm in the same boat. How do you enable IO-APIC support in the
kernel?
>It is
please note:"Ultra" SCSI cable lengths are severely limited! The maximum
cable length is ten feet when four devices (including the host adapter) or
less are on the bus. If five devices are used (four devices and your host
adapter), then the maximum bus length is 1.5 meters (five feet!).
As I coun
How do you get interrupts 17 and 18 ???
--
Edward Schernau http://www.schernau.com
Network Architect mailto:[EMAIL PROTECTED]
Rational Computing Providence, RI, USA
Danilo Godec wrote:
>
> On Tue, 28 Mar 2000, Mike Bilow wrote:
>
> > I think you have an electrical issue.
>
> I feared that, but what should I do? It's all LVD and all pre-installed by
> Intel... except disks, of course.
Call for warranty service, I would think.
> Besides, it only happens eve
On Tue, 28 Mar 2000, Mike Bilow wrote:
> That's a hardware problem. A SCSI parity error is reported by the
> hardware and simply passed up the chain. Unless there is something
> seriously wrong in the aic7xxx sequencer code, which I doubt, this looks
> like a typical cabling and termination iss
Hi,
> >From the CPU load on the raid-1 soft IDE test, I think seems likely that you
> didn't have DMA enabled. Could that be possible ?
how can I verify it ?
Amicalement,
Octave
> no swap allowed <
On Tue, 28 Mar 2000, octave klaba wrote:
> > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU
> > > > 1° 2000 9212 96.4 20354 13.9 4411 3.6 3822 35.4 22180 8.0 85.6 0.7
> > > > 2° 2000 1727 22.4 2095 5.5 1381 34.9 3070 98.6 4320 97.8 74.8 7.3
> > > > 3° 2
> Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU
> > > 1° 2000 9212 96.4 20354 13.9 4411 3.6 3822 35.4 22180 8.0 85.6 0.7
> > > 2° 2000 1727 22.4 2095 5.5 1381 34.9 3070 98.6 4320 97.8 74.8 7.3
> > > 3° 2000 7236 91.6 18321 15.5 8003 13.7 8347 96.7 18
Dear all!
I am writing this mail due to hangups related to my raid devices. I am
seeking for suggestions enabling me to locate the problem. Any suggestions
are welcome! Below you find a description of my system as well as of the
problems. If you need further information, please let me know.
Bes
On Tue, Mar 28, 2000 at 08:22:22AM -0500, Mike Bilow wrote:
> > >From the CPU load on the raid-1 soft IDE test, I think seems likely that you
> > didn't have DMA enabled. Could that be possible ?
> >
> > It doesn't make sense to have 97% CPU load when reading with 4 MB/s unless
> > it's done wi
On Tue, 28 Mar 2000, Danilo Godec wrote:
> Mar 28 12:00:45 mail kernel: (scsi0:0:2:0) Parity error during Message-In phase
> Mar 28 12:00:45 mail kernel: (scsi0:0:2:0) Parity error during Data-In phase.
That's a hardware problem. A SCSI parity error is reported by the
hardware and simply passed
On Tue, 28 Mar 2000, Jakob Østergaard wrote:
> On Tue, 28 Mar 2000, octave klaba wrote:
>
> > Hi,
> >
> > a test between single ide <-> raid-1 soft ide <-> raid-1 soft scsi-2
> >
> > 1° PIII600/128RAM/1XIDE20.5
> > 2° PIII600/128RAM/2XIDE20.5 raid-1 soft
> > 3° PIII500/256/29
You can change the partition type at any time without stopping the array --
you won't lose any data either.
It's only used for partition management (i.e. fdisk, auto-RAID, etc).
Michael D. Black Principal Engineer
[EMAIL PROTECTED] 321-676-2923,x203
http
Today, I had another SCSI failure. I was able to get a bit more of dmesg
stuff, but can't figure out, what is going wrong there.
In /var/log/messages, the unusuall stuff starts with this repeated a
couple of times:
Mar 28 12:00:45 mail kernel: (scsi0:0:2:0) Parity error during Message-In phase
M
On Tue, 28 Mar 2000, octave klaba wrote:
> Hi,
>
> a test between single ide <-> raid-1 soft ide <-> raid-1 soft scsi-2
>
> 1° PIII600/128RAM/1XIDE20.5
> 2° PIII600/128RAM/2XIDE20.5 raid-1 soft
> 3° PIII500/256/2940U2W/SCSI-2/RAID-1/IBM18Go7200
>
> ---Sequential
Hi,
a test between single ide <-> raid-1 soft ide <-> raid-1 soft scsi-2
1° PIII600/128RAM/1XIDE20.5
2° PIII600/128RAM/2XIDE20.5 raid-1 soft
3° PIII500/256/2940U2W/SCSI-2/RAID-1/IBM18Go7200
---Sequential Output ---Sequential Input-- --Random--
-Pe
The aic7xxx driver is definitely unstable in my experience on SMP when
shared interrupts are used. It will usually hang on boot in this case.
This is an especially annoying problem because many SMP motherboards will
insist on assigning interrupts automatically; Intel and Supermicro are
particul
Hi,
I had (or have) similar hangs (all frozen, no syslog-entry, kernel still
running since ping works, but all user-level stuff hangs). The hardware in
my case is a onboard AIC-7890, an additional AHA-394X, a 3com 3c905B. All
on a Dual-PIII-450 on a Asus motherboard running raidutils 0.9 on a
SMP
I have not really done this yet, but
if [ ! -e /proc/mdstat ] || \
[ `grep -ci resync /proc/mdstat` -eq 0 ] ; then
swapon -a
fi
seems like a reasonable approach. Martin Bene posted a slightly different
variant which waits until remirroring is done and then st
33 matches
Mail list logo
