Sponsored Content
Operating Systems Solaris No local disk in format in Solaris Post 302777267 by solaris_1977 on Thursday 7th of March 2013 02:20:26 PM
Old 03-07-2013
format gives me long output of all Storage disks, but none of both local disks. Yes, disks are encapsulated with VxVM
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Finding local disk space

Hi Guys!! Iam new to this thread. I have a very urgent requirement of finding the local disk space. Iam running a php script on linux machine and need to find the local disk space on the remote machines. I tried using df -h, which works if I specify the drive name on the remote machine.... (4 Replies)
Discussion started by: navjak
4 Replies

2. Solaris

run xclock from local solaris to remote solaris

Hello - I am trying to connect to a remote solaris box from a solaris box i have locally present with me using 'ssh login@IP' ... Its connecting fine but... when I run xclock - it says 'Can't open display' Whereas, IF I connect to same remote solaris IP from my windows desktop locally via putty... (9 Replies)
Discussion started by: panchpan
9 Replies

3. Solaris

installing from local disk

We ordered a DVD for solaris 10 upgrade . However I realized that we have cd rom only and DVD is unreadable . Can i use this DVD , to upgrade the release from local disks. If yes , is there any specific procedure. (5 Replies)
Discussion started by: Hitesh Shah
5 Replies

4. UNIX for Advanced & Expert Users

Problems with tar between local and nfs disk

Hi, I am trying to move a local directory from a local disk to a nfs disk that has been shared on another file server. I am using this tar command: tar cf - . | (cd /export/nfsdisk && tar xpf - ) It copies the data okay but the big problem is that is resets the owner:group to 'nobody'. The... (2 Replies)
Discussion started by: jlowry
2 Replies

5. UNIX for Dummies Questions & Answers

Are disk format across AIX and Solaris platforms compatable?

I totally new to UNIX and I have a newbie question. I have 2 servers, AIX and Solaris and I need to be on just one platform. both serves have 2 physical drives, with the OS on one and data on the other. can I take the data drive from the AIX server and mount it on the Solaris server? or would... (2 Replies)
Discussion started by: AusTan24
2 Replies

6. Solaris

Sharing a local disk between to solaris machines

Hi, I recently added a disk on a solaris 9 and I wanted to make it accessible for another machine, using the same name here is what i did : On the machine holding the internal disk in vfstab i added the line /dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /SHARED2 ufs 2 yes ... (2 Replies)
Discussion started by: zionassedo
2 Replies

7. AIX

Sysdump on local disk

Hello Team, Our p740 systems are booting up from SAN. We would like to configure the local disk(which is not part of rootvg) as a primary dump device. I have assigned the same too. But in the errpt throwing the below error. Please help me on this. ... (1 Reply)
Discussion started by: gowthamakanthan
1 Replies

8. Shell Programming and Scripting

Unable to convert passwd lastupdate value into scalar local format

Dear all, I am unable to get the desired result upon executing the below script. the problem is at `perl -le 'print scalar localtime $msecage'` ouput which gives the following result "Thu Jan 1 05:00:00 1970" instead of "Tue Nov 13 10:30:56 2012" but when I run the same command from shell... (2 Replies)
Discussion started by: m_raheelahmed
2 Replies

9. UNIX for Beginners Questions & Answers

SAN vs. Local disk.

I am in the market looking to purchase a new E950 server and I am trying to decide between using local SSD drives or SSD based SAN. The application that will be running on this server is read-intensive so I am looking for the most optimal configuration to support this application. There are no... (2 Replies)
Discussion started by: ikx
2 Replies
vxdisksetup(1M) 														   vxdisksetup(1M)

NAME
vxdisksetup, vxdiskunsetup - configure a disk for use with Veritas Volume Manager SYNOPSIS
vxdisksetup [-ifB] disk_address [attribute ...] vxdisksetup [-ifB] disk_address format=hpdisk [attribute ...] vxdisksetup [-if] disk_address format=cdsdisk [attribute ...] /etc/vx/bin/vxdiskunsetup [-C] [-F] disk_address... DESCRIPTION
The vxdisksetup command configures the disk for use by Veritas Volume Manager (VxVM). vxdisksetup is called by the vxdiskadd command as part of initial disk configuration. It is not typically necessary to call this command directly. Note: In release 4.0 of VxVM, the behavior of the vxdisksetup command has been changed so that it only creates auto-configured disks (with a disk access type of auto; see vxdisk(1M)), which can have one of the following formats: cdsdisk The disk is formatted as a CDS disk that is suitable for moving between different operating systems. This is the default format for non-EFI disks (provided that the -i option is used to write the disk header). It is not suitable for boot disks or EFI disks. Note: As the CDS format is applied to the entire disk and is unsuitable for boot disks, options and attributes that relate to partitions, slices or booting are not applicable. The CDS format is also incompatible with EFI disks. hpdisk The disk is formatted to include a private region that VxVM uses to store configuration information. Following the private region, the remainder of the disk forms the public region from which subdisks can be allocated. This format can be applied to disks that can be used to boot the system. If the disk is not initialized as a boot disk, space is reserved on the disk to allow it to be converted to cdsdisk format if required. The hpdisk format is the default for EFI disks. none The disk is unformatted. Note: This value may be displayed, but it cannot be set as a valid format. The vxdiskunsetup command reverses the configuration done by vxdisksetup and makes the specified disks unusable by VxVM. vxdiskunsetup can be applied only to VxVM-initialized disks that are not in use within an imported disk group. The disk_address argument passed to vxdisksetup or to vxdiskunsetup directs the command to the device that corresponds to the disk being operated upon. The address should be provided in the form c#t#d#, which define a controller number (c#), a SCSI target ID (t#), and a SCSI logical unit number (d#). Each number is specified in decimal and can be multiple digits. If the disks are named using the enclosure based naming scheme, the address usually takes the form enclosurename_diskno. The name must reference a valid disk under the /dev/vx/rdmp directory. The vxdiskunsetup command operates by removing the public and private regions that were created by the last invocation of vxdisksetup on the specified disks. After this operation, those disks are converted from the online to the error state state (as displayed by vxdisk list). The /etc/default/vxdisk file can be used to set the default values of the format and privlen attributes for the vxdisk and vxdisksetup com- mands. Values in this file override inbuilt values, and may themselves be overridden by values specified on the command line. For details, see the vxdisk(1M) manual page. Note: When vxdisksetup is executed on an HP IPF (IA64) system, the target disk is either configured or deconfigured as an EFI partitioned disk. The action that is taken depends on whether the -B option is specified, and whether the disk is already formatted as an EFI parti- tioned disk: o If the -B option is specified, and the disk is not already formatted as an EFI disk, the idisk(1M) utility is called to format the disk as an EFI partitioned disk. The partitioning creates an EFI header in the first 1K block, a 100MB partition (or slice) 1, and partition 2 (the HP-UX partition) on the remainder of the disk. If the vxbootsetup(1M) command is subsequently used to configure the disk as a boot disk, partition 1 is populated with an EFI file system, which contains the boot programs that are needed by an HP IPF system, and the HP-UX partition (partition 2) is set up as a logical simple VxVM disk with the same layout as a non-EFI disk. When vxdisksetup has completed setting up an EFI disk, the resulting disk must be addressed using the s2 suffix to select the logical sim- ple VxVM disk. o If the -B option is not specified and the target disk is currently formatted as an EFI partitioned disk, any EFI formatting is destroyed, and the disk is initialized as a non-EFI partitioned disk. OPTIONS
-B Initializes the Veritas Volume Manager private region to begin at block number 2144. This block is designated as the private region offset for a Veritas Volume Manager root disk. Without this option, the private region is initialized to start at the default block number 128. Note: This option is not supported for cdsdisk format disks. -C vxdiskunsetup usually does not operate on disks that appear to be imported by some other host (for example, a host that shares access to the disk). In this case, the -C option can be specified to force de-configuration of the disk, effectively removing the host locks that were detected by vxdiskunsetup. -f Forces a disk to be initialized even if it is a member of a deported disk group. -F By default, the vxdiskunsetup command only operates on online disks. It does not operate on disks that are imported or offline. This option forces an unsetup operation to be performed on such disks. -i Writes a disk header to the disk, initializes the private region of the disk and makes the disk directly usable (as a new disk in a disk group, for example). Note: A disk that is a member of an imported disk group cannot be initialized. The command also fails if the disk is a member of a deported disk group. The -f option can be used to override the latter restriction. ATTRIBUTES
You can specify attributes to affect the layout strategy used by vxdisksetup. CAUTION: Take great care when using these attributes as they can render a disk unusable by VxVM. config Sets up kernel logs or configuration databases on the disk. This attribute has the opposite effect to the noconfig attribute. This is the default behavior if the -i option is specified. Otherwise, the attribute is ignored. noconfig Prevents setting up kernel logs or configuration databases on the disk. The size of the default private region is set to 160 blocks, which is the minimum allowed private region size. noconfig is ignored unless the -i option is specified. noreserve Do not reserve space for conversion to other formats such as cdsdisk. privlen=length Specifies the length of the private region of the disk. The default size of this area is 32MB. The maximum possible size of the private region is 524288 blocks. For cdsdisk format disks, privlen is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. privoffset=offset Indicates the sector offset of the private region on the disk. The default value for the private region offset is block number 128 for non-boot disks and block number 2144 for boot disks. For cdsdisk format disks, privoffset is silently rounded up to the nearest multiple of 8KB that is larger than or equal to 128KB if it is not already a multiple of 8KB or if its value is less than 128KB. publen=length Specifies the length of the public region of the disk. This defaults to the size of the disk minus the private area on the disk. For cdsdisk format disks, publen is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. puboffset=offset Sets the offset on the disk where the public region starts. By default, this is past the end of the private region. For the hpdisk format, 128 blocks of disk space are reserved at the end of the private region unless this is overridden by the value of puboffset or the -B option is specified. The reserved space allows for later conversion to the cdsdisk format. For cdsdisk format disks, puboffset is silently rounded up to the nearest multiple of 8KB if it is not already a multiple of 8KB. EXAMPLES
To initialize a disk for regular use, enter: /etc/vx/bin/vxdisksetup -i c2t1d0 To initialize a disk for normal use, but set the private region size to 1MB instead of the default size of 32MB, enter: /etc/vx/bin/vxdisksetup -i c2t1d0 privlen=1m Force deconfiguration of a VxVM-initialized disk, c0f4d0: /etc/vx/bin/vxdiskunsetup -C c0t4d0 NOTES
The default private region size increased from 512KB to 1MB in release 3.2, and from 1MB to 32MB in release 5.0. FILES
/etc/default/vxdisk Defaults file used by the vxdisk and vxdisksetup utilities. SEE ALSO
vxcdsconvert(1M), vxdisk(1M), vxdiskadd(1M), vxintro(1M) VxVM 5.0.31.1 24 Mar 2008 vxdisksetup(1M)
All times are GMT -4. The time now is 12:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy