Is qtree a "file system" boundary from hard link's perspective?

Hi,

ONTAP 9.1rc1

Scenario:

volume A contains 2 qtrees: tree1 and tree2

If I create a file in qtree1, and then try to create a hard link in tree2 for the file, it will complain "Invalid cross-device link." So it seems to me a qtree is like a volume having its own file system. In other words, say in qtree1 a file has inode 11111, it's possible in qtree2 there a file also having inode 11111. Is it correct?

I know hard links should be avoided in general but unfortunately the data set i am dealing with already have alot of hard links and I need to migrate them from isilon to NetApp.

Thanks,