Error Writing Vtoc In Solaris
Contents |
known simply as Solaris, is a Unix-based operating system introduced by Sun Microsystems. The Solaris OS is now owned by Oracle. Search Forums Show Threads Show Posts vtoc solaris 10 Tag Search Advanced Search Unanswered Threads Find All Thanked Posts Go to Page...
Solaris Vtoc Label
learn linux and unix commands - unix shell scripting label a slice on disk erorr Solaris warning error writing vtoc. label failed Thread Tools Search this Thread Display Modes #1 02-10-2012 newbi8321 Registered User Join Date: Feb 2012 Last Activity: 25 November 2013, 9:48 AM EST Posts: 3 Thanks: 5 Thanked 0 Times in 0 Posts label a slice on disk erorr Hi there, I am trying to do root volume mirroring on SunFire V210 server. I have two disks in it.First one is c1t0do and second one is c1t1do. Both disks already have partitions in them so I am deleting the partitions of second disk(c1t1do) using format command and selecting cylinder start 0 and size 0mb. When I do the same on partition 6 I could not able to label the partition 6 and its shows an error. Please help me . Thanks in advance. Code: partition> 6 Part Tag Flag Cylinders Size Blocks 6 unassigned wm 4027 - 4047 104.34MB (21/0/0) 213696 Enter partition id tag[unassigned]: Enter partition permission flags[wm]: Enter new starting cyl[4027]: 0 Enter partition size[213696b, 21c, 20e, 104.34mb, 0.10gb]: 0mb partition> label Ready to label disk, continue? y Warning: error writing VTOC. Warning: no backup labels Label failed. ---------- Post updated at 11:01 PM ---------- Previous update was at 10:42 PM ---------- Solution : You should never make size of slice 2 0mb. Remove advertisements Sponsored Links newbi8321 View Public Profile Find all posts by newbi8321 #2 02-10-2012 cerber0 Registered User Join Date: Nov 2008 Last Activity: 18 September 2016, 8:30 AM EDT Location: Mexico DF Posts: 46 Thanks: 0 Thanked 5 Times in 5 Posts I think that you should not delete the slice 2 (backup partition), this partition normally contains all space on disk. The Following User Says Thank You to cerber0 For This
Volume Details Solaris Volume Manager Solaris VTOC Errors Availability Suite Overview A Solaris raw disk or LUN, when initialized by the utility format(1M), contains one or more partitions (slices) with information on the physical layout of the volume. This information is stored in cylinder 0 in the VTOC. The VTOC is located on each formatted disk and, in most cases, mapped in partition 2 (the backup partition), which often includes every block on the raw http://www.unix.com/solaris/176614-label-slice-disk-erorr.html device. A physical backup of partition 2 to an identical disk's partition 2 copies the data in every single block, including the volume's VTOC. It is recommended that the ONLY time any partition containing a VTOC be used is when identical disks are configured and one is attempting to do a physical backup of one disk's partition 2 https://docs.oracle.com/cd/E19359-01/819-6151-10/VTOCprotect.html to partition 2 of another disk of the same size. Other scenarios of using a partition containing a VTOC are often problematic. Volume Details For optimal use of almost every block on a raw disk or LUN, Solaris' supported volume managers, file systems, and databases (and many other applications that can use individual partitions on a disk for storage) have knowledge of a volume's VTOC and have incorporated software to exclude writing any data to, or on top of, the volume's VTOC. By using the Solaris prtvtoc(1M), format(1M), or metastat(1M) utilities, a system administrator can determine if any source or destination device has partitions or metadevices containing cylinder 0. If the partitions or volumes are used for backup, mirroring, replication, or snapshots, it must be understood that the VTOC of the source device will be copied to the destination device, possibly changing the destination device's VTOC. If the volumes contained in raw device partitions or volumes do not contain cylinder 0, there would be no change in the disk
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring http://serverfault.com/questions/198557/how-can-solaris-format-write-to-a-disk-without-a-vtoc-being-present developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top how can Solaris format write to a disk without a vtoc being present? up vote 1 down vote error writing favorite 1 Facts: VTOC (or EFI) is required to access slices of a disk device s2 slice is used to access whole disk (including VTOC on the disk beginning) new disk device comes without VTOC system: Solaris 10 OS, on SPARC architecture Question: How can it be, that format is able write VTOC to a disk if it does not have a VTOC? Question in detail: To create VTOC, format needs to write s2. To write s2, VTOC needs to error writing vtoc exist. Simplified: to create VTOC, VTOC needs to exist. How this chicken and egg problem is avoided by format? ext #1: if I label an un-labeled disk (c2t5006016041E076B0d8s2), the following happens: [...] 11157: open("/dev/rdsk/c2t5006016041E076B0d8s2", O_RDWR|O_NDELAY) = 3 [...] 11157/1: write(1, " D i s k n o t l a b".., 33) = 33 11157/1: read(0, 0xFF2B9CD0, 1024) (sleeping...) 11157/1: read(0, " y\n", 1024) = 2 11157/1: open("/dev/rdsk/c3t5006016141E076B0d8s0", O_RDONLY|O_NDELAY) = 4 11157/1: ioctl(4, 0x0417, 0xFFBFED80) Err#22 EINVAL 11157/1: close(4) = 0 11157/1: ioctl(3, 0x04C9, 0xFFBFF52C) = 0 11157/1: ioctl(3, 0x0402, 0xFFBFF644) = 0 11157/1: ioctl(3, 0x0418, 0xFFBFF670) = 0 11157/1: ioctl(3, 0x04C9, 0xFFBFF5B4) = 0 11157/1: ioctl(3, 0x04C9, 0xFFBFF5B4) = 0 11157/1: ioctl(3, 0x04C9, 0xFFBFF5B4) = 0 11157/1: ioctl(3, 0x04C9, 0xFFBFF5B4) = 0 11157/1: ioctl(3, 0x04C9, 0xFFBFF5B4) = 0 11157/1: write(1, "\n\n F O R M A T M E N".., 15) = 15 [...] what are those ioctl() calls? They cleanly do the job, but what are these calls actually? solaris hard-drive share|improve this question edited Nov 8 '10 at 10:55 asked Nov 5 '10 at 12:07 asdmin 1,4981122 add a comment| 3 Answers 3 active oldest votes up vote 4 down vote accepted The OS doesn't use read/write calls to read or write the vtoc. It just need to be able to successfully open the s2 device (which is just a symlink to the real device) to know if a disk is there. There is hop