亚洲av成人无遮挡网站在线观看,少妇性bbb搡bbb爽爽爽,亚洲av日韩精品久久久久久,兔费看少妇性l交大片免费,无码少妇一区二区三区

Chinaunix

標(biāo)題: 求助SDS鏡象重啟完后總是有幾個(gè)分區(qū)需要needs maintenance [打印本頁(yè)]
作者: tootooluu    時(shí)間: 2006-08-15 19:23
標(biāo)題: 求助SDS鏡象重啟完后總是有幾個(gè)分區(qū)需要needs maintenance
ultra 10 機(jī)器，solaris 6 + disksuite  4.2，20G硬盤

       0. c0t0d0 <ST320011A cyl 39533 alt 2 hd 16 sec 63>
          /pci@1f,0/pci@1,1/ide@3/dad@0,0
       1. c0t3d0 <ST320420A cyl 39533 alt 2 hd 16 sec 63>
          /pci@1f,0/pci@1,1/ide@3/dad@3,0

做鏡象，做完后同步一切正常，但一重啟動(dòng)，就會(huì)出現(xiàn)某些分區(qū)needs maintenance

d30: Mirror
    Submirror 0: d10
      State: Okay         
    Submirror 1: d20
      State: Needs maintenance
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 6086304 blocks

d10: Submirror of d30
    State: Okay         
    Size: 6086304 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s0                   0     No    Okay         


d20: Submirror of d30
    State: Needs maintenance
    Invoke: metareplace d30 c0t3d0s0 <new device>
    Size: 6086304 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s0                   0     No    Maintenance  


d31: Mirror
    Submirror 0: d11
      State: Okay         
    Submirror 1: d21
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 1049328 blocks

d11: Submirror of d31
    State: Okay         
    Size: 1049328 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s1                   0     No    Okay         


d21: Submirror of d31
    State: Okay         
    Size: 1049328 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s1                   0     No    Okay         


d32: Mirror
    Submirror 0: d12
      State: Okay         
    Submirror 1: d22
      State: Needs maintenance
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 6291936 blocks

d12: Submirror of d32
    State: Okay         
    Size: 6291936 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s4                   0     No    Okay         


d22: Submirror of d32
    State: Needs maintenance
    Invoke: metareplace d32 c0t3d0s4 <new device>
    Size: 6291936 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s4                   0     No    Maintenance  


d33: Mirror
    Submirror 0: d13
      State: Okay         
    Submirror 1: d23
      State: Needs maintenance
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 3145968 blocks

d13: Submirror of d33
    State: Okay         
    Size: 3145968 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s5                   0     No    Okay         


d23: Submirror of d33
    State: Needs maintenance
    Invoke: metareplace d33 c0t3d0s5 <new device>
    Size: 3145968 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s5                   0     No    Maintenance  


d34: Mirror
    Submirror 0: d14
      State: Okay         
    Submirror 1: d24
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 12583872 blocks

d14: Submirror of d34
    State: Okay         
    Size: 12583872 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s6                   0     No    Okay         


d24: Submirror of d34
    State: Okay         
    Size: 12583872 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s6                   0     No    Okay         


d35: Mirror
    Submirror 0: d15
      State: Okay         
    Submirror 1: d25
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 10486224 blocks

d15: Submirror of d35
    State: Okay         
    Size: 10486224 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s7                   0     No    Okay         


d25: Submirror of d35
    State: Okay         
    Size: 10486224 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s7                   0     No    Okay         


用metareplace修復(fù)，依然報(bào)錯(cuò)
/usr/opt/SUNWmd/sbin/metareplace -e d30 c0t3d0s0
# WARNING: md: d20: write error on /dev/dsk/c0t3d0s0
WARNING: md: d20: /dev/dsk/c0t3d0s0 needs maintenance

懷疑硬盤故障，更換新硬盤，重裝操作系統(tǒng)，故障依然，非常茫然，求助各位大大��！

# more /etc/vfstab
#device         device          mount           FS      fsck    mount   mount
#to mount       to fsck         point           type    pass    at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr          ufs     1       yes     -
fd      -       /dev/fd fd      -       no      -
/proc   -       /proc   proc    -       no      -
/dev/md/dsk/d31 -       -       swap    -       no      -
/dev/md/dsk/d30 /dev/md/rdsk/d30        /       ufs     1       no      logging
/dev/md/dsk/d32 /dev/md/rdsk/d32        /usr    ufs     1       no      logging
/dev/md/dsk/d33 /dev/md/rdsk/d33        /var    ufs     1       no      logging
/dev/md/dsk/d35 /dev/md/rdsk/d35        /bak    ufs     1       no      logging
/dev/md/dsk/d34 /dev/md/rdsk/d34        /usr1   ufs     1       no      logging
swap    -       /tmp    tmpfs   -       yes     -

系統(tǒng)補(bǔ)丁升級(jí)到105181-39，disksuite補(bǔ)丁到106627-11。
另外，是在多用戶模式下！

# who -r
   .       run-level 3  Aug 15 19:18     3      0  S

# df -k
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/md/dsk/d30      2978534   32409 2886555     2%    /
/dev/md/dsk/d32      3095966  400349 2633698    14%    /usr
/proc                      0       0       0     0%    /proc
fd                         0       0       0     0%    /dev/fd
/dev/md/dsk/d33      1523574  121694 1340938     9%    /var
swap                  716016      16  716000     1%    /tmp
/dev/md/dsk/d34      6191949       9 6130021     1%    /usr1
/dev/md/dsk/d35      5159318       9 5107716     1%    /bak

求助！搞了好幾天了：（
作者: tootooluu    時(shí)間: 2006-08-15 19:27
# /usr/opt/SUNWmd/sbin/metadb -i
        flags           first blk       block count
     a m  p  luo        16              1034            /dev/dsk/c0t0d0s3
     a    p  luo        1050            1034            /dev/dsk/c0t0d0s3
     a    p  luo        2084            1034            /dev/dsk/c0t0d0s3
     a    p  luo        16              1034            /dev/dsk/c0t3d0s3
     a    p  luo        1050            1034            /dev/dsk/c0t3d0s3
     a    p  luo        2084            1034            /dev/dsk/c0t3d0s3
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/opt/SUNWmd/mddb.cf
p - replica's location was patched in kernel
m - replica is master, this is replica selected as input
W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
作者: tootooluu    時(shí)間: 2006-08-15 19:28
各位大人出來(lái)指點(diǎn)一下小弟��！
作者: susbin    時(shí)間: 2006-08-15 19:33
我不是大人， 是小人。
disksuite 4.2 版本對(duì) solaris 2.6 是不是太高了？
作者: tootooluu    時(shí)間: 2006-08-15 19:34
查了手冊(cè)，支持6的呀。。。。還是問(wèn)人家討了半天才要到的4.2
作者: susbin    時(shí)間: 2006-08-15 19:40
沒(méi)見(jiàn)過(guò) Solaris 6.
作者: susbin    時(shí)間: 2006-08-15 19:46
在這壇子里搜一下吧，有些貼和你的問(wèn)題差不多。
作者: tootooluu    時(shí)間: 2006-08-15 21:13
都看遍了啊，沒(méi)辦法才發(fā)的。用solaris 6也是沒(méi)辦法，用戶的應(yīng)用程序是在6基礎(chǔ)上設(shè)計(jì)的，8不支持：（
作者: susbin    時(shí)間: 2006-08-15 21:42
讀讀這一貼，也許會(huì)有幫助：

SDS做鏡像的問(wèn)題。在線等回復(fù)
http://www.72891.cn/viewthread.php?tid=782786
作者: tootooluu    時(shí)間: 2006-08-15 21:47
謝謝樓上兄弟，這個(gè)帖子我看過(guò)了的，沒(méi)結(jié)果啊。。。能試的我都試過(guò)了，打算明天過(guò)去去FSCK 然后NEWFS去��！但一塊是SUN剛發(fā)過(guò)來(lái)的新硬盤�。海�
作者: susbin    時(shí)間: 2006-08-15 22:05
“做鏡象，做完后同步一切正常，但一重啟動(dòng)，就會(huì)出現(xiàn)某些分區(qū)needs maintenance”

有幾個(gè)分區(qū)是要重啟后才能同步的吧。
作者: tootooluu    時(shí)間: 2006-08-15 22:58
不是的吧，我做玩，他自己就在同步，如果不重啟，同步狀態(tài)都是好的
作者: maike_xiao    時(shí)間: 2006-08-15 23:18
樓主能不能你把你做的步驟發(fā)上來(lái)讓大家看看？
作者: susbin    時(shí)間: 2006-08-16 00:13
/, /usr 都是要要重啟后才能同步。
作者: tootooluu    時(shí)間: 2006-08-16 08:36
問(wèn)題是，我重啟動(dòng)完，metareplace -e d30 c0t3d0s0，總是報(bào)錯(cuò)：（
作者: wuqing    時(shí)間: 2006-08-16 09:01
原帖由 tootooluu 于 2006-8-16 08:36 發(fā)表
問(wèn)題是，我重啟動(dòng)完，metareplace -e d30 c0t3d0s0，總是報(bào)錯(cuò)：（


問(wèn)題集中在以下三個(gè)分區(qū):
/
/usr
/var

/dev/md/dsk/d30 /dev/md/rdsk/d30        /       ufs     1       no      logging
/dev/md/dsk/d32 /dev/md/rdsk/d32        /usr    ufs     1       no      logging
/dev/md/dsk/d33 /dev/md/rdsk/d33        /var    ufs     1       no      logging

這三個(gè)分區(qū)的鏡像尤其是/分區(qū)其步驟和其他分區(qū)是不一樣的,給你一個(gè)參考樣例(SVM Administration Guide.pdf Page116-117):

Example 11–6 SPARC: Creating a Mirror From the root (/) File System
# metainit -fd 1 1 1 c0t0d0s0
d1: Concat/Stripe is setup
# metainit d2 1 1 c0t1d0s0
d2: Concat/Stripe is setup
# metainit d0 -m d1
d0: Mirror is setup
# metaroot d0
# lockfs -fa
# reboot
...
# metattach d0 d2
d0: Submirror d2 is attached
# ls -l /dev/dsk/c0t1d0s0
lrwxrwxrwx 1 root root 88 Feb 8 15:51 /dev/rdsk/c1t3d0s0 ->
../../devices/pci@1f,0/pci@1,1/ide@3/dad@0,0:a
# init 0

.
.
ok nvalias backup_root /pci@1f,0/pci@1,1/ide@3/disk@0,0:a
ok setenv boot-device disk backup_root net
ok nvstore

In this example, the -f option forces the creation of the first RAID-0 volume, d1, which contains the mounted root (/) file system on /dev/dsk/c0t0d0s0. The second concatenation, d2, is created from /dev/dsk/c0t1d0s0. This slice must be the same size as, or larger than the size of d1. The metainit command with the -m option creates the one-way mirror d0 using the concatenation that contains root (/).

Next, the metaroot command edits the /etc/vfstab and /etc/system files so that the system can be booted with the root (/) file system on a volume. It is a good idea to run the lockfs -fa command before rebooting. For more information, see the lockfs(1M) man page.

Do not attach the second submirror before the system is rebooted. You must reboot after running the metaroot command and before attaching the second submirror.

After a reboot, the submirror d2 is attached to the mirror, causing a mirror resynchronization. The system confirms that the concatenations and the mirror are set up, and that submirror d2 is attached.

The ls -l command is run on the root raw device to determine the path to the alternate root device in case the system might later need to be booted from it.
作者: wuqing    時(shí)間: 2006-08-16 09:05
/var  分區(qū)也是比較特別的,就是總是在不停地記錄日志,這個(gè)也只有在單用戶的模式下才可能同步數(shù)據(jù)
最好是把你做這三個(gè)分區(qū)鏡像的步驟貼出來(lái),大家才好分析是什么原因

和硬盤沒(méi)有關(guān)系,20G的小硬盤還是很皮實(shí)的,更何況是新盤.步驟大體上沒(méi)有問(wèn)題,畢竟還有2個(gè)鏡像是Okay狀態(tài)嘛

注意:給的例子是Solaris10 SVM Administration Guide中的,僅供參考
作者: alex_linux    時(shí)間: 2006-08-16 09:41
Needs maintenance 如果同步還出現(xiàn)得話，建議將mirror打掉重做，還要徹底打點(diǎn)，光metadetach是不行得，用metaclear －f 清楚狀態(tài)，然后做mirror。
問(wèn)題基本差不多OK。。
作者: john.you    時(shí)間: 2006-08-16 09:44
找SDS for Solaris 2.6的軟件來(lái)用。
作者: tootooluu    時(shí)間: 2006-08-16 11:12
謝謝各位，我的這三個(gè)分區(qū)操作步驟如下：
metainit -f d10 1 1 c0t0d0s0
metainit -f d20 1 1 c0t3d0s0
metainit d30 -m d10
metaroot d30
查看/etc/vfstab，并且能看到“/”文件系統(tǒng)將被掛載到/dev/md/dsk上而不是掛載到/dev/dsk.
metainit -f d12 1 1 c0t0d0s4
metainit -f d22 1 1 c0t3d0s4
metainit d32 -m d12
metainit -f d13 1 1 c0t0d0s5
metainit -f d23 1 1 c0t3d0s5
metainit d33 -m d13
。。。。
編寫/etc/vfstab表
lockfs -fa
init 6
追加第二個(gè)鏡像設(shè)備到鏡像
metattach d32 d22
metattach d33 d23
.....
installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t3d0s0
ok setenv boot-device disk disk3
ok reset-all
基本步驟就是這些了
alex_linux朋友，說(shuō)的metaclear我沒(méi)試過(guò)
我是這么修復(fù)的：
/usr/opt/SUNWmd/sbin/metadetach -f d30 d20
fsck -y /dev/md/rdsk/d20
/usr/opt/SUNWmd/sbin/metadetach -f d33 d23
fsck -y /dev/md/rdsk/d23
/usr/opt/SUNWmd/sbin/metadetach -f d32 d22
fsck -y /dev/md/rdsk/d22

/usr/opt/SUNWmd/sbin/metattach d30 d20
/usr/opt/SUNWmd/sbin/metattach d33 d23
/usr/opt/SUNWmd/sbin/metattach d32 d22

結(jié)果依然報(bào)錯(cuò)，
WARNING: md: d22: write error on /dev/dsk/c0t3d0s4
WARNING: md: d22: /dev/dsk/c0t3d0s4 needs maintenance
metaclear －f 能說(shuō)的清楚點(diǎn)嗎？SUN 800建議我裝一下solaris 8看看是不是硬件問(wèn)題！
而且我每次拆鏡像完后，fsck總能發(fā)現(xiàn)有壞的地方，需要支持：）
作者: tootooluu    時(shí)間: 2006-08-16 11:15
還有就是：
metareplace -e d30 c0t3d0s0
metareplace -e d32 c0t3d0s4
metareplace -e d33 c0t3d0s5

也報(bào)同樣的錯(cuò)誤�。海�
作者: tootooluu    時(shí)間: 2006-08-16 11:41
剛剛做了如下操作：
# /usr/opt/SUNWmd/sbin/metadetach -f d30 d20
d30: submirror d20 is detached
# /usr/opt/SUNWmd/sbin/metaclear -f d30 d20
metaclear: sun04: d30: metadevice is open

d20: Concat/Stripe is cleared

# /usr/opt/SUNWmd/sbin/metainit -f d20 1 1 c0t3d0s0
d20: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metattach d30 d20
d30: submirror d20 is attached

同步到73%的時(shí)候出錯(cuò)：（
作者: tootooluu    時(shí)間: 2006-08-16 12:52
沒(méi)人回帖了：（
作者: 孤城    時(shí)間: 2006-08-16 13:47
不會(huì)是硬盤有問(wèn)題了吧,做之前先f(wàn)sck看看
作者: zbf    時(shí)間: 2006-08-16 14:43
標(biāo)題: just for reference
Document Audience: SPECTRUM
Document ID: 5970
Title: Solstice DiskSuite[TM] - 'metastat' shows all metadevices as "needs maintenance" after a reboot
Update Date: Mon Apr 11 00:00:00 MDT 2005
Products:  Solstice DiskSuite 4.2.1 Software
Technical Areas:  LVM (Logical Volume Management)

--------------------------------------------------------------------------------


--------------------------------------------------------------------------------

Keyword(s)iskSuite, Online DiskSuite, On-Line DiskSuite, SDS, ODS, error, fail, failure, fails, mirror, mirroring

Problem Statement  Top

On a system running Solstice DiskSuite[TM], all mirrors show a state of "Needs maintenance" after rebooting the system.  This occurs on all mirrors on the system, including the root disk, if that, too, is under DiskSuite control.


The mirrors are able to be turned into an "Okay" state by using the metaclear and metainit commands. However, when the system is rebooted, the mirrors return to a state of "Needs maintenance."


An example of this condition is seen by the metastat command:

# metastat

d0: Mirror
    Submirror 0: d10
      State: Needs maintenance         
    Submirror 1: d20
      State: Needs maintenance         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 6298425 blocks

d10: Submirror of d0
    State: Needs maintenance         
    Size: 6298425 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s0                   0     No    Okay         


d20: Submirror of d0
    State: Needs maintenance         
    Size: 6298614 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c1t1d0s0                   0     No    Okay                 


Resolution  Top

This may be caused by the "metasync -r" command not getting executed when the system boots, or if the system boots up only to single-user mode.


This metasync command is normally executed in one of the startup scripts run at boot time.


For Online: DiskSuite[TM] 1.0, the metasync command is located in the /etc/rc.local script.  This entry is placed in that file by the metarc command.


For Solstice DiskSuite versions between 3.x and 4.2, inclusive, the metasync command is located in the /etc/rc2.d/S95SUNWmd.sync file.

For Solstice DiskSuite version 4.2.1 and above, the metasync command is located in the file /etc/rc2.d/S95lvm.sync.

In all cases, because this script is not run until the system transitions into run state 3 (multi-user mode), it is to be expected to have both submirrors in a "Needs maintenance" state until the command is run. I/O to these metadevices works just fine while in this state, so there is no need to worry.
作者: tootooluu    時(shí)間: 2006-08-16 14:50
樓上這篇我也看過(guò)，但情況不完全一樣啊，我的進(jìn)程起來(lái)的呀。。。而且，它上面說(shuō)是兩個(gè)盤都Needs maintenance。
作者: zbf    時(shí)間: 2006-08-16 14:50
標(biāo)題: Solaris 2.6, Solstice DiskSuite version should be 4.1
Description  Top

Quick reference to the various locations for the Solstice DiskSuite[TM] or Solaris[TM] Volume Manager software that ships with Solaris.

Document Body  Top

The location and names of the Solstice DiskSuite packages has changed from version to version, making it difficult to find the right software sometimes. Below is a list of Solaris[TM] versions and which CDROM holds the software.

Solaris[TM] 2.5.1, Solstice DiskSuite 4.0

Solaris 2.5.1 Server Pack, INTRANET EXTENSION CD-ROM

Packages:

SUNWmd (required) Base Product SUNWmdg (optional) GUI package SUNWmdn (optional) SNMP log daemon package

Solaris 2.6, Solstice DiskSuite 4.1

Solaris 2.6 Server Pack, INTRANET EXTENSIONS CD-ROM

Packages:

SUNWmd (required) Base Product SUNWmdg (optional) GUI package SUNWmdn (optional) SNMP log daemon package

Solaris 7, Solstice DiskSuite 4.2

Solaris 2.7 Server Pack, EASY ACCESS SERVER 2.0/3.0 CD-ROM (Note: this CD-ROM comes in its own cardboard slipcase.)

Packages:

SUNWmd (required) Base Product SUNWmdg (optional) GUI package SUNWmdn (optional) SNMP log daemon package

Solaris 8, Solstice DiskSuite 4.2.1

Solaris 8 Server Pack, 2nd of 2 "Solaris Software" CD's (2 of 2) under the EA (Easy Access) directory.  

/cdrom/sol_8_1000_sparc_2/Solaris_8/EA/products/DiskSuite_4.2.1/sparc/Packages

Disksuite 4.2.1 is also downloadable by customers from: http://www.sun.com/bigadmin/downloads/indexSun.html

Packages:

SUNWmdu Solstice DiskSuite Commands SUNWmdr Solstice DiskSuite Drivers SUNWmdx Solstice DiskSuite Drivers(64-bit) SUNWmdg (optional) Solstice DiskSuite Tool SUNWmdnr (optional) Solstice DiskSuite Log Daemon Configuration Files SUNWmdnu (optional) Solstice DiskSuite Log Daemon

Solaris 9 and later, Solaris[TM] Volume Manager

Solaris Volume Manager (SVM - formerly Disksuite) is bundled with the operating system.  The software can be found on the 1st of 2 "Solaris Software" CD's (1 of 2), and optional packages for the GUI are located on 2 of 2 (SUNWlvma, etc).  To run the Solaris VolumeManager GUI, you must load the SMC 2.0 packages.

Packages:

SUNWmdr Solaris Volume Manager, (Root) SUNWmdu Solaris Volume Manager, (Usr) SUNWmdx Solaris Volume Manager Drivers, (64-bit) SUNWlvma Solaris Volume Management API's [GUI] SUNWlvmg Solaris Volume Management Application [GUI] SUNWlvmr Solaris Volume Management (root) [GUI]
作者: hjp1973    時(shí)間: 2006-08-16 18:06
原帖由 tootooluu 于 2006-8-15 19:23 發(fā)表
# more /etc/vfstab
#device         device          mount           FS      fsck    mount   mount
#to mount       to fsck         point           type    pass    at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr          ufs     1       yes     -
fd      -       /dev/fd fd      -       no      -
/proc   -       /proc   proc    -       no      -
/dev/md/dsk/d31 -       -       swap    -       no      -
/dev/md/dsk/d30 /dev/md/rdsk/d30        /       ufs     1       no      logging
/dev/md/dsk/d32 /dev/md/rdsk/d32        /usr    ufs     1       no      logging
/dev/md/dsk/d33 /dev/md/rdsk/d33        /var    ufs     1       no      logging
/dev/md/dsk/d35 /dev/md/rdsk/d35        /bak    ufs     1       no      logging
/dev/md/dsk/d34 /dev/md/rdsk/d34        /usr1   ufs     1       no      logging
swap    -       /tmp    tmpfs   -       yes     -


Solaris2.6文件系統(tǒng)不支持logging選項(xiàng),應(yīng)改為"-",然后重起系統(tǒng)在看看!
作者: www326yu    時(shí)間: 2006-08-17 08:35
還有個(gè)可能就是用戶的母盤，也就原來(lái)的用戶自己的系統(tǒng)盤就是有問(wèn)題的，當(dāng)你鏡像同步時(shí)鏡像盤讀到原盤某個(gè)有問(wèn)題的block時(shí)無(wú)法讀出數(shù)據(jù)也就不能完成同步，所以你每次做完同步后都會(huì)看到系統(tǒng)提示需要Needs maintenance
作者: scsi    時(shí)間: 2006-08-17 16:57
messages文件有什么報(bào)錯(cuò)沒(méi)有？
作者: tootooluu    時(shí)間: 2006-08-17 23:43
謝謝各位支持！現(xiàn)在問(wèn)題已經(jīng)解決，又問(wèn)SUN公司調(diào)了一個(gè)新盤，一次成功！重啟了幾次，都沒(méi)問(wèn)題！
可能是之前兩個(gè)盤P/N號(hào)一樣，但盤的容量還是有細(xì)微的差別導(dǎo)致吧，說(shuō)不清楚：）謝謝各位了！
作者: Barrfee    時(shí)間: 2006-08-18 00:18
問(wèn)題有幾種可能：
1、系統(tǒng)根本沒(méi)有啟動(dòng)到多用戶下面：
who -r 顯示不一定特別準(zhǔn)確，需要自己判斷

2、軟件本身存在文件損壞，如果有興趣的話，可以自己校驗(yàn)一下

3、補(bǔ)丁的問(wèn)題，可能性不大

4、硬盤的firmware版本不對(duì)

5、還有是硬盤的firmware的型號(hào)不匹配，尤其對(duì)于OBP版本比較低的硬件。

6、啟動(dòng)腳本存在問(wèn)題，可能性也不大。

最終建議：比較更換前后主機(jī)運(yùn)行環(huán)境的差別。

該結(jié)貼了。
作者: 四平    時(shí)間: 2006-08-18 09:45
硬盤容量問(wèn)題,FCO

Asset ID: 1-6-A0202-1-1
Update Date: Thu Mar 06 00:00:00 MST 2003
Keywords:  

--------------------------------------------------------------------------------

----------------------------------------------------------------------------
             - Sun Proprietary/Confidential: Internal Use Only -
----------------------------------------------------------------------------

                             FIELD CHANGE ORDER
            (For Authorized Distribution by Enterprise Services)
            

FCO #: A0202-1
Status: active
Synopsis: Mirrored 20GB disk drives on Ultra 10 and Sun Blade 100 systems may be exposed to a drive compatibility issue when replacing a failed drive.
<date>Mar/06/2003</date>
SunAlert: No
Top FIN/FCO Report: No
Products Reference: Workstation Harddisk
Product Category: DeskTop / System Component
Product Affected:
Systems Affected:

Mkt_ID    Platform      Model   Description           Serial Number
------    --------      -----   -----------           -------------
-         A22           -       Ultra 10              -
-         A36           -       Sun Blade 100         -

X-Options Affected:

Mkt_ID    Platform      Model   Description           Serial Number
------    --------      -----   -----------           -------------
-          -                -        -                      -




Systems Affected:

Mkt_ID    Platform      Model   Description           Serial Number
------    --------      -----   -----------           -------------
-         A22           -       Ultra 10              -
-         A36           -       Sun Blade 100         -

X-Options Affected:

Mkt_ID    Platform      Model   Description           Serial Number
------    --------      -----   -----------           -------------
-          -                -        -                      -

AFFECTED PARTS:

Part Number          Description                      Model
-----------          -----------                      -----                                   
370-4327-01          ATA Disk Drive 20.0GB              ST320414A
                     ATA Disk Drive 20.0GB              ST320011A
                     ATA Disk Drive 20.4GB              ST320420A

REFERENCES
  LEAP: 2051                          
  BugID: 4673592                       
  ESC: 536839                       
  Radiance: 10169433                     
  ECO: WO_24317                     

PROBLEM DESCRIPTION:

Change History
--------------
A0202-1

Date Modified: Mar/06/2003
Updates: CORRECTIVE ACTION
. CORRECTIVE ACTION: Added following note:

NOTE: Although the Seagate Model Number (ST320011A) reflects a 20.1GB
       capacity, any drive marked with Sun part number 370-5560 has been  
       configured and tested as a 20.4GB drive and should be used as such.

--------------

Seagate 20.0GB and 20.4GB disk drives, used on Ultra 10 and Sun Blade 100
systems, are both identified with the same SUN part number (370-4327).
A problem can arise when a replacement of one of the mirrored disk drives
is required.

If a mirrored 20GB disk drive fails on one of these platforms it is
important to ensure that the same capacity drive is used so that
the replacement drive is compatable with it's mirrored counter-part.
In some cases it may be necessary to replace both 20GB disk drives
to ensure they both are of the same capacity.

The root cause of this problem is that there are two drives with two
similar but different capacities reporting to the same part number
(F370-4327). The failing condition exist when disk mirroring is used
and the drive capacities are not similar.

The corrective action was made available via ECO WO_24317 on
August 7, 2002 releasing part number 370-5560-01, which is a 20.4GB
(only) disk drive.

When replacing a failed 20GB mirrored disk drive on a Ultra 10 or
Sun Blade 100 system please follow the instructions listed in the
Corrective Action section below.
Parts Affected:
Part Number          Description                      Model
-----------          -----------                      -----                                   
370-4327-01          ATA Disk Drive 20.0GB              ST320414A
                     ATA Disk Drive 20.0GB              ST320011A
                     ATA Disk Drive 20.4GB              ST320420A

REFERENCES
  LEAP: 2051                          
  BugID: 4673592                       
  ESC: 536839                       
  Radiance: 10169433                     
  ECO: WO_24317
Problem Description:
Seagate 20.0GB and 20.4GB disk drives, used on Ultra 10 and Sun Blade 100
systems, are both identified with the same SUN part number (370-4327).
A problem can arise when a replacement of one of the mirrored disk drives
is required.

If a mirrored 20GB disk drive fails on one of these platforms it is
important to ensure that the same capacity drive is used so that
the replacement drive is compatable with it's mirrored counter-part.
In some cases it may be necessary to replace both 20GB disk drives
to ensure they both are of the same capacity.

The root cause of this problem is that there are two drives with two
similar but different capacities reporting to the same part number
(F370-4327). The failing condition exist when disk mirroring is used
and the drive capacities are not similar.

The corrective action was made available via ECO WO_24317 on
August 7, 2002 releasing part number 370-5560-01, which is a 20.4GB
(only) disk drive.

When replacing a failed 20GB mirrored disk drive on a Ultra 10 or
Sun Blade 100 system please follow the instructions listed in the
Corrective Action section below.
Parts Affected:
September 30, 2004


IMPLEMENTATION :

---
|   |   MANDATORY (Fully Pro-Active)
---

---
|   |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---

---
| X |   UPON FAILURE
---

REPLACEMENT TIME ESTIMATE: .5 hours

SPECIAL CONSIDERATION:

CORRECTIVE ACTION:

For those customers who have experienced a failure on a mirrored
Seagate 20.0GB or 20.4GB disk drive, follow the below guidelines;

1. If the system has mirrored 20.4GB disk drives, replace the faulty
   drive with part number 370-5560.

2. If the system has mirrored 20.0GB disk drives, replace both drives
   with part number 370-5560, thus ensuring matching capacities.

If the service is being done for a customer NOT covered under a
product warranty or service contract, the second drive should be
provided at no cost to the customer.

NOTE: Although the Seagate Model Number (ST320011A) reflects a 20.1GB
       capacity, any drive marked with Sun part number 370-5560 has been  
       configured and tested as a 20.4GB drive and should be used as such.


COMMENTS:

For those customers who do NOT mirror their disk drives and
experience a 20GB disk failure, please continue to use Sun
part number 370-4327 as the replacement.

http://plc-ims-2.central:9090/servlet/fcopm.fco.FCO_Gliap?A0202-1

BILLING TYPE:

Warranty: Sun will provide parts at no charge under Warranty
           Service. On-Site Labor Rates are based on how the
           system was initially installed.

Contract: Sun will provide parts at no charge. On-Site Labor Rates
           are based on the type of service contract.

Non Contract: Sun will provide parts at no charge. Installation by
               Sun is available based on the On-Site Labor Rates
               defined in the Price List.

--------------------------------------------------------------------------
Implementation Footnote:
________________________

i)   In case of Mandatory FCOs, Sun Services will attempt to contact
      all known customers to recommend the part upgrade.

ii)  For controlled proactive swap FCOs, Sun Services mission critical
     support teams will initiate proactive swap efforts for their respective
     accounts, as required.

iii) For Replace upon Failure FCOs, Sun Services partners will implement
     the necessary corrective actions as and when they are required.

--------------------------------------------------------------------------

All released FINs and FCOs can be accessed using your favorite network
browser as follows:

SunWeb Access:
______________

* Access the top level URL of http://sdpsweb.EBay/FIN_FCO/

* From there, select the appropriate link to query or browse the FIN and
  FCO Homepage collections.

SunSolve Online Access:
_______________________

* Access the SunSolve Online URL at http://sunsolve.Central/

* From there, select the appropriate link to browse the FIN or FCO index.

Internet Access:
_______________

* Access the top level URL of https://infoserver.Sun.COM

--------------------------------------------------------------------------
General:
________

Send questions or comments to finfco-manager@Sun.COM

---------------------------------------------------------------------------
Implementation:
---
|   |   MANDATORY (Fully Pro-Active)
---

---
|   |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---

---
| X |   UPON FAILURE
---
Replacement Time Estimate:
.5 hours
Symptom:

Corrective Action:
For those customers who have experienced a failure on a mirrored
Seagate 20.0GB or 20.4GB disk drive, follow the below guidelines;

1. If the system has mirrored 20.4GB disk drives, replace the faulty
   drive with part number 370-5560.

2. If the system has mirrored 20.0GB disk drives, replace both drives
   with part number 370-5560, thus ensuring matching capacities.

If the service is being done for a customer NOT covered under a
product warranty or service contract, the second drive should be
provided at no cost to the customer.
Comments:
For those customers who do NOT mirror their disk drives and
experience a 20GB disk failure, please continue to use Sun
part number 370-4327 as the replacement.

http://plc-ims-2.central:9090/servlet/fcopm.fco.FCO_Gliap?A0202-1

Billing Type:
Warranty: Sun will provide parts at no charge under Warranty
           Service. On-Site Labor Rates are based on how the
           system was initially installed.

Contract: Sun will provide parts at no charge. On-Site Labor Rates
           are based on the type of service contract.

Non Contract: Sun will provide parts at no charge. Installation by
               Sun is available based on the On-Site Labor Rates
               defined in the Price List.

--------------------------------------------------------------------------
Implementation Footnote:
________________________

i)   In case of Mandatory FCOs, Sun Services will attempt to contact
      all known customers to recommend the part upgrade.

ii)  For controlled proactive swap FCOs, Sun Services mission critical
     support teams will initiate proactive swap efforts for their respective
     accounts, as required.

iii) For Replace upon Failure FCOs, Sun Services partners will implement
     the necessary corrective actions as and when they are required.

--------------------------------------------------------------------------

All released FINs and FCOs can be accessed using your favorite network
browser as follows:

SunWeb Access:
______________

* Access the top level URL of http://sdpsweb.EBay/FIN_FCO/

* From there, select the appropriate link to query or browse the FIN and
  FCO Homepage collections.

SunSolve Online Access:
_______________________

* Access the SunSolve Online URL at http://sunsolve.Central/

* From there, select the appropriate link to browse the FIN or FCO index.

Internet Access:
_______________

* Access the top level URL of https://infoserver.Sun.COM

--------------------------------------------------------------------------
General:
________

Send questions or comments to finfco-manager@Sun.COM

---------------------------------------------------------------------------

From - Thu Mar  6 16:25:39 2003
Return-path: <hd4723@bast.Central.Sun.COM>
Received: from bast.Central.Sun.COM ([129.147.58.198])
by edgemail1.Central.Sun.COM
(iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003))
with ESMTP id <0HBC009KMJ8C44@edgemail1.Central.Sun.COM> for
hd4723@ims-ms-daemon; Thu, 06 Mar 2003 14:19:24 -0700 (MST)
Received: from peacemaker (peacemaker [129.147.20.82])
        by bast.Central.Sun.COM (8.11.6+Sun/8.11.6/ENSMAIL,v2.2)
with SMTP id h26LJI002145; Thu, 06 Mar 2003 14:19:18 -0700 (MST)
Date: Thu, 06 Mar 2003 14:19:18 -0700 (MST)
From: Joe Davis <hd4723@bast.Central.Sun.COM>
Subject: FCO:Release:Approved FCO A0202-1 (Mirrored 20GB disk drives on Ultra
10 and Sun Blade 100 systems may be exposed to a drive compatibility issue
when replacing a failed drive)
To: fieldnotice-updates@tis-server.Central.Sun.COM
Cc: Joe.Davis@Sun.COM
Reply-to: Joe Davis <hd4723@bast.Central.Sun.COM>
Message-id: <200303062119.h26LJI002145@bast.Central.Sun.COM>
MIME-version: 1.0
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.6_06 SunOS 5.8 sun4u sparc
Content-type: TEXT/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-MD5: kur6zRgezUo3It1v+DkknA==
Original-recipient: rfc822;hd4723@edgemail1.Central.Sun.COM
Status: RO
X-Status: $$$$
X-UID: 0000000002

----------------------------------------------------------------------------
             - Sun Proprietary/Confidential: Internal Use Only -
----------------------------------------------------------------------------

                             FIELD CHANGE ORDER
            (For Authorized Distribution by Enterprise Services)
Status: active

   
Copyright 1994-2006 Sun Microsystems, Inc.    All rights reserved.
Legal Terms Privacy Policy Feedback
作者: 四平    時(shí)間: 2006-08-18 09:47
Ultra 5/10 workstations may encounter uncorrectable data errors on IDE disks

Asset ID: 1-7-I0779-1-1
Update Date: 2004-06-08
Keywords:  

--------------------------------------------------------------------------------

------------------------------------------------------------
        - Sun Proprietary/Confidential: Internal Use Only -
------------------------------------------------------------------------
                        FIELD INFORMATION NOTICE
           (For Authorized Distribution by Sun Services)
FIN #: I0779-1
Status: active
Synopsis: Ultra 5/10 workstations may encounter uncorrectable data errors on IDE disks during boot after using shutdown -y -i5 -g0 command.
Create date: May/26/04
SunAlert: Yes
Top FIN/FCO Report: Yes
Products Reference: Ultra 5/10 with IDE drives
Product Category: Storage / Disks
Product Affected:
Systems Affected
----------------
Mkt_ID   Platform   Model   Description   Serial Number
------   --------   -----   -----------   -------------
  -        A21              ALL    Ultra 5             -
  -        A22       ALL    Ultra 10            -


X-Options Affected
------------------
Mkt_ID   Platform   Model   Description                           Serial Number
------   --------   -----   -----------                           -------------
X6174A      -         -     X-Opt Internal 20GB Drive for U5/U10 SB1        -
X5236A      -         -     X-Opt Internal 9.1GB Drive for U5/U10        -
X5227A      -         -     X-Opt Internal 4.3GB Drive for U10                -
Parts Affected:
Part Number      Description                               Model
-----------      -----------                               -----
370-4327-03      20GB Disk 3 1/2" 7200 RPM Ultra ATA/100     -
370-3693-01      9.1GB Disk 3 1/2" 7200 RPM Ultra ATA/66     -
370-3176-01      4.3GB Disk 3 1/2" 4500 RPM Ultra ATA-3      -
370-3692-01      4.3GB Disk 3 1/2" 5400 RPM Ultra ATA-3      -
370-3863-02      8.4GB Disk 3 1/2" 5400 RPM Ultra ATA-4      -
References:
BugId:   4380416  - init 5 corrupts filesystems on ultra-10 440MHz on
                   2.5.1 systems.
         4435428  - darwin:EIDE disk with write-cache enabled should be
                   flushed before power-off.
         4337637 - grover: IDE doesn't complete all writes.
         
PatchId: 106197-06  - SunOS 5.5.1: Jumbo patch for ide and atapi fixes.
         103640-38  - SunOS 5.5.1: kernel, nisopaccess, & libthread patch.
         106407-07  - SunOS 5.6: Jumbo patch for ide and atapi fixes.
         105181-31  - SunOS 5.6: Kernel update patch.
         106541-21  - SunOS 5.7: Kernel update patch
         108974-05 - SunOS 5.8: dada, uata, dad, sd and scsi drivers patch.
         108528-03  - SunOS 5.8: kernel update patch.

ESC:     529449 - init 5 corrupts filesystems on ultra5.
         530062 - darwin:EIDE disk with write-cache enabled should be
                  flushed before power-off.
Problem Description:
On Sun Ultra 5/10 workstations, use of the following shutdown(1M)
command 'shutdown -y -i5 -g0' might result in the IDE disk drive not
getting "sync'ed" properly.  If the disk is not "sync'ed" (see sync(1M))
properly, "Uncorrectable data Errors" are reported which may lead to
unnecessary disk replacement.

Failing Configuration: Ultra 5/10 systems with internal IDE drives.

Here are two different cases of error messages which may be seen in the
/var/sadm/messages files upon boot up after using the shutdown -y -i5
-g0 command:

    Case 1
    ------
        Jan 9 15:04:16 Ultra-10  unix: WARNING:
        /pci@1f,0/pci@1,1/ide@3/dad@1,0 (dad1):
        Jan 9 15:04:16 Ultra-10        Uncorrectable data Error: Block 289ed0
        Jan 9 15:04:18 Ultra-10  unix: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@1,0
(dad1):
        Jan 9 15:04:18 Ultra-10        disk not responding to selection
        Jan 9 15:04:18 Ultra-10  unix: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@0,0
(dad0):
        Jan 9 15:04:18 Ultra-10   ATA transport failed: reason `reset`: retrying
command
        Jan 9 15:04:22 Ultra-10  unix: dad1:    disk okay
        Jan 9 15:42:06 Ultra-10  unix: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@2,0
(dad1):
        Jan 9 15:42:06 Ultra-10  Uncorrectable data Error: Block 8ca48
        Jan 9 15:42:07 Ultra-10  unix: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@2,0
(dad1):
        Jan 9 15:42:07 Ultra-10  disk not responding to selection
        Jan 9 15:42:07 Ultra-10  unix: dad1:      disk okay
        Jan 9 15:45:26 Ultra-10  unix: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@2,0
(dad1):
        Jan 9 15:45:26 Ultra-10  Uncorrectable data Error: Block 5201c4
        Jan 9 15:45:27 Ultra-10  disk not responding to selection
   
   Case 2
   ------     
        Mar 29 11:04:16 Ultra-10 unix: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@1,0
(dad1):
        Mar 29 11:04:16 Ultra-10        Uncorrectable data Error: Block 289ed0
        Mar 29 11:04:18 Ultra-10 unix: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@1,0
(dad1):
        Mar 29 11:04:18 Ultra-10        disk not responding to selection
        Mar 29 11:04:18 Ultra-10 unix: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@0,0
(dad0):
        Mar 29 11:04:18 Ultra-10        ATA transport failed: reason 'reset':
retrying command
        Mar 29 11:04:22 Ultra-10 unix: dad1:    disk okay
                                          
   NOTE: In some cases, the fsck(1M) command may need to be run manually
         to repair file systems when the system is booted.  But in most
         cases fsck activation during reboot.

Unlike SCSI disks, IDE drives have their internal write cache enabled.
Whenever the system is powered down, the data in the disk cache is not
flushed causing possible data corruption.

The fix requires writing a new entry point in the IDE driver that will
send a disk flush command before powering down the disk.
Implementation:
---
       |   |          MANDATORY (Fully Pro-Active)
          ---   
           
  
        ---
       | X |         CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
        ---
           
                                    
        ---
       |   |         REACTIVE (As Required)
        ---
Corrective Action:
The following recommendation is provided as a guideline for authorized
Enterprise Services Field Representatives who may encounter the above
mentioned problem.

The recommended workaround is to use the "-i0" option instead of the
"-i5" option for shutdown:

    # shutdown -y -i0 -g0                        

Please install the following patches as a final solution:

     ---------------------------------------------------------
    | Solaris |  Solaris patchId       | IDE PatchId          |
    |=========================================================|
    | 2.5.1   |  103640-38  (or later)  | 106197-06  (or later) |  
    |---------+------------------------+----------------------|
    | 2.6     |  105181-31  (or later)  | 106407-07  (or later) |
    |---------+------------------------+----------------------|
    | 7       |  106541-21  (or later)  | See NOTE             |
    |---------+------------------------+----------------------|
    | 8       |  108528-03  (or later)  | 108974-05 (or later) |
     ---------------------------------------------------------
  
    NOTE: For Solaris 7, there is no IDE patch available, so the fix
          is not complete for that release.
Comments:
There have been cases in the field that the disk drives were
inadvertently replaced.

The boot disk is less prone to data loss as this is not used normally
to store user data.  But any other internal IDE drives could cause
substantial damage to the customer as data perceived by applications to
have been written to the disks are lost.

--------------------------------------------------------------------------
Implementation Footnote:
________________________

i)   In case of MANDATORY FINs, Enterprise Services will attempt to contact   
     all affected customers to recommend implementation of the FIN.
        

ii)  For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical sup-   
     port teams will recommend implementation of the FIN (to their respective
     accounts), at the convenience of the customer.


iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the need  
     arises.

--------------------------------------------------------------------------

All released FINs and FCOs can be accessed using your favorite network
browser as follows:

SunWeb Access:
______________

* Access the top level URL of http://cte.ebay/FIN_FCO/

* From there, select the appropriate link to query or browse the FIN and
  FCO Homepage collections.

SunSolve Online Access:
_______________________

* Access the SunSolve Online URL at http://sunsolve.Corp/

* From there, select the appropriate link to browse the FIN or FCO index.

Internet Access:
_______________

* Access the top level URL of https://infoserver.Sun.COM

--------------------------------------------------------------------------
   
General:
________

Send questions or comments to finfco-manager@cte.Corp

--------------------------------------------------------------------------
Status: active

   
Copyright 1994-2006 Sun Microsystems, Inc.    All rights reserved.
Legal Terms Privacy Policy Feedback
作者: tootooluu    時(shí)間: 2006-08-18 10:51
感謝大家支持，把操作步驟整理了一下，貼上來(lái)：）

安裝Disksuite 4.2

1  SUNWmd      Solstice DiskSuite
                 (sparc) 4.2,REV=1998.02.09.12.47.28
  2  SUNWmdg     Solstice DiskSuite Tool
                 (sparc) 4.2,REV=1998.14.09.08.19.32
  3  SUNWmdn     Solstice DiskSuite Log Daemon
                 (sparc) 4.2,REV=1998.02.09.12.47.28

選擇1，2，3，在安裝過(guò)程中全部選“y”
全部安裝成功后 init 6 重啟機(jī)器。

# prtvtoc /dev/rdsk/c0t0d0s2 | fmthard -s - /dev/rdsk/c0t3d0s2
fmthard:  New volume table of contents now in place.
# /usr/opt/SUNWmd/sbin/metadb -a -f -c 3 /dev/dsk/c0t0d0s3 /dev/dsk/c0t3d0s3

# /usr/opt/SUNWmd/sbin/metainit -f d10 1 1 c0t0d0s0
d10: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit -f d20 1 1 c0t3d0s0
d20: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit d30 -m d10
d30: Mirror is setup
# /usr/opt/SUNWmd/sbin/metaroot d30      

# /usr/opt/SUNWmd/sbin/metainit -f d11 1 1 c0t0d0s1
d11: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit -f d21 1 1 c0t3d0s1
d21: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit d31 -m d11
d31: Mirror is setup
# /usr/opt/SUNWmd/sbin/metainit -f d12 1 1 c0t0d0s4
d12: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit -f d22 1 1 c0t3d0s4
d22: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit d32 -m d12
d32: Mirror is setup
# /usr/opt/SUNWmd/sbin/metainit -f d13 1 1 c0t0d0s5
d13: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit -f d23 1 1 c0t3d0s5
d23: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit d33 -m d13
d33: Mirror is setup
# /usr/opt/SUNWmd/sbin/metainit -f d14 1 1 c0t0d0s6
d14: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit -f d24 1 1 c0t3d0s6
d24: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit d34 -m d14
d34: Mirror is setup
# /usr/opt/SUNWmd/sbin/metainit -f d15 1 1 c0t0d0s7
d15: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit -f d25 1 1 c0t3d0s7
d25: Concat/Stripe is setup
# /usr/opt/SUNWmd/sbin/metainit d35 -m d15
d35: Mirror is setup

# vi  /etc/vfstab
#device         device          mount           FS      fsck    mount   mount
#to mount       to fsck         point           type    pass    at boot options
#
#/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr          ufs     1       yes     -
fd      -       /dev/fd fd      -       no      -
/proc   -       /proc   proc    -       no      -
/dev/md/dsk/d31 -       -       swap    -       no      -
/dev/md/dsk/d30 /dev/md/rdsk/d30        /       ufs     1       no      -
/dev/md/dsk/d34 /dev/md/rdsk/d34        /usr    ufs     1       no      -
/dev/md/dsk/d32 /dev/md/rdsk/d32        /var    ufs     1       no      -
/dev/md/dsk/d35 /dev/md/rdsk/d35        /export/home    ufs     2       yes     
-
/dev/md/dsk/d33 /dev/md/rdsk/d33        /opt    ufs     2       yes     -
swap    -       /tmp    tmpfs   -       yes     -

# /usr/opt/SUNWmd/sbin/metainit hsp001
hsp001: Hotspare pool is setup
# lockfs -fa  
#init 6

# /usr/opt/SUNWmd/sbin/metattach d30 d20
d30: submirror d20 is attached
# /usr/opt/SUNWmd/sbin/metattach d31 d21   
d31: submirror d21 is attached
# /usr/opt/SUNWmd/sbin/metattach d32 d22
d32: submirror d22 is attached
# /usr/opt/SUNWmd/sbin/metattach d33 d23
d33: submirror d23 is attached
# /usr/opt/SUNWmd/sbin/metattach d34 d24
d34: submirror d24 is attached
# /usr/opt/SUNWmd/sbin/metattach d35 d25
d35: submirror d25 is attached

#installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t3d0s0

ok setenv boot-device disk disk3
ok reset-all
作者: tootooluu    時(shí)間: 2006-08-18 10:54
目前狀態(tài)：
# /usr/opt/SUNWmd/sbin/metastat
d30: Mirror
    Submirror 0: d10
      State: Okay         
    Submirror 1: d20
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 6086304 blocks

d10: Submirror of d30
    State: Okay         
    Size: 6086304 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s0                   0     No    Okay         


d20: Submirror of d30
    State: Okay         
    Size: 6086304 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s0                   0     No    Okay         


d31: Mirror
    Submirror 0: d11
      State: Okay         
    Submirror 1: d21
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 1049328 blocks

d11: Submirror of d31
    State: Okay         
    Size: 1049328 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s1                   0     No    Okay         


d21: Submirror of d31
    State: Okay         
    Size: 1049328 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s1                   0     No    Okay         


d32: Mirror
    Submirror 0: d12
      State: Okay         
    Submirror 1: d22
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 6291936 blocks

d12: Submirror of d32
    State: Okay         
    Size: 6291936 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s4                   0     No    Okay         


d22: Submirror of d32
    State: Okay         
    Size: 6291936 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s4                   0     No    Okay         


d33: Mirror
    Submirror 0: d13
      State: Okay         
    Submirror 1: d23
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 3145968 blocks

d13: Submirror of d33
    State: Okay         
    Size: 3145968 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s5                   0     No    Okay         


d23: Submirror of d33
    State: Okay         
    Size: 3145968 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s5                   0     No    Okay         


d34: Mirror
    Submirror 0: d14
      State: Okay         
    Submirror 1: d24
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 12583872 blocks

d14: Submirror of d34
    State: Okay         
    Size: 12583872 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s6                   0     No    Okay         


d24: Submirror of d34
    State: Okay         
    Size: 12583872 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s6                   0     No    Okay         


d35: Mirror
    Submirror 0: d15
      State: Okay         
    Submirror 1: d25
      State: Okay         
    Pass: 1
    Read option: roundrobin (default)
    Write option: parallel (default)
    Size: 10486224 blocks

d15: Submirror of d35
    State: Okay         
    Size: 10486224 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t0d0s7                   0     No    Okay         


d25: Submirror of d35
    State: Okay         
    Size: 10486224 blocks
    Stripe 0:
        Device              Start Block  Dbase State        Hot Spare
        c0t3d0s7                   0     No    Okay         


hsp001: is empty
作者: tootooluu    時(shí)間: 2006-08-18 10:55
---------OVER--------

謝謝大家支持



歡迎光臨 Chinaunix (http://www.72891.cn/) Powered by Discuz! X3.2