You have to copy the file to a new name _on Lustre_ to allocate a new inode (new storage) on Lustre, and then "mv" it to replace the original file.
Mv across filesystems is basically a cp, which will overwrite the destination file, not replace the inode. Kevin On Jan 20, 2009, at 3:55 AM, Heiko Schroeter <[email protected] > wrote: > Hm, i do got it that one has to 'move' the file back. But ... > >>> Copy the data on a client to a temp storage outside (does it has >>> to be >>> outside?) the lustre system and 'move' them back into lustre to >>> create >>> new inodes entries on the MDS. >> >> Actually, it should NOT be on storage outside Lustre in this case. >> > > why staying inside lustre (in this case) ? (Bandwidth ?, > Performance ?...) > > What would be a different case/scenario that one has to go 'out' of > lustre ? > > Thanks and Regards > Heiko > _______________________________________________ > Lustre-discuss mailing list > [email protected] > http://lists.lustre.org/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
