( If you still see that message detach and attach the diskĨ. Actually you findĭisk and metavolumes are ok and I/O is happening to theįile systems… how will you remove the metareplace messageĪns: Do a two way mirror and check the metastat –p. Metastat -p shows a metavolume needs replacement. System corrupted 3) Wrong entries in /etc/vfstab fileħ. You have a boot disk under svm, the machine fails toīoot and remains in ok prompt? what could be the possibleĪns: 1) May be issue with /etc/system file 2) Root file Insufficient state database replicas issues 3) WrongĦ. What are the common errors you find in Solaris VolumeĪns: 1) Disks failures (Boot device failures) 2) Hence its good to create as many replicas on separateĥ. ![]() If all the three database replicas are corrupted meaning we State database replicas when we setup a disk configuration. Is achieved by using “majority consensus algorithm” andĪccording to this algorithm we need half+1 number of stateĭatabase replicas before it finds for a valid data.Īnd for the above reason we need to recreate at least three Should figure out which state database replicas stillĬontain valid data and boot using the valid ones and this If the solaris box loses a state database replica, SVM Replicated database copies and each copy is considered as a What is the significance of 51% state database replicasĪns: A state database is the collections of multiple, #metareplace -e d11 devicename ( Where d11 is theĤ. #prtvtoc /dev/rdsk/devicename | fmthard -s –Ħ) Once the VTOC is in place now use metareplace command to Once unconfigured replace the disk and configure it asĥ) Now copy the Volume Table Of Contents (VTOC) to the new #metadb –d c0t0d0sX where x is slice numberģ) Once the meta state databases are removed we can use Submirrors and once replaced it resyncs with the failedġ) Find the meta state databases on the sliceĢ) If any meta state databases exist remove them ![]() What you would do if you want to replace a slice usingĪns: We use metareplace usually when we have have faulty If you get error here : #metadetach -f d1 d2ģ) Now check the status again: # metastat -p ![]() How do you replace a failed boot disk under Meta inĪns: 1) Checks the disks available: #metastat –pĢ) Detach the one with errors: #metadetach d1 d2.Metadb -d c1t0d0s7to scan for the newly added disk.Devfsadm prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s – /dev/rdsk/c1t1d0s2 fmthard: New volume table of contents now in place. installboot /usr/platform/sun4u/lib/fs/ufs/bootblk /dev/rdsk/c1t1d0s0 metadb -afc 3 c1t0d0s7 metadevadm -u c1t0d0 metattach # metattach d10 d11# metattach d0 d1 # metareplace -e d0 c1t0d0s0 d0: device c1t0d0s0 is enabled# metareplace -e d10 c1t0d0s1 d10: device c1t0d0s1 is enabled /sbin/installgrub /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c1t0d0s0 GRUB: GRUB is the reference implementation of the Free Software Foundation’s Multi boot Specification, which provides a user the choice to boot one of multiple operating systems installed on a computer or select a specific kernel configuration available on a particular operating system’s partitions. How do you replace a failed boot disk under meta in solaris? Step by step explanation? You can add acls for user “user1” using folowing command-#setfacl -m u:user1:r–,g:testgroup:r– File1Thanks,Amit Shiknis How to use -s and -m in acl ? Give two examples? In server where will you find route information? How will you clear counter of iostat without rebooting the Solaris OSġ) minute filed -1-602) hourfiled-–1-243) day of month filed-1-304) month filed-–1-125) week filed-–1-66) command filed-/dec/cosole
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |