From: The Funks (funks@nauticom.net)
Date: Wed Dec 17 2003 - 20:06:01 EST
Hi All,
Thanks for all your input you guys are amazing! I used Soltice Disksuite
4.2.1 (free download from SUN)
The client wanted to go with a RAID5 config.
So.....I installed Soltice Disksuite 4.2.1 and implemented a Raid5 config (I
think :-\ )
I used 3 slices from 3 different disks with each slice at 4gb.
With SDS I made these slices replicas then moved them onto raid.
then
ran metastat d0
d0: RAID
State: Okay
Interlace: 32 blocks
Size: 25157368 blocks
Original device:
Size: 25161024
Device Start Block Dbase
State Hot Spare
c0t9d0s0 5042 Yes
Okay
c0t8d0s3 5042 Yes
Okay
c0t12d0s0 5042 Yes
Okay
c0t12d0s1 5042 Yes
Okay
Is this all I do?????????
Please let me know what I am missing.
How does the data become redundant? Does all data written become redundant
automagically or do I specify which filesystems?
Also, every time I reboot I get the following errors/warnings:
/dev/rdsk/c0t9d0s7: I/O error
Can't open /dev/rdsk/c0t9d0s7
/dev/rdsk/c0t9d0s7: CAN'T CHECK FILE SYSTEM.
/dev/rdsk/c0t9d0s7: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/rdsk/c0t8d0s4: I/O error
Can't open /dev/rdsk/c0t8d0s4
/dev/rdsk/c0t8d0s4: CAN'T CHECK FILE SYSTEM.
/dev/rdsk/c0t8d0s4: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
WARNING - Unable to repair one or more of the following filesystem(s):
/dev/rdsk/c0t0d0s7 /dev/rdsk/c0t9d0s7 /dev/rdsk/c0t11d0s7
/dev/rdsk/c0t8d0s0
/dev/rdsk/c0t8d0s1 /dev/rdsk/c0t8d0s3 /dev/rdsk/c0t8d0s4
/dev/rdsk/c0t10d0
Run fsck manually (fsck filesystem.).
Type control-d to proceed with normal startup...
Is there a fix for this mess?
TIA,
MF
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:27:42 EDT