On 2014/03/21, 6:52 AM, "Wojciech Turek" <wjt27@cam.ac.uk<mailto:wjt27@cam.ac.uk>> wrote:Are you using multiple MDTs? In the current 2.4/2.5/2.6 DNE implementation, rename across MDTs will return -EXDEV and cause "mv" to copy the files. In 2.6 there is an inode migration tool that will move just the inodes (though not using the normal rename() syscall since it will also change the inode number).
I am trying to move some large directories on the same lustre filesystem however I can see that instead of quick name remapping mv does copy operation. Is there a way to avoid this?
In 2.7 there will be support for link and rename of inodes across MDTs.
Cheers, Andreas
As a test I created new directory with hundreds of large files and moved it and mv works as expected. I do not understand what is different about the other directories that they can not be simply moved.
Best regards,
Wojciech
--
Wojciech Turek
Senior System Architect
<< Tomorrow (noun) A mystical land where 99% of all human productivity, motivation and achievement is stored >>
--
Andreas Dilger
Lustre Software Architect
Intel High Performance Data Division