DUPLICATE INODES

[jsharpe]

I have a dba who is having a problem. As he moves files he is encountering duplicate inodes, thus the file cannot be moved. Copying the file gives the new file a inode number of course, but the old number remains. This is usually not a problem because if I move the file to a hold area (to keep the inode) and then cp /dev/null to the moved file to empty it out (saving space, his files are large.) HOWEVER (as always) the inode numbers reappear, but they seem to have shifted to different files. Should an inode always remain with its created file (I thought so) and I thought that they are unique. Anyway, what causes this problem of duplicates in the first place?

I am using 4.0f. is this a reported bug or just my lack of understanding?

 

[dblair]

Is the database using the datafile being copied shutdown??

Regards.

DSB

 

[jsharpe]

yes, the database is copied to a hold area so it can be compressed before writing to tape.