FilePool policies and hardlink behavior

Question

Hi,

The context: two files is related to the same inode (hardlink) on primary server, and one of them is matching a file pool policy (going to be smartlinked), not the other one. What's the behavior when file pool policy is applied ? What the behavior with inode and data blocks (stay on primary server, duplication ...) ?

Thanks in advance,

Fabrice

Peter_Sero · Accepted Answer

Fabrice:

with hardlinked files in different directories, it is in fact not predictable or contollable which file pool policies applies, or in which order matching policies would apply. So your concern is a very valid one.

As file pool policies are primarily a SmartPools construct, a good reference is this whitepaper: https://www.delltechnologies.com/resources/en-us/asset/white-papers/products/storage/h8321-wp-smartpools-storage-tiering.pdf

Under SmartPools Best Practices, on page 31, we find:

Avoid creating hardlinks to files which will cause the file to match different file pool policies

Makes sense?

-- Peter

DELL-Sam L · Answer

Hello Fabrice59, Which version of OE or Onefs are you running on your Isilon system?

Fabrice59 · Answer

Hi Sam, The version is 8.2.2.0 Fabrice

DELL-Sam L · Answer

Hello Fabrice, Here is the link to the administrator guide and if you look on page 313-324 explains more about the policies & how they will function. https://dell.to/3cmDufN

Fabrice59 · Answer

Hi Sam, Thank you for the document linked. I'm not able to find the answer about my specific question about hardlinks, but I've learned more about cloud file policies. Fabrice

Fabrice59 · Answer

Thank you for your answer. It makes sense !

Isilon

FilePool policies and hardlink behavior

Was this post helpful?

Register Now! for Secure Secrets with Kubernetes & DevSecOps - and grab a lab!

Dell Technologies at SpiceWorld 2022