Duplicating the Veritas disks VTOCs with fmthard

[dbase77]

Hi,

Im trying to duplicate root disk vtoc on another disk. Command that I use as follow:

prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t2d0s2

I received this error:

fmthard: Partition 0 overlaps partition 4. Overlap is allowed only on partition on the full disk partition).

Am I missing something here? How do I go about solving this problem?

Thank you in advance.

regards,
dbase77

 

[KenCunningham]

This probably isn't of much help, as there doesn't appear to be a solution attached, but:

http://www.netsys.com/sunmgr/2002-10/msg00223.html

details the same problem and offers some undocumented switches which you might want to try. There is also a mention elsewhere of a patch to prevent this problem in SDS, but possibly this doesn't affect Veritas. Anyway, good luck!

 

[daFranze]

can I see the vtoc pls.?

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years

 

[dbase77]

Hi,

Thank you for replying. Here is output from vtoc:

* /dev/rdsk/c1t0d0s2 partition map
*
* Dimensions:
* 512 bytes/sector
* 424 sectors/track
* 24 tracks/cylinder
* 10176 sectors/cylinder
* 14089 cylinders
* 14087 accessible cylinders
*
* Flags:
* 1: unmountable
* 10: read-only
*
* Unallocated space:
* First Sector Last
* Sector Count Sector
* 143349312 4240444288 88826303
*
* First Sector Last
* Partition Tag Flags Sector Count Sector Mount Directory
0 2 00 88826304 20972736 109799039
1 3 01 109799040 33550272 143349311
2 5 01 0 143349312 143349311
3 15 01 0 10176 10175
4 14 01 10176 143339136 143349311


regards,
dbase77

 

[daFranze]

unfortunately I do not have a Veritas Boot Disk any more, so I cannot compare to my installations, but afaik s3 is private Region and s4 is public region, since it is the OS's boot disk you need to have a boot slice for the os-loader/OBP, which is s0 (I guess); if you install VeritasVM on the system and you do a boot disk mirror with VeritasVM it will generate s3 and s4 with overlapping partitions, so fmthard is correct, when it says there are;

if you want to copy the layout I suggest to do this via format (save a layout and use one "by name")
At Sun I "learned" to mirror OS Disks with SDS only... ;-)

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years

 

[dbase77]

Hi,

Thank you for the information. Looks like I still need to use format to set the partition manually.

Thank you again.

regards,
dbase77

 

[mikeclark]

You have probably sorted this out by now but as the error said you have overlapping partitians.
Partitian 2 is the whole disk 0 to 143349311

partitian 3 is 0 10176 10175
partitian 4 is 10176 143339136 143349311
which uses the rest of the disk.
partitians 0 and 1 also use the same area which just don't work.
Where one partitian ends the next one should start from the next sector onwards.

 

[daFranze]

@mike

Veritas encapsulated this disk! There overlapping partitions, yes that's right, but this is how Veritas works with the disks! S2 is very much the same!

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years

 

[screwloose]

The comments leads me to a question on slices for a disk. A coworker has been partitioning all of the disks in a manner as shown below:

0 root wm 0 - 68 129.38MB (69/0/0) 264960
1 swap wu 69 - 137 129.38MB (69/0/0) 264960
2 backup wu 0 - 36825 67.43GB (36826/0/0) 141411840
3 unassigned wm 138 - 4507 8.00GB (4370/0/0) 16780800
4 unassigned wm 4508 - 26353 40.00GB (21846/0/0) 83888640
5 unassigned wm 26354 - 31979 10.30GB (5626/0/0) 21603840
6 usr wm 31980 - 36825 8.87GB (4846/0/0) 18608640
7 unassigned wm 0 0 (0/0/0) 0

but starts using slice 3, then 4 and 5. Leaving slice 6 to contain the rest, minus slices 0 and 1 which have approx 250MB of disk available. This coworker has done this on every disk they have setup. Whereas, I blank out all slices and then allocate from slice 0, then 1, and so on, so I don't waste disk space.

Is the way I do it the correct way, or am I missing something and my coworker is doing it properly?

Thanks.

 

[screwloose]

I would also like to add this is EMC disk and I am use to AIX and LVM, where I can create a volume group and then logical volumes and add to them as needed. The way the company has gone about setting up the EMC disk with DiskSuite is to use the whole disk if needed or can be, yet, there are many times they only want 300MB or 500MB for a filesystem which leaves me slicing up a disk, with some slices on a disk going to 3, 4, or 5 different filesystems. Is there a better way to be allocating the EMC disk?

This is Solaris 9 with DiskSuite.

Thanks.