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: [URL]  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
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 
FilePool policies and hardlink behavior