Skip to content

Instantly share code, notes, and snippets.

@rjmoggach
Last active January 31, 2018 18:06
Show Gist options
  • Save rjmoggach/47fa50056f7202549717166e80e85cd6 to your computer and use it in GitHub Desktop.
Save rjmoggach/47fa50056f7202549717166e80e85cd6 to your computer and use it in GitHub Desktop.
Configuring A New Framestore for Autodesk Flame

Initial Checks

After Red Hat Installation is complete, login to your new installation.

Default Autodesk Login

User: root Pass: password

1) Check /etc/fstab to verify whether or not StorageMedia entry has been added.

In Terminal:

nano /etc/fstab

2) /etc/fstab should include the following at the bottom of your list of entries:

# KEEP THIS LINE FOR CDROM — from ADSK Redhat DVD
/dev/cdrom      /mnt/cdrom        auto    pamconsole,exec,noauto,managed 0 0
/dev/vg00/lvol1   /mnt/StorageMedia    xfs   rw,noatime,inode64
  • Logical Volume: /dev/vg00/lvol1
  • Mount Point: /mnt/StorageMedia
  • Filesystem: xfs
  • Option Flags: rw,noatime,inode64

If these options are present after re-installing your Storage Array, storage config is complete.

If you are building a new framestore from scratch, complete the following steps.

Quick Guide to Framestore Volume Creation

Devices:

/sda /sdb /sdc

Become Partions:

/sda1 /sdb1 /sdc1

Are Combined Into a Physical Volume:

lvm2 (note: lvm1 is often a part of your OS Boot Disk)

And Become a Volume Group:

vg00

Which Then has a new Logical Volume created on it, usually called:

lvol1

Configure New Framestore Volume from scratch

1) List Available Disks

In Terminal:

fdisk -l (full output)

OR

fdisk -l | grep dev (output sorted by device)

2) Determine the device name of your RAID array:

i.e. /dev/sdb/ /dev/sdc/ /dev/sdd/ etc.

Assuming your RAID array is /dev/sdb/

3) Use ‘Parted’ command line utility to partition your array.

  • Repeat for every array you have connected.
  • You should see some brief disk activity as each command is executed.

In Terminal:

/sbin/parted -s -- /dev/sdb mklabel gpt mkpart primary 0 -1

Once partitioned your array name will now be /dev/sdb1

4) Convert your array(s) into physical volumes.

In Terminal:

pvcreate /dev/sdb1

Add additional partitions if you have multiple arrays to convert, for example:

In Terminal:

pvcreate /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1

Note: Use pvremove to delete a physical volume created by mistake.

5) Verify your physical volumes were created correctly:

In Terminal:

pvscan -v

6) Create a Volume Group vg00 from your Physical Volume(s):

In Terminal:

Single Volume...

vgcreate vg00 /dev/sdb1

Multiple Volumes...

vgcreate vg00 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1

7) Verify vg00 was created and find the Free PE / Size Field.

In Terminal:

vgdisplay -v

8) Get the “Free PE” Value indicated in the output of the vgdisplay command.

Example:

Free PE / Size 228671 / 893.25 GB (Dual 480GB SSD Array)

Note: Use vgremove to delete volume groups created by mistake.

  1. Create a new Logical Volume ‘lvol1’ on your Volume Group ‘vg00’ using Free PE value.

EXAMPLE: If using one 30TB volume (12-Bay RAID Array)

In Terminal:

lvcreate -l 7868927 -I32 -n lvol1 vg00

Where:

lvcreate = create logical volume
-l = create logical volume that uses the entire volume group
7868927 = PE Value (array size) obtained from using the vgdisplay -v command earlier
-I32 = The stripe size in Kb (using capital ‘I’, NOT ‘L’)
-n = flag for name of new volume
lvol1 = new volume name
vg00 = the volume group the new volume is being carved out of

If successful you will see output stating “lvol1” created.

Format New Framestore Volume With XFS Filesystem

1) Calculate the optimal agsize for your volume using mkfs.xfs command.

In Terminal:

mkfs.xfs -d agcount=128 -f /dev/vg00/lvol1

Note the agsize value. In our 30TB array example, agsize = 62951416

If BOTH sunit=0 blks, AND swidth=0 blks, multiply agsize by 4096 as described below to obtain a final agsize value.

62951416 blks x 4096 = new agsize = 257848999936

NOTE: if sunit=0 blks, AND swidth=0 blks DO NOT equal 0, see the following article under ‘Creating the XFS Filesystem on the Logical Volume’ for more details: https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/Configuring-a-Logical-Volume-for-Flame-Media-Storage-Step-3.html

2) Use mkfs.xfs command with your new agsize value to format your framestore volume.

In Terminal:

mkfs.xfs -d agsize= <new agsize> -f /dev/vg00/lvol1

Using our 30TB Array Example….

mkfs.xfs -d agsize= 257848999936 -f /dev/vg00/lvol1

The XFS filesystem is created on the storage array.

Mount New Framestore Volume to Designated Mount Point

1) Create the directory that will server as a mount point called StorageMedia

In Terminal:

mkdir /mnt/StorageMedia

2) Mount the XFS Filesytem on your framestore to your new mount point.

In Terminal:

mount -av -t xfs -o rw,noatime,inode64 /dev/vg00/lvol1 /mnt/StorageMedia

3) Add the following entry to /etc/fstab so automatically mount the volume at startup.

In Terminal:

Open fstab in Nano…

nano /etc/fstab

Add this entry to the below all other entries in the fstab file…

/dev/vg00/lvol1 /mnt/StorageMedia rw,noatime,inode64

4) Set Permissions for StorageMedia

In Terminal:

mkdir -p /mnt/StorageMedia/flame01/p7
chown -R root:users /mnt/StorageMedia/flame01/p7
chmod -R 777 /mnt/StorageMedia/flame01/p7

3) Press Ctrl+X, to Exit nano.

4) Press Y, then Enter to commit changes to /etc/fstab

5) Reboot and verify /mnt/StorageMedia is mounted after start-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment