SUMMARY: Re: weird metadevice problem

From: Adam and Christine Levin <>
Date: Tue Feb 25 2003 - 13:58:07 EST
Original problem at the bottom.

Thanks to those who responded, especially
Cris Lovett <>
"Harrington, David B. (Contractor) (DSCR)" <>

Unfortunately, I've spoken to Sun and it appears that the problem is a
serious one.  There's a bug in Disksuite 4.2.1, bugid 4633012, that causes
this problem.  They're working on a new version of the 4.2.1 patch,
revision 15, that supposedly fixes this problem, but it only fixes it in
that it won't happen again.  It will not fix the current problem.  I'm
being told to recreate the volume and restore from backups.

Considering that hot-sparing and restoring RAID5 volumes and slices is
something fundamental to disksuite, I'm a little miffed at Sun.


On Wed, 19 Feb 2003, Adam and Christine Levin wrote:
> Enterprise E450, disks on a bunch of D1000 arrays, Solaris 8.
> We had a disk go bad in a RAID5 volume.  It hot-spared automatically.  We
> replaced the bad disk and relabelled it in format so that it's got the
> same partition layout as the original bad disk and the hot-spare.
> Then, we run metareplace:
> # metareplace -e d60 c3t9d0s0
> metareplace: [hostname]: c3t9d0s0: No space left on device
> I've seen that error when we forgot to relabel a factory-fresh disk, but
> I've confirmed that the partition layout is identical, so I don't know
> what's going on here.  Any thoughts?
> Thanks much,
> -Adam
sunmanagers mailing list
Received on Thu Feb 27 11:44:23 2003

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:04 EST