- To: "SLUG List" <slug@xxxxxxxxxxx>
- Subject: Re: [SLUG] removing duplicate files
- From: "Amos Shapira" <amos.shapira@xxxxxxxxx>
- Date: Thu, 5 Jul 2007 00:06:15 +1000
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=eo5JkxPpqqg9r4r2gwZuthXhc0F/cyRlbOdL9N/PFOhoOXwwoHDfWmx1Nb+/nFqI96b/OAJjyQOW1RO2qWd0ZioSfAf7BVhR/oercADO/Mcg8LfxF8SXVqYO2Bmk0HheKj9WddH4BaUbCMuhRTC+PCyD1AeLlXxTnEYhRmnmvjk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=Edu33n9dLTNi0p8XFvHxSXwzSCYQf9k/dZEw6gQgFjTo9W3O+eUZMRIB88+u/EMc3MFvgnDCRFwsrylAfFjeCn8+D+n2aB5mFW9SUtr4Zit5srj8Z8zszD/GQMUzTx6mSZAimBRiH6ChRz6DeLuDHwX2I3kx5nHmjZeqgPjqvUU=
On 04/07/07, Kevin Shackleton <kevins@xxxxxxxxxxxx> wrote:
To explain more about my remove duplicate file problem . .
# rm -rv <somefile>
rm: cannot lstat `<somefile>': No such file or directory
Is "somefile" the exact file name (e.g. full path name or full path between
current working dir and the file?). If not then it indeed won't lookup the
file in the directories underneath and you need to use "find".
If the file is in your current working directory and just typing "rm
<somefile>" doesn't find it then I suspect the name you type is not the
right one - maybe there are control characters or unicode characters in the
See "man ls" for ways to ask ls to display special characters like "-b",
"-N", or "-q". If you go the "-N" way then pipe the output through "cat -v
The problem is in lstat, not rm. The problem is that it's not recursing
It's not a problem - that's the way it's supposed to happen. See "man rm".
Neither will Gnome File Browser search these directories.
The problem I suspect is that over time having copied this set of
directories several times through different file systems, including as a
share from a Windows VMWare session, the property bits of the directory
entries have been made incorrect. They are executable, as per Matthew
Hannigan's post on Monday. I can cd through the directories and they
appear to be correct in every other way except recursing through them.
How do you define "recursing through them"?
(they are mp3 data and just to be different xmms does recurse when asked
to load a directory that has subdirectories)
So it can't be a permissions problem - all processes of the same user are
equal in the eyes of the filesystem.
Any thoughts? And a command to fix the several hundred directories too
First let's decide what exactly is the problem before trying to hit it
randomly until it breaks, shall we?