Mitchell Laks wrote:
Hi,
I have a production server in place at a remote site.
I have a single system drive that is an ide drive
and two data drives that are on a via SATA controller in a raid1
configuration.
I am monitoring the /var/log/messages and I get messages every few days
Mar 22
Brad Campbell wrote:
I've been running 3 together in one box for about 18 months, and four in
another for a year now... the on board BIOS will only pickup 8 drives,
but they work just fine under Linux and recognise all connected drives.
What distro and kernel ?
I tried this about 2 - 3
Christopher Smith wrote:
Brad Campbell wrote:
I've been running 3 together in one box for about 18 months, and four
in another for a year now... the on board BIOS will only pickup 8
drives, but they work just fine under Linux and recognise all
connected drives.
What distro and kernel ?
On Sat, 2006-03-25 at 21:38 -0800, dean gaudet wrote:
On Sat, 25 Mar 2006, Alex Izvorski wrote:
http://linuxraid.pastebin.com/621363 - oprofile annotated assembly
it looks to me like a lot of time is spent in __find_stripe() ... i wonder
if the hash is working properly.
in raid5.c
On Sat, 1 Apr 2006, Alex Izvorski wrote:
Dean - I think I see what you mean, you're looking at this line in the
assembly?
65830 16.8830 : c1f: cmp%rcx,0x28(%rax)
yup that's the one... that's probably a fair number of cache (or tlb)
misses going on right there.
I looked at
Mar 29 23:33:26 A1 kernel: ata6: status=0x51 { DriveReady SeekComplete Error
}
Mar 29 23:33:26 A1 kernel: ata6: error=0x84 { DriveStatusError BadCRC }
BadCRC is unambiguous: the packet was corrupted. that could happen several
ways, the most common of which is bogus cables (remember, PATA is
