SAM-QFS - How to set partial release file size on an existing filesystem
Last updated on MAY 30, 2018
Applies to:Sun QFS and Storage Archive Manager (SAM) - Version 4.0 and later
Information in this document applies to any platform.
Customer sites may begin running out of online disk space, and may want to configure partial release on an existing file system.
Releasing and staging are complementary processes. Files can be completely released from online disk cache after they are archived, or a site can specify that the beginning of a file (the stub) remain in disk cache while the remainder of the file is released. Partially releasing a file provides immediate access to data in the file stub without requiring that the file be staged. You can specify both the default partial release size and the maximum size of the stub to remain online when a file system is mounted.
From the release man page, the default partial file size is 8kb and the maximum is 16kb:
By default, the minimum partial_size is 8
kilobytes, and the maximum partial_size is 16
kilobytes or whatever the -o maxpartial=maxpartial
setting is for this file system as specified on
the mount(1M) command. For more information on
the mount(1M) command, see the mount_samfs(1M) man
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms