Setup guide

rmmod celerityfc
modprobe celerityfc
NOTE Depending on the storage you are running, your system might not use all of the drivers listed. If your
system does not use a driver listed, the commands to unload or reload the drivers will fail. You can ignore
these failures. They just indicate that the driver is not required by your system.
3 Reload the Stone and Wire driver: /etc/init.d/stone+wire reload. Your filesystem should now be
mounted.
Verifying Disk Usage
You cannot write to storage partitions that are completely full.
To see if the filesystem is full, run /usr/discreet/sw/sw_df.
If your filesystem is full or almost full, consider deleting or archiving older material from clip libraries to
free disk space. VTR archiving in Creative Finishing applications requires free space on the framestore to
generate slates, test patterns, headers, and audio encoding. You can also clear the Undo Buffer to free up
space.
Clearing the Undo Buffer
The Undo Buffer takes up space on your filesystem. Consider clearing it if your filesystem is full or almost
full to free disk space.
WARNING Clearing the Undo Buffer cancels any undoable operation. Consider what operations might be stored
in the Undo Buffer before you clear it.
To clear the Undo Buffer:
1 Open your Creative Finishing application, and go into the Preferences menu.
2 Click Clear Buffer in the Undo section.
Solving a Framestore ID Mismatch
The framestore ID must match the filesystem ID for the workstation to mount your filesystem.
If the IDs do not match, you must change your framestore ID to ensure that all hosts on your Wire network
have a unique ID.
1 Open a terminal as root, and run cat /usr/discreet/sw/cfg/sw_storage.cfg. The output of the
command includes the [Framestore] section, which lists the framestore ID.
2 Open /usr/discreet/sw/cfg/sw_framestore_map in a text editor. The sw_framestore_map file includes
a section similar to the following:
[FRAMESTORES]
FRAMESTORE=london HADDR=172.16.129.32 ID=32
The Framestore ID value in the sw_framestore_map file must match the Filesystem ID value listed in
the sw_storage.cfg file.
NOTE If the framestore ID in the sw_storage.cfg file is not the same as the one in the sw_framestore_map
file, the ID listed in sw_storage.cfg has priority.
3 Change the Framestore ID value in the sw_framestore_map file to match the Filesystem ID listed in
the sw_storage.cfg file.
Software configuration | 43