On Sun, 19 Oct 2014, Robert White <rwhite@xxxxxxxxx> wrote:
> On 10/17/2014 08:54 PM, Russell Coker wrote:
> > # find . -name "*546"
> > ./1412233213.M638209P10546
> > # ls -l ./1412233213.M638209P10546
> > ls: cannot access ./1412233213.M638209P10546: No such file or directory
> >
> > Any suggestions?
>
> Does "ls -l *546" show the file to exist? e.g. what happens if you use
> the exact same wildcard in the ls command as you used in the find?
# ls -l *546
ls: cannot access 1412233213.M638209P10546: No such file or directory
That gives the same result as find, the shell matches the file name but then
ls can't view it.
lstat64("1412233213.M638209P10546", 0x9fab0c8) = -1 ENOENT (No such file or
directory)
>From strace, the lstat64 system call fails.
> It is possible (and back in the day it was quite common) for files to be
> created with non-renderable nonsense in the name. for instance if the
> first four characters of the name were "13^H4" (where ^H is the single
> backspace character) the file wold look like it was named 14* but it
> would be listed by ls using "13*". If the file name is "damaged", which
> is usually a failing in the program that created the file, then it can
> be "hidden in plain sight".
If that's the case then it's still a kernel bug somewhere. Maildrop and
Dovecot don't create files with any unusual characters in the names.
> Note that this sort of name is hidden from the copy-paste done in the
> terminal window because the binary nonsense is just not in the output
> any more by the time you select it with the mouse.
>
> It doesn't have to be a backspace, BTW, it can be any character that the
> terminal window will not render.
>
> If things get really ugly you may need to remove the file using
>
> find . -name "*546" -exec rm "{}" \;
# find . -name "*546" -exec rm "{}" \;
rm: cannot remove `./1412233213.M638209P10546': No such file or directory
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
