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.
Additionally, I'd say use the default print instead of the -exec rm.
Because once you find it, you might want to do other tests (doing a file
on it to find type, finding the size, possibly catting it...) to figure
out what it is and possibly how it came to get there, before ultimate
removal.
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?
... Just things I'd be trying were I to see such a thing here.
--
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
