File system creation procedure

  1. Create volume groups

    Two volume groups, pdvg and segvg, are created to contain the /var/pd and /var/psf/segments file systems. Creating separate volume groups helps spread I/O across multiple actuators, which can improve performance. The pdvg volume group contains the important InfoPrint Manager database objects and should be backed up at regular intervals. The segvg volume group contains the segmented print files, and can be considered to be transient data. If you have multiple hard drives available for use with segvg, striping across these disks provides multiple heads accessing the data for faster I/O performance, which is useful when driving high speed/high resolution printers.

    Note: A 128 MB Physical Partition size is recommended for 73.4GB drives. If your server has larger or smaller drives, you should adjust this value proportionally.
    1. Create pdvg volume group: 
      smitty mkvg
		VOLUME GROUP name								[pdvg]
		Physical partition SIZE in megabytes	[128]
		PHYSICAL VOLUME names						[hdisk1]
		Activate volume group AUTOMATICALLY	[yes]
	 	 at system restart?
		Volume Group MAJOR NUMBER					[]
		Create VG Concurrent Capable?			[no]
		Auto-varyon in Concurrent Mode			[no]
		LTG Size in kbytes							[256]
      Commandline:
      mkvg -f -y'pdvg' -s'128' hdisk1
    2. Create segvg volume group
      smitty mkvg
		VOLUME GROUP name									[segvg]
		Physical partition SIZE in megabytes		[128]
		PHYSICAL VOLUME names							[hdisk2 hdisk3]
		Activate volume group AUTOMATICALLY		[yes]
		 at system restart?
		Volume Group MAJOR NUMBER						[]
		Create VG concurrent capable?				[no]
		Auto-varyon in Concurrent Mode				[no]
		LTG size in kbytes								[128]
      Commandline:
      mkvg -f -y'segvg' -s'128' hdisk2 hdisk3
      Note: You need to divide the drives your server has available between your Volume Groups.

  2. Create logical volumes

    The logical volumes are created to contain the file systems. Since /var/psf/segments is a third level directory, /var/psf must be created first, so that it is mounted before /var/psf/segments. If for some reason you create them in the wrong order, you will need to edit /etc/filesystems to correct the order. Try to avoid this.

    To calculate the number of LOGICAL PARTITIONS, issue lsvg pdvg to get the number of free physical partitions available on the hard drive. Use a number roughly 30 less than the number of free physical partitions to fill the entire drive with the volume group.

    1. Create lvpd logical volume
      smitty mklv
Volume Group name											[pdvg]
		
		Logical volume NAME								[lvpd]
		VOLUME GROUP name									[pdvg]
		Number of LOGICAL PARTITIONS					[512]
		PHYSICAL VOLUME names							[hdisk1]
		Logical volume TYPE								[jfs]
		POSITION on physical volume					middle
		RANGE of physical volumes						minimum
		MAXIMUM NUMBER of PHYSICAL VOLUMES			1
			to use for allocation
		Number of COPIES of each logical			1 
			partition
		Mirror Write Consistency?						active
		Allocate each logical partition copy		yes
			on a separate physical volume
		RELOCATE the logical volume during 		yes
			reorganization	
		Logical Volume label							/var/pd
		MAXIMUM NUMBER of LOGICAL PARTITIONS		512
		Enable BAD BLOCK relocation					yes
		SCHEDULING POLICY for reading/writing		parallel
			logical partion copies
		Enable WRITE VERIFY?							no
		File containing ALLOCATION MAP				[]
		Stripe Size											[Not Striped]
      Commandline:
      mklv -y'lvpd' -t'jfs' -u'1' -L'/var/pd' pdvg 512 hdisk1
    2. Create lv01 logical volume
      smitty mklv
Volume Group NAME 			[rootvg]
	
		Logical Volume NAME 							[lv01]
		VOLUME GROUP name									[rootvg]
		Number of LOGICAL PARTITIONS					[512]
		PHYSICAL VOLUME names							[hdisk0]
		Logical volume TYPE								[jfs]
		POSITION on physical volume					middle
		RANGE of physical volumes						minimum
		MAXIMUM NUMBER of PHYSICAL VOLUMES			1
			to use for allocation
		Number of COPIES of each logical 			1
			partition		
		Mirror Write Consistency?						active
		Allocate each logical partition copy		yes
			on a separate physical volume
		Relocate the logical partition during 	yes
			reorganization	
		Logical Volume label							/var/psf
		MAXIMUM NUMBER of LOGICAL PARTITIONS		512
		Enable BAD BLOCK relocation					yes
		SCHEDULING POLICY for reading/writing		parallel
			logical partion copies
		Enable WRITE VERIFY?							no
		File containing ALLOCATION MAP				[]
		Stripe Size											[Not Striped]
      Commandline
      mklv -y'lv01' -t'jfs' -u'1' -L'/var/psf/' rootvg 512 hdisk0
    3. Create lvpsfs logical volume
      smitty mklv
Volume Group name				[segvg]
	
		Logical volume NAME								[seglv]
		VOLUME GROUP name									[segvg]
		Number of LOGICAL PARTITIONS					[512]
		PHYSICAL VOLUME names							[hdisk2 hdisk3]
		Logical volume TYPE								[jfs]
		POSITION on physical volume					middle
		RANGE of physical volumes						minimum
		MAXIMUM NUMBER of PHYSICAL VOLUMES			2
			to use for allocation
		Number of COPIES of each logical			1 
			partition		
		Mirror Write Consistency?						active
		Allocate each logical partition copy		yes
			on a separate physical volume
		RELOCATE the logical volume during 		yes
			reorganization	
		Logical Volume label							/var/psf/segments
		MAXIMUM NUMBER of LOGICAL PARTITIONS		512
		Enable BAD BLOCK relocation					yes
		SCHEDULING POLICY for reading/writing		parallel
			logical partion copies
		Enable WRITE VERIFY?							no
		File containing ALLOCATION MAP				[]
		Stripe Size											[Not Striped]
      Note: To stripe /var/psf/segments, use 128K for the Stripe Size.
      Commandline:
      mklv -y'lvpsfs' -t'jfs' -u'2' -L'/var/psf/segments' 
segvg 512 hdisk2 hdisk3
  3. Create file systems in logical volumes

    Three file systems are created for InfoPrint Manager to use during installation. The size of file system information would be determined by the size of the SCSI disk drives. A reasonable file system size to use is:

    18.2GB disk
    33554432
    36.4GBdisk
    67108864
    73.4GB disk
    134217728
    146.8GB disk
    268435456
    1. Create /var/pd file system
      smitty crjfslvbf 
		LOGICAL VOLUME name								lvpd
		MOUNT POINT											/var/pd
		Mount AUTOMATICALLY at System restart?	yes
		PERMISSIONS											read/write
		Mount OPTIONS										[]
		Start Disk Accounting?							no
		Number of byutes per inode					4096
		Allocation Group Size (Mbytes)				64
        Note:
      1. The crjfslvbf is used because this example assumes the creation of a large file enabled JFS system on a previously defined logical volume.
      2. The fragment size defaults to 4096.
      Commandline:
      crfs -v jfs -a bf=true -A''`locale nostr | awk -F: '{print $1}'`'' 
-p'rw'-t''`locale nostr | awk -F: '{print $1}'`'' -a nbpi='4096' 
-a ag='64'
    2. Create /var/psf file system
      smitty crjfslvstd
		LOGICAL VOLUME name								lv01
		MOUNT POINT											/var/psf
		Mount AUTOMATICALLY at system restart?	yes
		PERMISSIONS											read/write
		Mount OPTIONS										[]
		Start Disk Accounting?							no
		Fragment Size										4096
		Number of bytes per inode						4096
		Allocation Group Size (Mbytes)				8
        Note:
      1. The crjfslvstd is used because this example assumes the creation of a standard JFS system on a previously defined logical volume.
      2. It is best to set the fragment size to its highest value of 4096 bytes.
      Commandline:
      crfs -v jfs -A''`locale nostr | awk -F: '{print $1}'`'' -p'rw' 
-t''`locale nostr | awk -F: '{print $1}'`'' -a frag='4096' 
-a nbpi='4096' -a ag='8'
    3. Create /var/psf/segments file system
      smitty crjfslvbf

		LOGICAL VOLUME name								seglv
		MOUNT POINT											/var/psf/segments
		Mount AUTOMATICALLY at system restart?	yes
		PERMISSIONS											read/write
		Mount OPTIONS										[]
		Start Disk Accounting							no
		Number of bytes per inode						4096
		Allocation Group Size (Mbytes)				64
      Note: The fragment size defaults to 4096.
      Commandline:
      crfs -v jfs -a bf=true -A''`locale nostr | awk -F: '{print $1}'`'' 
-p'rw' -t''`locale nostr | awk -F: '{print $1}'`'' -a nbpi='4096' 
-a ag='64'

  4. Mount the file systems
    1. Mount /dev/lvpd
      Smitty mountfs
		FILE SYSTEM name											/dev/lvpd
		DIRECTORY over which to mount						/var/pd
		TYPE of file system										jfs
		FORCE the mount?											no
		REMOTE NODE containing the file system				[]
			to mount?
		Mount as a REMOVABLE file system						no
		Mount as a READ-ONLY system?							no
		Disallow DEVICE access via this mount?			no
		Disallow execution of SUID and sgid programs	no
			in this file system?
      Commandline:
      mount -v'jfs' /dev/lvpd /var/pd
    2. Mount /dev/lv01
      Smitty mountfs
		FILE SYSTEM name											/dev/lv01
		DIRECTORY over which to mount						/var/psf
		TYPE of file system										jfs
		FORCE the mount?											no
		REMOTE NODE containing the file system				[]
			to mount?
		Mount as a REMOVABLE file system						no
		Mount as a READ-ONLY system?							no
		Disallow DEVICE access via this mount?			no
		Disallow execution of SUID and sgid programs	no
			in this file system?
      Commandline:
      mount -v'jfs' /dev/lv01 /var/psf
    3. Mount /dev/lvpsfs

      First, create the directory for the segments: 

      cd /var/psf
mkdir segments

      Note: Make sure that the group is printq and permissions are 744.

      Next: 

      Smitty mountfs
		FILE SYSTEM name											/dev/lvpsfs
		DIRECTORY over which to mount						/var/psf/segments
		TYPE of file system										jfs
		FORCE the mount?											no
		REMOTE NODE containing the file system				[]
			to mount?
		Mount as a REMOVABLE file system						no
		Mount as a READ-ONLY system?							no
		Disallow DEVICE access via this mount?			no
		Disallow execution of SUID and sgid programs	no
			in this file system?
      Commandline:
      mount -v'jfs' /dev/lvpsfs /var/psf/segments

    Note: To find the command line equivalent of any command issued through smitty, use the F6 key.
Parent topic: Manual InfoPrint Manager file system allocation