Summary: Problem with LVM: Both submirrors "need maintenance"
2007-12-25 3:51:00
and thanks to ponder at discworld.be, David Loesche (DLoesche at yipes.com),
Scott Beardsley (thebofh at gmail.com), Gary Law (shunhelp1 at lycos.com) and
Michael Schulte (msu.linux at gmx.de) for responding to my question.
Hmm, most of you suggested to detach and re-attach the mirror, or try to
enable the second mirror first. I did this, and even deleted the entire
mirror, updated /etc/vfstab and /etc/system to tell the machine to boot
from the original disk, re-booted it, and created the mirrors again from
scratch.
Unfortunately, nothing helped me out...
So, I've issued a maintenance window for tomorrow evening. I will try to
shutdown the machine to single-user, and fsck the device to get rid of
the errors.
Let's hope I get it workin' again, if not, I will have to recover from
backup.
Thanks to all,
have a nice hackin',
Harald
On Mon, 2004-08-16 at 13:39, Harald Husemann wrote:
> Hi gurus,
>
> I have a big problem here with Solaris Volume Manager on a V240, running
> Sol. 9.
>
> One of the mirrors (unfortunately the root-mirror...) is in
> maintenance-state:
>
> root at plato # metastat d10
> d10: Mirror
> Submirror 0: d11
> State: Needs maintenance
> Submirror 1: d12
> State: Needs maintenance
> Pass: 1
> Read option: roundrobin (default)
> Write option: parallel (default)
> Size: 62211726 blocks (29 GB)
>
> d11: Submirror of d10
> State: Needs maintenance
> Invoke: after replacing "Maintenance" components:
> metareplace d10 c1t0d0s0 <new device>
> Size: 62211726 blocks (29 GB)
> Stripe 0:
> Device Start Block Dbase State Reloc Hot Spare
> c1t0d0s0 0 No Last Erred Yes
>
>
> d12: Submirror of d10
> State: Needs maintenance
> Invoke: metasync d10
> Size: 62211726 blocks (29 GB)
> Stripe 0:
> Device Start Block Dbase State Reloc Hot Spare
> c1t1d0s0 0 No Okay Yes
>
>
> Device Relocation Information:
> Device Reloc Device ID
> c1t0d0 Yes id1,sd at SSEAGATE_ST336607LSUN36G_3JA7CQQX0000743600J4
> c1t1d0 Yes id1,sd at SSEAGATE_ST336607LC______3JA14LFQ00007311AATB
>
> Okay, I tried a metareplace:
>
> root at plato # metareplace -e d10 c1t0d0s0
> metareplace: plato: d10: c1t0d0s0: component in invalid state to replace
> - Replace "Maintenance" components first
>
> root at plato #
>
> Hm, well, the the metasync first. The sync starts, and after syncing
> abt. 8%, it stops without any message.
>
> I hope, anyone out there has an idea what I can do to fix this? It's a
> productive machine, so rebooting it would not be a good idea...
>
> Thanks a lot,
>
> Harald
Comments
Got something to say?
You must be logged in to post a comment.
