2007/10/26, Jake Conk <jake.conk@gmail.com>:
quoted text
> Hello,
>
> I was trying to restart my server and noticed it wasn't coming back
> online so when I went down to go take a look at it I was having a RAID
> problem. This is what was showing on the screen:
>
> ...
> PARTIALLY TRUNCATED INODE I=720
> THE FOLLOWING SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
> [...]
> My question is what causes this? How can I be warned before a problem
> like this happens and what's the best way to prevent this from coming
> up? And lastly, is it possible in the worst case scenario if one of my
> disks is completely fsck'ed up is it possible to run the system on 1
> of the raid 1 disks until a second comes?

Your problem is related to filesystem, not disks. For some reasons
your filesystem (on top of raid) was not properly unmounted: assuming
you didn't hard-reboot your server, this happened to me whith some IDE
devices which lied about commit of write operations. Even if my server
was rebooted normally, filesystem and disks were left in an
inconsistent state. Better SCSI disks solved the problem. Hardware has
become more crappy day by day.
RAID in general keeps your system up if a disk fails, not if
filesystem on top of it screws up.

f.