Petit tutorial sur Veritas FS, gestion du file system de VERITAS.
Last Updated: Thu May 10 14:23:37 CDT 2001<\/p>\n
\t\t\tA1000 Dual Port Setup and Configuration
\t\t\twith Veritas Volume Manager and Filesystem
\t\t———————————————————–<\/p>\n
Overview:<\/p>\n
The following tutorial documents the steps used to configure a single
A1000 array to be shared between two hosts. It then documents the
steps used to create simple Veritas volumes and filesystems on each
of the logical array drives, as well as the steps necessary to deport
and import the volumes between the two hosts.<\/p>\n
This tutorial is based on an actual install of the configuration used
in the examples.<\/p>\n
Hardware configs:<\/p>\n
\t\t Sun StorEdge A1000 – SCSI Target ID 1
\t\t\t w\/ 7 18GB disk drives<\/p>\n
d0 d1 d2 HS d0 d1 d2
\t\t ———————————————–
\t\t| 2,0 2,1 2,2 2,3 | 1,0 1,1 1,2 |
\t\t ———————————————–
\t\t\t|\t\t\t|
\t\t\t| controller 1\t\t| controller 1
\t\t\t|\t\t\t|
\t\t ————–\t\t————-
\t\t | E220R |\t\t| E220R |
\t\t ————–\t\t————-
\t\t node1\t\t node2
| |
c0t0d0 c0t0d0 Internal root drive
c0t1d0 c0t1d0 Internal root mirror<\/p>\n
– Both E220R's have a dual-channel Differential Ultra-SCSI card, with the
first port (controller 1) connected to the A1000 array. <\/p>\n
– The A1000 array was configured as 3 logical drives, plus one hot spare.
The logical drives consist of 2 18GB disk drives mirrored (RAID 1).<\/p>\n
– The A1000 logical drives are seen as:<\/p>\n
\tc1t1d0, c1t1d1, c1t1d2<\/p>\n
– Final configs are setup as:<\/p>\n
Internal Drives:<\/p>\n
\tBoot drive c0t0d0 encapsulated as rootdisk and mirrored to disk01 (c0t1d0)<\/p>\n
A1000 Drives are all simple (concatenated) veritas volumes with vxfs filesystems:<\/p>\n
\t\/mh = disk02 = c1t1d0 = RAID 1 hardware mirror using array drives 1,0 and 2,0<\/p>\n
\t\/ms = disk03 = c1t1d1 = RAID 1 hardware mirror using array drives 1,1 and 2,1<\/p>\n
\t\/amt = disk04 = c1t1d2 = RAID 1 hardware mirror using array drives 1,2 and 2,2<\/p>\n
\tHardware RAID Hot Spare drive is 2,3<\/p>\n
– Steps used to configure RAID:<\/p>\n
\t1. Installed A1000 in Rack<\/p>\n
\t2. Cabled A1000 to port 1 of dual-port differential SCSI card on node1<\/p>\n
\t3. Set SCSI ID switch on back of A1000 to target 1<\/p>\n
\t4. powered on A1000<\/p>\n
\t5. powered on E220R<\/p>\n
\t6. At boot prompt, verified the array was seen:<\/p>\n
\t\tsetenv auto-boot? false
\t\treset-all
\t\tprobe-scsi-all<\/p>\n
\t7. Booted E220R<\/p>\n
\t8. Verified OS and app patch requirements per Sun Infodoc 20029
\t "A1000\/A3x00\/A3500FC Software\/Firmware Configuration Matrix"
\t (only patch required was the RAIDManager version 6.22 jumbo
\t patch 108834-09)<\/p>\n
\t9. Installed the RAIDManager ver. 6.22 software from the included CD:<\/p>\n
\t\tmount -r -F hsfs \/dev\/sr0 \/cdrom
\t\tcd \/cdrom\/… (don't remember the exact path)
\t\tpkgadd -d . SUNWosar SUNWosafw SUNWosamn SUNWosau<\/p>\n
\t This installs the following packages:<\/p>\n
\t\tsystem SUNWosafw Open Storage Array Firmware
\t\tsystem SUNWosamn Open Storage Array Man Pages
\t\tsystem SUNWosar Open Storage Array (Root)
\t\tsystem SUNWosau Open Storage Array (Usr)<\/p>\n
\t10. Verified that \/etc\/osa\/mnf does not have a period (.) in the name.
\t There is a known problem with this. If it does, change to an
\t underscore (_). This was per the A1000 install notes at:
\t http:\/\/www.eng.auburn.edu\/pub\/mail-lists\/ssastuff\/Solaris8-A1000.html<\/p>\n
\t11. Installed the RAIDManager jumbo patch 108834-09<\/p>\n
\t12. Performed a reconfiguratoin reboot:
\t\ttouch \/reconfigure
\t\tinit 6<\/p>\n
\t13. Verified the A1000 could be seen, and what firmware revision level
\t it was:<\/p>\n
\t\t\/usr\/lib\/osa\/bin\/raidutil -c c1t1d0 -i<\/p>\n
\t Firmware was currently at:
\t\t03.01.02.35<\/p>\n
\t14. Upgraded firmware to current versions. The current versions
\t are included as part of the patch install, and are stored in
\t \/usr\/lib\/osa\/fw.<\/p>\n
\t To install the latest boot code:<\/p>\n
\t\t\/usr\/lib\/osa\/bin\/fwutil 03010304.bwd c1t1d0<\/p>\n
\t To install the latest firmware:<\/p>\n
\t\t\/usr\/lib\/osa\/bin\/fwutil 03010363.apd c1t1d0<\/p>\n
\t15. Verified the A1000 was updated:<\/p>\n
\t\t\/usr\/lib\/osa\/bin\/raidutil -c c1t1d0 -i<\/p>\n
\t Reports something similar to:<\/p>\n
\t\tLUNs found on c1t1d0.
\t\tLUN 0 RAID 5 103311 MB<\/p>\n
\t\tVendor ID Symbios
\t\tProductID StorEDGE A1000
\t\tProduct Revision 0301
\t\tBoot Level 03.01.03.04
\t\tBoot Level Date 07\/06\/00
\t\tFirmware Level 03.01.03.63
\t\tFirmware Date 03\/15\/01
\t\traidutil succeeded!<\/p>\n
\t16. Now verify that the drives can be all seen:<\/p>\n
\t\t\/usr\/lib\/osa\/bin\/drivutil -i c1t1d0<\/p>\n
\t This will report something similar to:<\/p>\n
Drive Information for ig028_002<\/p>\n
Location Capacity Status Vendor Product Firmware \tSerial
(MB) ID Version \tNumber
[1,0] 17274 Optimal IBM DDYST1835SUN18G S96H 010811E164
[2,0] 17274 Optimal IBM DDYST1835SUN18G S96H 0108109219
[1,1] 17274 Optimal IBM DDYST1835SUN18G S96H 0108115692
[2,1] 17274 Optimal IBM DDYST1835SUN18G S96H 010811E211
[1,2] 17274 Optimal IBM DDYST1835SUN18G S96H 010810V958
[2,2] 17274 Optimal IBM DDYST1835SUN18G S96H 01081WH714
[2,3] 17274 Spare-Stdby IBM DDYST1835SUN18G S96H 010810V946<\/p>\n
\t17. Delete the default lun 0 configuration:<\/p>\n
\t\t\/usr\/lib\/osa\/bin\/raidutil -c c1t1d0 -D 0<\/p>\n
\t Reports something similar to:<\/p>\n
\t\tLUNs found on c1t0d0.
\t\tLUN 0 RAID 5 103644 MB
\t\tDeleting LUN 0.
\t\tPress Control C to abort.<\/p>\n
\t\tLUNs successfully deleted<\/p>\n
\t\traidutil succeeded!<\/p>\n
\t18. Created the RAID 1 drive mirrors by mirroring the following
\t pairs of drives:<\/p>\n
\t\t1,0 –> 2,0 mirrored as logical unit 0 (d0)
\t\t1,1 –> 2,1 mirrored as logical unit 1 (d1)
\t\t1,2 –> 2,2 mirrored as logical unit 2 (d2)<\/p>\n
\t Commands used:<\/p>\n
\t\t\/usr\/lib\/osa\/bin\/raidutil -c c1t1d0 -l 1 -n 0 -s 0 -r fast -g 10,20<\/p>\n
\t\t\/usr\/lib\/osa\/bin\/raidutil -c c1t1d0 -l 1 -n 1 -s 0 -r fast -g 11,21<\/p>\n
\t\t\/usr\/lib\/osa\/bin\/raidutil -c c1t1d0 -l 1 -n 2 -s 0 -r fast -g 12,22<\/p>\n
\t19. Created the hot spare drive using drive 2,3:<\/p>\n
\t\t\/usr\/lib\/osa\/bin\/raidutil -c c1t1d0 -h 23<\/p>\n
\t20. Partitioned and labeled each new drive with a single slice 2
\t partition as the whole disk using the format command.<\/p>\n
At this point the A1000 was ready to go on the first system. If this was
the only system, you would just build your filesystems and mount the drives
at this point, the same as any other drive.<\/p>\n
Because we were dual-porting this between two nodes of a future cluster,
we now needed to configure the second node. We now need to change the
scsi-initatior-id of the second controller to 6 (from the default of 7).
This is so both scsi controllers can be connected to the array at the
same time.<\/p>\n
To configure the second node:<\/p>\n
\t1. Leave the array disconnected from the second system for now<\/p>\n
\t2. Power on the second E220R<\/p>\n
\t3. Update the nvramrc to set the controller to id 6 per
\t the Sun Infodoc 20704 "Setting the scsi-initatior-id on PCI
Systems with Sun Cluster Software". (This applies to any
\t dual ported systems, cluster or not.)<\/p>\n
\t\tA. From the OBP prompt, get list of controllers:<\/p>\n
\t\t\tok setenv auto-boot? false
\t\t\tok reset-all
\t\t\tok probe-scsi-all<\/p>\n
\t\tB. edit nvramrc using the path for the scsi controller(s)
\t\t that you are changing:<\/p>\n
\t\t\tok nvedit
\t\t\t0: probe-all install-console banner
\t\t\t1: cd \/pci@1f,4000\/scsi@2,1
\t\t\t2: 6 " scsi-initiator-id" integer-property
\t\t\t3: device-end
\t\t\t4: cd \/pci@1f,4000\/scsi@2
\t\t\t5: 6 " scsi-initiator-id" integer-property
\t\t\t6: device-end
\t\t\t7: banner (Control C)<\/p>\n
\t\tC. Do a ctrl-c, and store the nvramrc:<\/p>\n
\t\t\tok nvstore<\/p>\n
\t\tD. Set the system to use the nvramrc:<\/p>\n
\t\t\tok setenv use-nvramrc? true<\/p>\n
\t\tE. Do a reset:<\/p>\n
\t\t\tok reset-all<\/p>\n
\t4. Verify the nvramrc settings were saved and that the
\t scsi-initiator-id was changed to 6 on the card:<\/p>\n
\t\tok cd \/pci@1f,4000\/scsi@2,1
\t\tok .properties<\/p>\n
\t It should report something like:<\/p>\n
\t\t"scsi-initiator-id 000000006"<\/p>\n
\t5. Cable the second system (node2) via port 1 of the dual-port
\t differential SCSI card to the second SCSI port on the A1000.<\/p>\n
\t6. Reset the system again and then probe the scsi bus
\t to verify it sees the array:<\/p>\n
\t\tok reset-all
\t\tok probe-scsi-all<\/p>\n
\t7. Reset the auto-boot parameter, and then reset the
\t system and allow it to boot:<\/p>\n
\t\tok setenv auto-boot? true
\t\tok reset-all<\/p>\n
\t8. Install the RAIDManager ver 6.22 software and jumbo patch
\t as you did on the first node.<\/p>\n
\t9. Verify the RAIDManager software can see the configured array:<\/p>\n
\t \/usr\/lib\/osa\/bin\/raidutil -c c1t1d0 -i
\t \/usr\/lib\/osa\/bin\/drivutil -i c1t1d0<\/p>\n
\t *** DO NOT CONFIGURE THE RAID – IT IS ALREADY CONFIGURED ***<\/p>\n
\t10. Verify the the OS utilities (format, prtvtoc, etc.) can see the drives.<\/p>\n
At this point, the hardware is all configured. Next we need to
configure the Volume Manager and File System software.<\/p>\n
VXVM\/VXFS configs:<\/p>\n
\t1. Install the VXVM and VXFS software:<\/p>\n
\t\tmount -r -F hsfs \/dev\/sr0 \/cdrom
\t\tcd \/cdrom\/… (don't remember the exact path)
\t\tpkgadd -d . VRTSvxvm VRTSvmdev VRTSvmdoc VRTSvmman VRTSvmsa VRTSvxfs VRTSfsdoc<\/p>\n
\t This installs the following packages:<\/p>\n
\t\tsystem VRTSfsdoc VERITAS File System Documentation Package
\t\tsystem VRTSvmdev VERITAS Volume Manager, Header and Library Files
\t\tsystem VRTSvmdoc VERITAS Volume Manager (user documentation)
\t\tsystem VRTSvmman VERITAS Volume Manager, Manual Pages
\t\tsystem VRTSvmsa VERITAS Volume Manager Storage Administrator
\t\tsystem VRTSvxfs VERITAS File System
\t\tsystem VRTSvxvm VERITAS Volume Manager, Binaries<\/p>\n
\t NOTE: The manpages and docs are all optional. Also, the latest
\t\t packages can be obtained via the Veritas ftp site after
\t\t contacting Veritas.<\/p>\n
\t2 – Install the Veritas licenses:<\/p>\n
\t\tvxserial -c<\/p>\n
\t Enter the license key for each product. At a minimum, you need the
\t base volume manager key, and the veritas filesystem key. If you will
\t be using RAID 5, also enter that key.<\/p>\n
\t3 – Run vxinstall to complete the installation:<\/p>\n
\t\tvxinstall<\/p>\n
\t This will prompt for a quick or custom install. Select Quick Install<\/p>\n
\t\t1. Quick Installation
\t\t\t– encapsulate the boot drive c0t0d0
\t\t\t– use default disk names
\t\t\t– initial the mirror drive c0t1d0
\t\t\t– initial all drives on controller 1 (the array)<\/p>\n
\t NOTE: In order to properly encapsulate the boot drive, you need to have:<\/p>\n
\t\t– an unused cylinder at the beginning or end of drive
\t\t– slices 3 and 4 must be unused<\/p>\n
\t\tTo do this, I usually label the boot drive to have the root
\t\tslice 0 start at cylinder 1, and then only use slices 1,5,6,7 for
\t\tswap and the other filesystems.<\/p>\n
\t4 – Reboot the system when prompted<\/p>\n
\t5 – Verify all drives were configured and are seen:<\/p>\n
\t\tvxdisk list<\/p>\n
\t6 – Verify the root drive was encapsulated. The \/etc\/vfstab file and
\t df should both show that the root filesystems now are using \/dev\/vx
\t devices.<\/p>\n
\t7 – Delete the array drives from rootdg (quick install only creates rootdg
\t and places all drives in it.):<\/p>\n
\t\tvxdg -g rootdg rmdisk disk02
\t\tvxdg -g rootdg rmdisk disk03
\t\tvxdg -g rootdg rmdisk disk04<\/p>\n
\t8 – Now initialize the datadg disk group. You do this by naming the first
disk that will be in the group:<\/p>\n
\t\tvxdg init datadg disk02=c1t1d0s2<\/p>\n
\t9 – Now add the remaining drives to datadg:<\/p>\n
\t\tvxdg -g datadg adddisk disk03=c1t1d1s2
\t\tvxdg -g datadg adddisk disk04=c1t1d2s2<\/p>\n
\t10 – Mirror the root drive. First we mirror the root filesystem and
\t make the mirror drive bootable:<\/p>\n
\t\t\/etc\/vx\/bin\/vxrootmir disk01<\/p>\n
\t11 – Now mirror the remainder of the root volumes:<\/p>\n
\t\tvxassist -g rootdg mirror swapvol disk01
\t\tvxassist -g rootdg mirror usr disk01
\t\tvxassist -g rootdg mirror opt disk01
\t\tvxassist -g rootdg mirror var disk01<\/p>\n
\t NOTE: You cannot reboot until the volumes have completed the mirroring
\t\t process. If you do, you have to start them again. To verify the
\t\t mirrors are done, run:<\/p>\n
\t\t\tvxprint -ht<\/p>\n
\t\t And each volume shows as being ENABLED and ACTIVE, i.e.:<\/p>\n
\tv usr – ENABLED ACTIVE 4283208 fsgen – ROUND
\tpl usr-01 usr ENABLED ACTIVE 4283208 CONCAT – RW
\tsd rootdisk-03 usr-01 rootdisk 31080352 4283208 0 c0t0d0 ENA
\tpl usr-02 usr ENABLED ACTIVE 4283208 CONCAT – RW
\tsd disk01-03 usr-02 disk01 2709400 4283208 0 c0t1d0 ENA<\/p>\n
\t12 – Now build the datadg volumes. In this example, we are building 3 simple
\t volumes, one per disk, and we use the filesystem name as the volume name.<\/p>\n
\t\tA. Get the maxsize of the drive(s):<\/p>\n
\t\t\tvxassist -g datadg disk02<\/p>\n
\t\tB. Now create the mh volume using the maxsize returned above (17228m)
\t\t on disk02:<\/p>\n
\t\t\tvxassist -g datadg make mh 17228m layout=concat disk02<\/p>\n
\t\tC. Now create the ms volume using the maxsize returned above (17228m)
\t\t on disk03:<\/p>\n
\t\t\tvxassist -g datadg make ms 17228m layout=concat disk03<\/p>\n
\t\tD. Now create the amt volume using the maxsize returned above (17228m)
\t\t on disk04:<\/p>\n
\t\t\tvxassist -g datadg make amt 17228m layout=concat disk04<\/p>\n
\t13 – Now build the VXFS filesystems on each volume:<\/p>\n
\t\tmkfs -F vxfs -o largefiles \/dev\/vx\/rdsk\/datadg\/mh
\t\tmkfs -F vxfs -o largefiles \/dev\/vx\/rdsk\/datadg\/ms
\t\tmkfs -F vxfs -o largefiles \/dev\/vx\/rdsk\/datadg\/amt<\/p>\n
\t14 – At this point the volumes and filesystems are ready to go. Use vxprint
\t to verify all configs:<\/p>\n
\t\tvxprint -ht | more<\/p>\n
\t The output will look like:<\/p>\n
Disk group: rootdg<\/p>\n
DG NAME NCONFIG NLOG MINORS GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
V NAME RVG KSTATE STATE LENGTH USETYPE PREFPLEX RDPOL
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL\/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL\/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL\/]OFF AM\/NM MODE<\/p>\n
dg rootdg default default 0 989258071.1025.node1<\/p>\n
dm disk01 c0t1d0s2 sliced 4711 35363560 –
dm rootdisk c0t0d0s2 sliced 4711 35363560 –<\/p>\n
v opt – ENABLED ACTIVE 20662120 fsgen – ROUND
pl opt-01 opt ENABLED ACTIVE 20662120 CONCAT – RW
sd rootdisk-04 opt-01 rootdisk 10418232 20662120 0 c0t0d0 ENA
pl opt-02 opt ENABLED ACTIVE 20662120 CONCAT – RW
sd disk01-04 opt-02 disk01 6992608 20662120 0 c0t1d0 ENA<\/p>\n
v rootvol – ENABLED ACTIVE 607848 root – ROUND
pl rootvol-01 rootvol ENABLED ACTIVE 607848 CONCAT – RW
sd rootdisk-02 rootvol-01 rootdisk 0 607848 0 c0t0d0 ENA
pl rootvol-02 rootvol ENABLED ACTIVE 607848 CONCAT – RW
sd disk01-01 rootvol-02 disk01 0 607848 0 c0t1d0 ENA<\/p>\n
v swapvol – ENABLED ACTIVE 2101552 swap – ROUND
pl swapvol-01 swapvol ENABLED ACTIVE 2101552 CONCAT – RW
sd rootdisk-01 swapvol-01 rootdisk 607848 2101552 0 c0t0d0 ENA
pl swapvol-02 swapvol ENABLED ACTIVE 2101552 CONCAT – RW
sd disk01-02 swapvol-02 disk01 607848 2101552 0 c0t1d0 ENA<\/p>\n
v usr – ENABLED ACTIVE 4283208 fsgen – ROUND
pl usr-01 usr ENABLED ACTIVE 4283208 CONCAT – RW
sd rootdisk-03 usr-01 rootdisk 31080352 4283208 0 c0t0d0 ENA
pl usr-02 usr ENABLED ACTIVE 4283208 CONCAT – RW
sd disk01-03 usr-02 disk01 2709400 4283208 0 c0t1d0 ENA<\/p>\n
v var – ENABLED ACTIVE 7708832 fsgen – ROUND
pl var-01 var ENABLED ACTIVE 7708832 CONCAT – RW
sd rootdisk-05 var-01 rootdisk 2709400 7708832 0 c0t0d0 ENA
pl var-02 var ENABLED ACTIVE 7708832 CONCAT – RW
sd disk01-05 var-02 disk01 27654728 7708832 0 c0t1d0 ENA<\/p>\n
Disk group: datadg<\/p>\n
DG NAME NCONFIG NLOG MINORS GROUP-ID
DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
RV NAME RLINK_CNT KSTATE STATE PRIMARY DATAVOLS SRL
RL NAME RVG KSTATE STATE REM_HOST REM_DG REM_RLNK
V NAME RVG KSTATE STATE LENGTH USETYPE PREFPLEX RDPOL
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT NCOL\/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL\/]OFF DEVICE MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL\/]OFF AM\/NM MODE<\/p>\n
dg datadg default default 59000 989266501.1167.node1<\/p>\n
dm disk02 c1t1d0s2 sliced 4095 35282944 –
dm disk03 c1t1d1s2 sliced 4095 35282944 –
dm disk04 c1t1d2s2 sliced 4095 35282944 –<\/p>\n
v amt – ENABLED ACTIVE 35282944 fsgen – SELECT
pl amt-01 amt ENABLED ACTIVE 35282944 CONCAT – RW
sd disk04-01 amt-01 disk04 0 35282944 0 c1t1d2 ENA<\/p>\n
v mh – ENABLED ACTIVE 35282944 fsgen – SELECT
pl mh-01 mh ENABLED ACTIVE 35282944 CONCAT – RW
sd disk02-01 mh-01 disk02 0 35282944 0 c1t1d0 ENA<\/p>\n
v ms – ENABLED ACTIVE 35282944 fsgen – SELECT
pl ms-01 ms ENABLED ACTIVE 35282944 CONCAT – RW
sd disk03-01 ms-01 disk03 0 35282944 0 c1t1d1 ENA<\/p>\n
\t15 – If the volumes\/filesystems are to be managed as part of a cluster
\t the should now be added to it. If not, then the filesystems can
\t be added to node 1 using standard methods:<\/p>\n
\t\tmkdir \/mh
\t\tmkdir \/ms
\t\tmkdir \/amt
\t\tedit \/etc\/vfstab and add the 3 new volumes\/filesystems
\t\tmountall<\/p>\n
At this point, all filesystems should be online and operational. To manually
failover the array between nodes:<\/p>\n
\t1 – Unmount the filesystems on node 1<\/p>\n
\t\tumount \/mh
\t\tumount \/ms
\t\tumount \/amt<\/p>\n
\t2 – Deport the datadg disk group from node 1 (you can also use
\t the vxdiskadm menu for this):<\/p>\n
\t\tvxdg deport datadg<\/p>\n
\t3 – Import the datadg disk group on node 2 (you can also use
\t the vxdiskadm menu for this):<\/p>\n
\t\tvxdg import datadg<\/p>\n
\t NOTE: If the disks show as offline on node 2 (vxdisk list),
\t\t then you need to put them online before importing, i.e:<\/p>\n
\t\t\tvxdisk online c1t1d0s2<\/p>\n
Also, if the first node has failed and you were unable
to deport the disks first, you would need to force the
import with the -f option.<\/p>\n
\t4 – Enable the imported volumes:<\/p>\n
\t\tvxrecover -s<\/p>\n
\t This will attempt to enable all volumes. If you wish to
\t enable only certain volumes, use:<\/p>\n
\t\tvxrecover -s [volume_name]<\/p>\n
\t If you forget this step, you will get an error about the
\t volume not existing when you try to mount\/access it.<\/p>\n
\t5 – Mount the filesystems<\/p>\n
\t\tmount \/dev\/vx\/dsk\/datadg\/mh \/mh
\t\tmount \/dev\/vx\/dsk\/datadg\/ms \/ms
\t\tmount \/dev\/vx\/dsk\/datadg\/amt \/amt<\/p>\n
To fail back, you would use the same procedure.<\/p>\n","protected":false},"excerpt":{"rendered":"
Petit tutorial sur Veritas FS, gestion du file system de VERITAS.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[8],"tags":[],"class_list":["post-106","post","type-post","status-publish","format-standard","hentry","category-informatique"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pWrTo-1I","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/106","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=106"}],"version-history":[{"count":0,"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/106\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=106"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=106"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.lookit.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=106"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}