>[оверквотинг удален]
>Так! слушай, есть вопрос!
>Я как то совсем забыл о том что при зеркалировании дисков с
>помощью metadevice
>в /etc/system должны быть строки:
>
>* Begin MDD root info (do not edit)
>rootdev:/pseudo/md@0:0,0,blk
>* End MDD root info (do not edit)
>
>пришли ка, полный листинг /etc/system и /etc/vfstab Это текущий листинг /etc/system с ГЮЧНОГО сервера.
*ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
*
* SYSTEM SPECIFICATION FILE
*
* moddir:
*
* Set the search path for modules. This has a format similar to the
* csh path variable. If the module isn't found in the first directory
* it tries the second and so on. The default is /kernel /usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules
* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)
* exclude:
*
* Modules appearing in the moddir path which are NOT to be loaded,
* even if referenced. Note that `exclude' accepts either a module name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys
* forceload:
*
* Cause these modules to be loaded at boot time, (just before mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it will
* be installed.
*
* Example:
* forceload: drv/foo
* set:
*
* Set an integer variable in the kernel or a module to a new value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named 'test_module'
*
* set test_module:debug = 0x13
*
set shmsys:shminfo_shmmax = 0x2000000
set shmsys:shminfo_shmmin = 1
set shmsys:shminfo_shmmni = 256
set shmsys:shminfo_shmseg = 256
set semsys:seminfo_semmap = 256
set semsys:seminfo_semmni = 512
set semsys:seminfo_semmns = 512
set semsys:seminfo_semmsl = 32
Это оригинальный листинг /etc/system.orig с Глючного сервера.
*ident "@(#)system 1.18 97/06/27 SMI" /* SVR4 1.5 */
*
* SYSTEM SPECIFICATION FILE
*
* moddir:
*
* Set the search path for modules. This has a format similar to the
* csh path variable. If the module isn't found in the first directory
* it tries the second and so on. The default is /kernel /usr/kernel
*
* Example:
* moddir: /kernel /usr/kernel /other/modules
* root device and root filesystem configuration:
*
* The following may be used to override the defaults provided by
* the boot program:
*
* rootfs: Set the filesystem type of the root.
*
* rootdev: Set the root device. This should be a fully
* expanded physical pathname. The default is the
* physical pathname of the device where the boot
* program resides. The physical pathname is
* highly platform and configuration dependent.
*
* Example:
* rootfs:ufs
* rootdev:/sbus@1,f8000000/esp@0,800000/sd@3,0:a
*
* (Swap device configuration should be specified in /etc/vfstab.)
* exclude:
*
* Modules appearing in the moddir path which are NOT to be loaded,
* even if referenced. Note that `exclude' accepts either a module name,
* or a filename which includes the directory.
*
* Examples:
* exclude: win
* exclude: sys/shmsys
* forceload:
*
* Cause these modules to be loaded at boot time, (just before mounting
* the root filesystem) rather than at first reference. Note that
* forceload expects a filename which includes the directory. Also
* note that loading a module does not necessarily imply that it will
* be installed.
*
* Example:
* forceload: drv/foo
* set:
*
* Set an integer variable in the kernel or a module to a new value.
* This facility should be used with caution. See system(4).
*
* Examples:
*
* To set variables in 'unix':
*
* set nautopush=32
* set maxusers=40
*
* To set a variable named 'debug' in the module named 'test_module'
*
* set test_module:debug = 0x13
* Begin MDD root info (do not edit)
forceload: misc/md_trans
forceload: misc/md_raid
forceload: misc/md_hotspares
forceload: misc/md_sp
forceload: misc/md_stripe
forceload: misc/md_mirror
forceload: drv/pcisch
forceload: drv/glm
forceload: drv/sd
rootdev:/pseudo/md@0:0,10,blk
* End MDD root info (do not edit)
* Begin MDD database info (do not edit)
set md:mddb_bootlist1="sd:5:16 sd:5:1050 sd:5:2084 sd:13:16 sd:13:1050"
set md:mddb_bootlist2="sd:13:2084"
* End MDD database info (do not edit)
файла /etc/vfstab пишет что не существует.
Открылись новые подробности, оказывается правилный вывод mount должен быть таким:
/ on /pci@1c,600000/scsi@2/disk@0,0:a read/write/setuid/dev=800000 on Wed Dec 31 21:00:00 1969
/usr on /dev/dsk/c0t0d0s6 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=800006 on Mon Jun 29 13:23:55 2009
/proc on /proc read/write/setuid/dev=4b40000 on Mon Jun 29 13:23:54 2009
/dev/fd on fd read/write/setuid/dev=4c00000 on Mon Jun 29 13:23:55 2009
/etc/mnttab on mnttab read/write/setuid/dev=4cc0000 on Mon Jun 29 13:23:56 2009
/var on /dev/dsk/c0t0d0s1 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=800001 on Mon Jun 29 13:23:56 2009
/var/run on swap read/write/setuid/dev=1 on Mon Jun 29 13:23:56 2009
/var/point on /dev/md/dsk/d10 read/write/setuid/intr/largefiles/onerror=panic/dev=154000a on Mon Jun 29 13:39:42 2009
последовательностью команд:
ssh server-ip -C "mkdir /var/point"
ssh server-ip -C "mount /dev/md/dsk/d10 /var/point"
удалось примонтировать зеркало и получить доступ к файлу /var/point/etc/system т.е. я могу его через sftp выгрузить отредактировать и загрузить обратно, а с консолью мне помогут удаленно.
Остался вопрос почему после загрузки у меня вместо
/ on /dev/dsk/c1t0d0s0 read/write/setuid/intr/largefiles/logging/onerror=panic/dev=800000 on Tue Jun 9 13:47:17 2009
получается
/ on /pci@1c,600000/scsi@2/disk@0,0:a read/write/setuid/dev=800000 on Wed Dec 31 21:00:00 1969
видимо поэтому и на запись не дается.