From: Rasheed Darras (rasheed@anet.net.sa)
Date: Tue Feb 03 2004 - 05:39:55 EST
Thanks to all of you for replies.
Let me clarify more things.
At the time of this problem happened, the error I found on the console
was:-
############################################
panic[cpu0]/thread=2a1000f1d40: md: Panic due to lack of DiskSuite state
database replicas. Fewer than 50% of the total were available, so panic to
ensure data integrity.
000002a1000f1490 md:mddb_commitrec_wrapper+84 (2, 2a1000f15fc, 18, 14, 0,
ff00)
%l0-3: 0000000000000000 0000000000000001 0000000000000002 0000000000000003
%l4-7: 00000000011d8bf8 00000000014bac00 000003000038c2e0 0000030000280dd8
000002a1000f1540 md:setshared_name+2d8 (0, 30000079750, 0, 2a1000f16b0,
ffffffffffffffff, 10)
%l0-3: 000003000038c2e0 0000000000000000 0000030000280dd8 0000000000000001
%l4-7: 0000000000000003 0000000000000000 0000000000000000 0000030000280da0
000002a1000f1600 md:md_resolve_bydevid+1bc (1f, ffffffffffffffff, 5,
30001106000, 3c, 0)
%l0-3: 0000002000000003 0000002000000003 0000000000000000 00000000014bb1d8
%l4-7: 000000000004c318 0000030000280dc8 0000030000384978 0000000081010100
000002a1000f16c0 md_stripe:stripe_open_all_devs+100 (30000291ce0, 3, 0, 1,
0, 2a100525aec)
%l0-3: 0000030000291d00 0000000000000005 0000000000000000 0000000000000000
%l4-7: 0000000000000002 0000030000291d00 000000000000001f 0000000000000000
000002a1000f17a0 md_stripe:stripe_open+70 (2a1000f1908, 3, 4, 30000265f28,
3, ffbffb81)
%l0-3: 0000000000000003 000002a1000f1d40 00000000000005a0 000000000000001f
%l4-7: 000003000006acb8 0000030000291c78 000003000000e9c0 0000030005a18440
000002a1000f1850 md:md_layered_open+bc (1495c00, 2a1000f19c8, 3, 0, 1400000,
3000005ff50)
%l0-3: 000000000000001e 0000000000000001 000003000006acb8 ffffffffffffffff
%l4-7: 0000030000265f28 0000000000000055 0000000000000000 000003000039ea20
000002a1000f1910 md_mirror:mirror_probe_dev+ac (3000006a858, 1e,
30002579488, 1438518, 16, 0)
%l0-3: 0000000000000001 000000000000001e 0000000000000001 000000000000ffff
%l4-7: 000003000006a858 000000000000001e 0000030000279508 0000030000279508
000002a1000f19d0 md:md_probe_one+40 (30005a184c0, 2a1000f1d40, 20, 14a64a0,
2a1000f1d40, 0)
%l0-3: 00000000012f1574 00000000014bb1d0 000003000027a098 000003000000e930
%l4-7: 000003000000e958 000000000142e488 0000000001443000 0000030000296488
000002a1000f1a80 md:md_daemon+220 (0, 14bb1a0, 1438518, 1438518,
2a1000fdd40, 0)
%l0-3: 00000000011d5674 0000030005a184c0 0000000000000000 000002a1000f7d40
%l4-7: 00000000014bb1d0 00000000014bb1c8 0000000000000000 000003000025a000
syncing file systems... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 done (not
all i/o completed) dumping to /dev/dsk/c1t0d0s1, offset 65536, content:
kernel
0% done: 0 pages dumped, compression ratio 0.00, dump failed: error 5
rebooting...
############################################
What I did is to go to single mode and do fsck to all disks then I tried to
reboot the system.Run successfully.
But I don't want such things to happened again, so I add additional 6
replicas in the second disk :-
############################################
flags first blk block count
a m p luo 16 8192 /dev/dsk/c1t0d0s7
a p luo 8208 8192 /dev/dsk/c1t0d0s7
a p luo 16400 8192 /dev/dsk/c1t0d0s7
a p luo 24592 8192 /dev/dsk/c1t0d0s7
a p luo 32784 8192 /dev/dsk/c1t0d0s7
a p luo 40976 8192 /dev/dsk/c1t0d0s7
a u 16 8192 /dev/dsk/c1t1d0s7
a u 8208 8192 /dev/dsk/c1t1d0s7
a u 16400 8192 /dev/dsk/c1t1d0s7
a u 24592 8192 /dev/dsk/c1t1d0s7
a u 32784 8192 /dev/dsk/c1t1d0s7
a u 40976 8192 /dev/dsk/c1t1d0s7
############################################
And I added to the /etc/system "set md:mirrored_root_flag=1" before the MDD
root added by DiskSuite:-
############################################
set md:mirrored_root_flag=1
* Begin MDD root info (do not edit)
forceload: misc/md_trans
############################################
Is this enough or I have to do additional steps?
Rasheed
----- Original Message -----
From: "Rasheed Darras" <rasheed@anet.net.sa>
To: "Sun Managers" <sunmanagers@sunmanagers.org>
Sent: Monday, February 02, 2004 2:36 PM
Subject: DiskSuite Panic
> Dears,
>
>
> I have configured my Sun-Fire-V210 5.9 Solaris with DiskSuite 4.2.1...
>
> One day my system panic and I found this message on the console :-
>
>
>
> #####################
>
> panic[cpu0]/thread=2a1000f1d40: md: Panic due to lack of DiskSuite state
database replicas. Fewer than 50% of the total were available, so panic to
ensure data integrity.
>
> 000002a1000f1490 md:mddb_commitrec_wrapper+84 (2, 2a1000f15fc, 18, 14, 0,
ff00)
>
> %l0-3: 0000000000000000 0000000000000001 0000000000000002
0000000000000003
>
> %l4-7: 00000000011d8bf8 00000000014bac00 000003000038c2e0
0000030000280dd8 000002a1000f1540 md:setshared_name+2d8 (0, 30000079750, 0,
2a1000f16b0, ffffffffffffffff, 10)
>
> .
>
> #####################
>
>
>
> I have two internal 36GB disks ,put I have configured 6 replicas on one
disk !!!I know now that I have to configured 3 replicas on each disk.But my
system in production now so what is the steps to redo this in fast time
without having down time ( or not more than 15 min down). Thanks,Rasheed
> _______________________________________________
> sunmanagers mailing list
> sunmanagers@sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
_______________________________________________
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:57 EDT