Red Hat Bugzilla – Bug 150112
Can't copy from Netapp .snapshot directory to normal filesystem
Last modified: 2007-11-30 17:07:06 EST
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.
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
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):
Occurs whenever the inodes match.
Steps to Reproduce:
cp /db01/.snapshot/hourly.0/oradata/spsrepx/sps_idx1.dbf /db01/oradata/spsrepx/
cp: `/db01/.snapshot/hourly.0/oradata/spsrepx/sps_idx1.dbf' and
`/db01/oradata/spsrepx/sps_idx1.dbf' are the same file
File should have copied.
Works under Solaris 8/9
We also tried using the -f and --remove-destination cp options.
What filesystem provides the snapshot?
Oh, it's a Netapp. Sorry, missed that.
If there is any urgency for this, you would be best off going through support:
or call 800-REDHAT1
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.