Your message dated Wed, 02 Sep 2009 20:46:51 -0400
with message-id <[email protected]>
and subject line Re: coreutils: cp refuses to hardlink a specific file, with a
strange error message
has caused the Debian Bug report #512831,
regarding coreutils: cp refuses to hardlink a specific file, with a strange
error message
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
512831: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512831
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: coreutils
Version: 5.97-5.3
Severity: important
Really funny things happening:
virtual:~# mount | grep /backup
/dev/sdc1 on /backup type ext3 (ro)
127.0.0.1:/backup/vz/104 on /var/lib/vz/root/104/backup type nfs
(ro,soft,nolock,port=2049,mountport=2049,noudp,tcp,addr=127.0.0.1)
virtual:~# uname -a
Linux virtual 2.6.18+openvz #1 SMP Sun Mar 23 19:15:17 CET 2008 x86_64
GNU/Linux
mount /backup -o remount,rw; cp -al /backup/vz/104/backup.0
/backup/vz/104/backup.TEST; mount /backup -o remount,ro
cp: cannot create hard link
`/backup/vz/104/backup.TEST/scratch/news/articles/fr/comp/developpement/agl/windev/63260'
to
`/backup/vz/104/backup.TEST/scratch/news/articles/fr/comp/developpement/agl/windev/63260':
No such file or directory
Yes, that file is missing on the copy.
Thus I can hardlink it by hand:
virtual:~# mount /backup -o remount,rw; cp -al
/backup/vz/104/backup.0/scratch/news/articles/fr/comp/developpement/agl/windev/63260
/backup/vz/104/backup.TEST/scratch/news/articles/fr/comp/developpement/agl/windev/63260;
mount /backup -o remount,ro
and this is reproductible *each time*. Note the bizarre error message
above (hardlinking over itself).
Do it once more:
virtual:~# mount /backup -o remount,rw; cp -al /backup/vz/104/backup.0
/backup/vz/104/backup.TEST2; mount /backup -o remount,ro
cp: cannot create hard link
`/backup/vz/104/backup.TEST2/scratch/news/articles/fr/comp/developpement/agl/windev/63260'
to
`/backup/vz/104/backup.TEST2/scratch/news/articles/fr/comp/developpement/agl/windev/63260':
No such file or directory
look at the file more carefully:
virtual:~# ls -lai
/backup/vz/104/backup.0/scratch/news/articles/fr/comp/developpement/agl/windev/63260
14354482 -rw-rw-r-- 9 news news 1877 Jan 21 11:13
/backup/vz/104/backup.0/scratch/news/articles/fr/comp/developpement/agl/windev/63260
virtual:~# lsattr
/backup/vz/104/backup.0/scratch/news/articles/fr/comp/developpement/agl/windev/63260
------------------
/backup/vz/104/backup.0/scratch/news/articles/fr/comp/developpement/agl/windev/63260
If I remove that file and start the cp -al over to a new destination,
the error disappears.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18+openvz
Locale: LANG=C, LC_CTYPE=fr_CH.ISO-8859-1 (charmap=ISO-8859-1)
Versions of packages coreutils depends on:
ii libacl1 2.2.41-1 Access control list shared library
ii libc6 2.3.6.ds1-13etch8 GNU C Library: Shared libraries
ii libselinux1 1.32-3 SELinux shared libraries
coreutils recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
The report is from a fairly old version of debian which predates the
current stable release. I can't duplicate. My best guess is that this
has to do with hardware issues or a corrupt filesystem, but I'm not
sure. If anyone can duplicate this with the current release, please
reopen.
Mike Stone
--- End Message ---
