stinkingpig Wrote: > ....[color=blue]24x7 use is not that big a factor in my opinion, the > heat of 4 drives in a case designed for 1 hdd and some removable media > drives is more likely what kills the drives. sorry, not true from my experience. if a drive runs 24/7 for 2-3 years you really get a chance to see a failure. As posted befroe, this was quite a surprise to me as well...
stinkingpig Wrote: > ....[color=blue]1) rebuilding a RAID 5 array after losing a drive takes > a very long time.Like days and days. I haven't tried it with a SOHO > RAID card and some el cheapo IDE drives, but top-of-the-line HPAQ and > Dell cards with fast SCSI drives sure do suck. true , but doesn't care. The RAID 5 is fully functional during degraded mode (lost one drive) and during resyncing a new one. THis is really a great feature that minimizes downtime. stinkingpig Wrote: > ....[color=blue]2) Lose two from a RAID 5 array, you've lost it all. > Since people usually build arrays by buying the same drives from the > same manufacturer at the same time, chances of losing two at once are > remarkably high. True, but if you use RAID 6 the system can cope with two faulty drives. RAID 6 comes for free as software raid with kernel 2.6 and it works great. stinkingpig Wrote: > ....[color=blue]3) What about subtle drive errors which produce drive > corruption? I once lost a RAID 1 mirror because the failing drive > caused file system corruption on its way out. By the time that the > drive actually failed enough for LVM to notice and take it out of the > array, the "RAID protected" filesystem was trash. In "buy two drives > and copy the content", the copy fails when one of the drives doesn't > work perfectly. If you're using hard link backups, you don't trash the > copy, so you still have a backup. You are right, if the drive does bad things without raising error conditions on the IDE channel, than you are in hell. But that is a risk you do always take. For example, if you do copy the drive to a backup drive on a device-level, than you also get the inconsistent filesystem on the backup and your are lost as well. If you do it on a filesystem level than you already have replaced a part of your backup when you get aware of the problem. So this problem is not raid specific. Up to now I did not experience this type of error with my raids. But may be I just had luck :-) The advice to copy the whole stuff to a second drive is a bit hard to realize when you have 3 TB to move around. But may be that is my specific problem as well :-)) -- docbee ------------------------------------------------------------------------ docbee's Profile: http://forums.slimdevices.com/member.php?userid=26 View this thread: http://forums.slimdevices.com/showthread.php?t=18555 _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
