First step is to show the installation (from the O/S perspective) of the disk. This assumes that I have already installed it physically and have set it to a non-conflicting SCSI ID number, which I have.
# /sbin/diskadd 1 UX:diskadd: INFO: You have invoked the System V disk management (s5dm) diskadd utility. The purpose of this utility is to set up additional disk drives. This utility can destroy the existing data on the disk. Do you wish to continue? (Type y for yes or n for no followed by ENTER): y The recommended default partitioning for your disk is: a 100% "UNIX System" partition. To select this, please type "y". To partition your disk differently, type "n" and the "fdisk" program will let you select other partitions. y Surface analysis of your disk is recommended but not required. Do you wish to skip surface analysis? (y/n) n Checking for bad sectors in the UNIX System partition... Verify (UNIX partition only) /dev/rdsk/c0b0t1d0s0: Begin Verify (No more than 280 minutes) You will now be queried on the setup of your disk.After you have determined which slices will be created, you will be queried to designate the sizes of the various slices. How many slices/filesystems do you want created on the disk (1 - 13)? 1 Please enter the absolute pathname (e.g., /home3) for slice/filesystem 1 (1 - 32 chars)? /export/comet Enter the filesystem type for this slice (vxfs,ufs,s5,sfs), type 'na' if no filesystem is needed, or press <ENTER> to use the default (vxfs): Specify the block size from the the following list (1024, 2048, 4096, 8192), or press <ENTER> to use the first one: 2048 Should /export/comet be automatically mounted during a reboot? Type "no" to override auto-mount or press <ENTER> to enable the option: You will now specify the size in cylinders of each slice. (One megabyte of disk space is approximately 1 cylinders.) There are now 4094 cylinders available on your disk. The filesystem type you have chosen is limited to 1048576 cylinders. How many cylinders would you like for /export/comet (0 - 4094)? Press <ENTER> for 0 cylinders: 2 Notice: The selections you have made will leave 4092 cylinders unused. You have specified the following disk configuration: A /export/comet filesystem with 2 cylinders (2.0 MB) Is this allocation acceptable to you (y/n)? y Filesystems will now be created on the needed slices Creating the /export/comet filesystem on /dev/rdsk/c0b0t1d0s1 Allocated approximately 240 inodes for this file system. Specify a new value or press <ENTER> to use the default: UX:diskadd: INFO: Diskadd for Disk Drive 2 DONE at Mon Aug 7 19:53:30 EDT 2000 #
Now we must install the Veritas Volume Manager, since this will be my new storage server, it makes more sense to use a volume manager. This way I can add/remove/chage filesystems on the fly with no user interruption. Here is the output of the installation :
Volume Manager Installation
Menu: VolumeManager/Install
The Volume Manager names disks on your system using the controller
and disk number of the disk, substituting them into the following
pattern:
c<controller>b<bus>t<target>d<disk>
Some examples would be:
c0b0t0d0 - first controller, bus 0, first target, first disk
c1b0t0d0 - second controller, bus 0, first target, first disk
c1b0t1d0 - second controller, bus 0, second target, first disk
The Volume Manager has detected the following controllers on your system:
c0:
Hit RETURN to continue.
--
Volume Manager Installation
Menu: VolumeManager/Install
You will now be asked if you wish to use Quick Installation or
Custom Installation. Custom Installation allows you to select how
the Volume Manager will handle the installation of each disk
attached to your system.
Quick Installation examines each disk attached to your system and
attempts to create volumes to cover all disk partitions that might
be used for file systems or for other similar purposes.
If you do not wish to use some disks with the Volume Manager, or if
you wish to reinitialize some disks, use the Custom Installation
option Otherwise, we suggest that you use the Quick Installation
option.
Hit RETURN to continue.
---
Volume Manager Installation Options
Menu: VolumeManager/Install
1 Quick Installation
2 Custom Installation
? Display help about menu
?? Display help about the menuing system
q Exit from menus
Select an operation to perform: 2
---
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom
The c0b0t0d0 disk is your Boot Disk. You can not add it as a new
disk. If you encapsulate it, you will make your root filesystem
and other system areas on the Boot Disk into volumes. This is
required if you wish to mirror your root filesystem or system
swap area.
Encapsulate Boot Disk [y,n,q,?] (default: n) n
---
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom/c0
Generating list of attached disks on c0....
<excluding root disk >
The Volume Manager has detected the following disks on controller c0:
c0b0t1d0
Hit RETURN to continue.
---
Installation options for controller c0
Menu: VolumeManager/Install/Custom/c0
1 Install all disks as pre-existing disks. (encapsulate)
2 Install all disks as new disks. (discards data on disks!)
3 Install one disk at a time.
4 Leave these disks alone.
? Display help about menu
?? Display help about the menuing system
q Exit from menus
Select an operation to perform: 3
---
Installation options for disk c0b0t1d0
Menu: VolumeManager/Install/Custom/c0/c0b0t1d0
1 Install as a pre-existing disk. (encapsulate)
2 Install as a new disk. (discards data on disk!)
3 Leave this disk alone.
? Display help about menu
?? Display help about the menuing system
q Exit from menus
Select an operation to perform: 1
Enter disk name for c0b0t1d0 [< name > ,q,?] (default: disk01)
The c0b0t1d0 disk appears to be empty. Adding as a new disk.
Perform surface analysis (highly recommended)
[y,n,q,?] (default: y)
Hit RETURN to continue.
----
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom
The following is a summary of your choices.
c0b0t1d0 New Disk
Is this correct [y,n,q,?] (default: y) y
The Volume Manager is now reconfiguring (partition phase)...
Volume Manager: Partitioning c0b0t1d0 as a new disk.
The Volume Manager is now reconfiguring (initialization phase)...
Volume Manager: Adding disk01 (c0b0t1d0) as a new disk.
The Volume Daemon has been enabled for transactions.
The system now must be shut down and rebooted in order to continue
the reconfiguration.
Shutdown and reboot now [y,n,q,?] (default: n)
y
Next, the addition/creation of a new volume for use as a filesystem :
# vxassist -g rootdg -U fsgen make comet 1024000k
# mkfs -F vxfs -o C /dev/vx/rdsk/rootdg/comet 2048000
Mkfs: make vxfs file system?
(DEL if wrong)
version 4 layout
2048000 sectors, 1024000 blocks of size 1024, log size 256 blocks
65536 inodes, largefiles not supported
1024000 data blocks, 1022656 free data blocks
1 allocation units of 32768 blocks, 32768 data blocks
last allocation unit has 8192 data blocks
# mount -F vxfs -o mincache=closesync /dev/vx/dsk/rootdg/comet /export/comet
# vxinfo -U fsgen -g rootdg comet
# fsadm -b 2048000 -r /dev/vx/rdsk/rootdg/comet
Finally, configure in NFS so that it can be used by comet.
#!/sbin/sh # Copyright (c) 1998 The Santa Cruz Operation, Inc.. All Rights Reserved. # # THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF THE # SANTA CRUZ OPERATION INC. # # The copyright notice above does not evidence any actual or intended # publication of such source code. # copyright "%c%" #ident "@(#)initpkg:common/cmd/initpkg/rstab.sh 1.1.10.3" #ident "$Header: rstab.sh 1.2 91/04/26 $" # place share(1M) commands here for automatic execution # on entering init state 3. # # share [-F fstype] [ -o options] [-d ""] # .e.g, # share -F nfs -d "/var/news" /var/news share -F nfs -d "comet" /export/comet
# shareall
# dfshares castor
RESOURCE SERVER ACCESS TRANSPORT
castor:/export/comet castor - -
#
# /etc/init.d/nfs start