Sponsored Content
Operating Systems Solaris Why Veritas is not used for root file system. Post 302424450 by Rowley on Tuesday 25th of May 2010 08:57:19 AM
Old 05-25-2010
SDS or SVM is easy to set up either manually or through jumpstart, troubleshoot, maintain, and is the de-facto software disk manager solution on Solaris, and it works perfectly well.

Why bother going through the bother of encapsulating the root disk with VxVM? Save it for your data volumes....

My ha-pennies worth, anyway.
This User Gave Thanks to Rowley For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Veritas File System

Hello All. I have a question concerning VFS (Veritas File System). I are attempting to upgrade Solaris 2.6 UFS to the VFS (Veritas File System). We use Veritas to perform all our backups. I have been unable to find any documentation on SUN's or Veritas's website. The server's are SUN 4500 and... (3 Replies)
Discussion started by: KaEH
3 Replies

2. Filesystems, Disks and Memory

veritas vcs \ file system docs req.

hi if anyone has docs (corporate internals on how to setup vcs mfor example, especially with Veritas VM, pleas let me know..i need exposure experience in this area of Enterprise Administration thanks jasmine (SCSA & MCSE) (2 Replies)
Discussion started by: jasmine_uk
2 Replies

3. HP-UX

Root File system Space

Hi I'm using HP-UX 11.00, the root file system is as shown below. Several time it reach 100% used, to free some space I use to reboot the system. What can I do to free some space without rebooting the machine? Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol3 ... (2 Replies)
Discussion started by: cgege
2 Replies

4. Solaris

Veritas root disk mirroring

Hi there, My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct. 1. Break the sub-disks, plexes of the root mirror. 2. Remove the sub-disks,plexes of the root mirror. 3. Remove one of... (10 Replies)
Discussion started by: Jartan
10 Replies

5. Solaris

swap space in veritas file system

hi every one , i know how to add swap space in ufs file system. but i m facing problem in veritas file system . i wants to know how will i create swap or add new swap space in existing swap space . Note: disk under veritas volume manager control . please help me to solve this issue . (5 Replies)
Discussion started by: samy123
5 Replies

6. UNIX for Dummies Questions & Answers

Root File System

Hi, Please someone tell me, what are the contents of root file sysytem? and significance of it, what are all possible ways to mount root file system? (5 Replies)
Discussion started by: laxmi Sharma
5 Replies

7. Solaris

Migration of system having UFS root FS with zones root to ZFS root FS

Hi All After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies

8. Solaris

restore dump from veritas format using ufs file system

hi all i have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it? right now i don't have veritas file system setup. i have only ufs file sysytem please help some production data is to be restore. (3 Replies)
Discussion started by: nikhil kasar
3 Replies

9. Solaris

how to restore backup from veritas vm in ufs file system

Hi all I have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it? right now i don't have veritas file system setup. i have only ufs file sysytem please help some production data is to be restore. backup was taken... (0 Replies)
Discussion started by: nikhil kasar
0 Replies

10. UNIX for Dummies Questions & Answers

Question on Veritas file system..

Hi, I am on Solaris 10 server which is running Veritas. It's E420 server with two drives. I don't know much about Veritas. The other guy who works on this, on vacation this week. :-) Any way, looks like I have hard drive issue on the server. When I do iostat -E. I see this. sd0... (4 Replies)
Discussion started by: samnyc
4 Replies
bootconf(4)						     Kernel Interfaces Manual						       bootconf(4)

NAME
bootconf - boot device configuration table DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate boot devices should be automatically updated, the administrator must edit the file manually. There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown: disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following: Indicates that the root disk is in LVM or VERITAS Volume Manager (VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file. Indicates that the root disk is in the "whole disk" format with no partitions, but boot and swap space are reserved outside the file system. device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file that references the entire disk. Blank lines are permitted. Any line beginning with a is considered to be a comment. DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self- explanatory; a few warrant additional explanation: If there are no other messages about the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem is. The specified device file does not point to a disk where there is a lif which contains the file Some character other than or is in the first field of a line. As of release 10.0, the boot areas in must all be on the same type of disk layout. There are characters after the device file specification. EXAMPLES
The boot area is on an LVM root disk: l /dev/disk/disk7_p2 The boot area is on a whole disk layout: w /dev/disk/disk7 WARNINGS
All of the boot devices in the file must have the same disk layout. AUTHOR
was developed by the Hewlett-Packard Company. FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7). documentation. bootconf(4)
All times are GMT -4. The time now is 08:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy