From: John Adams (jna@retina.net)
Date: Wed Feb 26 2003 - 07:51:39 EST
Hello sun-managers, I've got a question for you.
I have a 8 disk A1000 that has 8 disks in it, and I've constructed a
RAID5 out of it:
db3:/# metastat
d10: RAID
State: Okay
Hot spare pool: hsp001
Interlace: 128 blocks
Size: 355612788 blocks
Original device:
Size: 355614720 blocks
Device Start Block Dbase State Hot Spare
c3t2d0s2 4179 No Okay
c3t3d0s2 4179 No Okay
c3t8d0s2 4179 No Okay
c3t9d0s2 4179 Yes Okay
c3t10d0s2 4179 Yes Okay
c3t11d0s2 4179 Yes Okay
hsp001: 2 hot spares
c3t0d0s2 Available 71127180 blocks
c3t1d0s2 Available 71127180 blocks
All of the labels are exactly the same, and my metadb slices are shared
with data slices (this is supported, from what I've read).
I can successfully newfs this filesystem (/dev/md/dsk/d10)....
Rounded cgsize up to 48
/dev/md/rdsk/d10: 355612788 sectors in 123092 cylinders of 27
tracks, 107 sectors
173639.1MB in 3847 cyl groups (32 c/g, 45.14MB/g, 5632 i/g)
... but attempts to mount the filesystem produce this error:
db3:/# mount /dev/md/dsk/d10 /raid
mount: /dev/md/dsk/d10 is not this fstype.
Any thoughts to what could be causing this? I've rebooted several times,
attempted to re-create the volume, but nothing works. I can't even fsck
the new volume either:
db3:/# fsck /dev/md/rdsk/d10
** /dev/md/rdsk/d10
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION;
eg. fsck [-F ufs] -o b=# [special ...]
where # is the alternate super block. SEE fsck_ufs(1M).
db3:/#
Thanks for any help you can give. This should be ultimately simple, but it
hasn't proven to work yet!
--john
-- J. Adams http://www.retina.net/~jna The secret of knowing where you are, is knowing what time it is. -- Anonymous _______________________________________________ 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:25:53 EDT