NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Home share sub-folder copied itself, relies on copy
Firmware 6.4.2 In the last week or so, I have had a regularly used sub-folder ("Expense Reports") in my home share duplicate itself, with the copy cryptically named "EQ5GJE~Q". So I had two fold...
Are you accessing on a windows PC? If so, which version of winodws? Are you mapping the share to a drive letter?
Back in ancient times, Microsoft only supported 8 character folder names. When they fixed that, they generated a "short" file name from the longer ones for backwards compatibility. SAMBA (the SMB engine in ReadyNAS) also can generate similar names for backwards compatibility. This is called "name mangling".
It looks like you are seeing both the regular name and the mangled name for some reason on the NAS. If so, its actually just another name for the same folder - which explains why the contents disappeared from both when you deleted it.
Yes, mapping as my J:, from a Windows 7 PC.
I'm familiar with the old 8-character naming limits... from 40 years ago.
Wouldn't it have been "Expens~1" though, instead of random "EQ5GJE~Q"?
Anyway... question remains WHY am I seeing this? How do I fix it?
Thanks.
shadowIT wrote:
Wouldn't it have been "Expens~1" though, instead of random "EQ5GJE~Q"?
There are a couple of different name-mangling algorithms out there, I'm not sure which one is used by the current SAMBA.
shadowIT wrote:
Anyway... question remains WHY am I seeing this? How do I fix it?
That is the right question of course. It's unusual behavior (I haven't seen it posted here before). Hopefully someone from Netgear will comment.
There is a way to turn name-mangling off in SAMBA, but not in the admin gui or SMB-PLUS. So it would require ssh access.
Names should only get mangled if they have a Windows reserved character in the name (like a colon). I've never seen what you've described here before. If you see it again, we'd have to debug it to find out why it's happening. Either Samba debug level 10 logs, or tcpdump, or both would be necessary.
The duplicate folder is STILL there, if that gives you enough to debug.
Or do you need it to happen again to another folder?
Yes, that should be enough. Can you collect a Wireshark caputure while you browse to that folder? It'd probably need to be the first time you've browsed that folder during that boot, or else the results may be cached.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
