Dave> Good afternoon, all. I'm wondering if anyone has
Dave> anything good or bad to say about kernel-resident raid
Dave> implementations using the recent large ide disks. 160 gig for
Dave> $199, 640 gb = $800, on a pc. raid 5, 480 gig. And that's
Dave> without using pci ide-bus expansion cards.
Which kernel and which raid tools are you using? Details are
important here!
Dave> I'm using a raid 0 set of 3 disks (wdc, maxtor) to transfer a
Dave> few hundred gig of jpgs between two sites. The pc (dell gx150)
Dave> has some hardware problems, eth cards have to be reseated each
Dave> time it's moved.
This is a huge warning sign!! If the hardware is know flaky, then you
shouldn't be using it.
Also, you should be using RAID5 in this case, since you want to be
able to handle a disk dying.
Dave> The raid set worked fine in testing, but after moving the pc to
Dave> the second site, a cpio failed at only 77 gig with: cpio: write
Dave> error: No space left on device. The raid set is 390 gb, and was
Dave> filled to about 270 during testing, with no problems. Copying
Dave> files off it after that, returned some i/o errors, below.
Dave> So, lots of space, but flaky? Are hardware controllers the
Dave> better choice?
I doubt it, getting a better motherboard and PC would be a better
choice. I'd also look into getting
Dave> tar: ./10.gz: Read error at byte 49152, reading 10240 bytes: Input/output
Dave> error
Dave> tar: ./10.gz: File shrank by 1096222 bytes; padding with zeros
Dave> cp: cannot stat `/z/27': Input/output error#
Dave> cp: reading `/z/73.gif': Input/output error
Dave> cp: reading `/z/75.gif': Invalid argument
Dave> cpio: ./net: Value too large for defined data type
Dave> cpio: ./inc: unknown file type
None of this really helps, did you look in /var/log/messages for any
info in there? Did you check the status of the RAID array before and
after you moved it? Did you shutdown and power off the system at the
source site, then power it back up and reboot to check the system?
In this case, I really think you need to use better hardware before
you start chasing software bugs.
John
John Stoffel - Senior Unix Systems Administrator - Lucent Technologies
[EMAIL PROTECTED] - http://www.lucent.com - 978-399-0479
---
Send mail for the `bblisa' mailing list to [EMAIL PROTECTED]'.
Mail administrative requests to [EMAIL PROTECTED]'.
