I havne't totally narrowed this one down, but I've had two instances where I could show that files with a
"._*" filename or a filename with a singlequote in the name caused very slow performance. It all still worked, which is what I can't quite figure out.
I had a stack of directories with some "._*" files in them (they were leftover "trash" AppleDouble files that a NAS had used... when I removed them, performance jumped back to normal.
Another directory had a lot of files with a singlequote in the name... again, if I got rid of them, performance back to normal.
Sorry if this isn't enough detail, not sure who to narrow down further.
I was using:
rmdupe -r --ref
I nearly always use a --ref, and having the "bad files" in the reference directory is enough to cause the issue.
I havne't totally narrowed this one down, but I've had two instances where I could show that files with a
"._*" filename or a filename with a singlequote in the name caused very slow performance. It all still worked, which is what I can't quite figure out.
I had a stack of directories with some "._*" files in them (they were leftover "trash" AppleDouble files that a NAS had used... when I removed them, performance jumped back to normal.
Another directory had a lot of files with a singlequote in the name... again, if I got rid of them, performance back to normal.
Sorry if this isn't enough detail, not sure who to narrow down further.
I was using:
rmdupe -r --ref
I nearly always use a --ref, and having the "bad files" in the reference directory is enough to cause the issue.