Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 150112 - Can't copy from Netapp .snapshot directory to normal filesystem
Can't copy from Netapp .snapshot directory to normal filesystem
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: coreutils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Pete Graner
Depends On:
  Show dependency treegraph
Reported: 2005-03-02 11:13 EST by Mark Hoover
Modified: 2007-11-30 17:07 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 15:06:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mark Hoover 2005-03-02 11:13:54 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):

How reproducible:
Occurs whenever the inodes match.

Steps to Reproduce:
cp /db01/.snapshot/hourly.0/oradata/spsrepx/sps_idx1.dbf /db01/oradata/spsrepx/
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
Comment 1 Mark Hoover 2005-03-02 11:21:20 EST
We also tried using the -f and --remove-destination cp options.
Comment 2 Tim Waugh 2005-03-07 06:26:20 EST
What filesystem provides the snapshot?
Comment 3 Tim Waugh 2005-03-07 06:26:47 EST
Oh, it's a Netapp.  Sorry, missed that.
Comment 7 Suzanne Hillman 2005-04-04 17:21:35 EDT
If there is any urgency for this, you would be best off going through support:

or call 800-REDHAT1
Comment 8 RHEL Product and Program Management 2007-10-19 15:06:46 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.