Duncan posted on Sun, 19 Oct 2014 05:37:36 +0000 as excerpted:
> Russell Coker posted on Sun, 19 Oct 2014 10:41:41 +1100 as excerpted:
>
>> # find . -name "*546" -exec rm "{}" \;
>> rm: cannot remove `./1412233213.M638209P10546': No such file or
>> directory
>
> Going with the non-printable-character theory, what happens if you
> expand that *546 find one character at a time? Does *0546 work? *10546?
> etc.
>
> When you find a boundary where it goes from working to not-working, what
> happens if you stick a wildcard in that boundary? Assuming *0546
> doesn't work, for instance, thus creating a boundary between the 0 and
> the 5, what about *0*546 or *0?546?
FWIW, I just had something similar happen here, except ls could see the
files and tell me what happened, tho for a moment I was wondering... In
my case it was a couple symlinks, dead because the partition they pointed
into wasn't mounted. But with this thread fresh in my mind, of course it
was the first thing to come to mind...
Another idea for potentially figuring out what's going on...
If you have tab-completion active, what sort of auto-completes does it
offer with for instance ls 141<tab> ? If necessary, again you can try
expanding one character at a time, except of course from the left here
instead of from the right as above.
For things like colons, I know bash-completion here fills in \: in place
of simply colon. I just tested what it'd do with a backspace char
embedded in a filename, and tab-completion substitutes ^H (while ls
substitutes ? ).
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
