Bug 150112

Description of problem:
Netapp solution id: ntapcs5964 

Cause of this problem: 
If a file in a snapshot has the same inode number as the corresponding file in 
the active file system, some UNIX programs may consider the two files to be 
the same although the file content is different. Typing 'ls -lai' shows that 
the file in the .snapshot and the active file system have the same inode 
number. Errors are caused by the the version of cp and it's inability to cross 
filesystems in a single mount point. 
 

Solution:  
Snapshot files carry the same permissions and inode numbers as the original 
files, keeping the integrity of the security system intact. Inodes are data 
structures that hold information (including permissions information) about 
files on the filer. There is an inode for each file and a file is uniquely 
identified by the file system on which it resides and its inode number on that 
system. 

The inode number for a file in a snapshot is the same as the inode number for 
the corresponding file in the active file system. As a result, some programs 
on UNIX clients consider the two files to be the same. For example, if you use 
the GNU diff program to compare the two files, it does not find any 
differences between them. In some cases, if you try to restore a file from a 
snapshot, you might see the following error message: 

cp:.snapshot/xxx and xxx are identical.
 

Version-Release number of selected component (if applicable):
coreutils-4.5.3-26

How reproducible:
Occurs whenever the inodes match.

Steps to Reproduce:
1. 
cp /db01/.snapshot/hourly.0/oradata/spsrepx/sps_idx1.dbf /db01/oradata/spsrepx/
sps_idx1.dbf
  
Actual results:
cp: `/db01/.snapshot/hourly.0/oradata/spsrepx/sps_idx1.dbf' and 
`/db01/oradata/spsrepx/sps_idx1.dbf' are the same file

Expected results:
File should have copied.

Additional info:
Works under Solaris 8/9