Thank you for checking this.
Yes, it is kind of tricky to deal with these directories.
Especially as they do not have a 8.3 shortname that could be leveraged to at least move files and then delete these directories.
Interestingly using a current Apple device did not allow to rename the directories either.
Seems that Apple fixed that loophole in the meantime.
Just in case anyone else encounteres the same, what finally helped to get rid of the "infected" directories:
mount the SMB share on a linux box (opensuse in wsl![:)]( "Smile")
, cifs-utils installed).
Options are needed to be able to rename and also process directories with non ascii characters.
mount -t cifs -o vers=1.0,iocharset=utf8,username=<username> //server/share /mnt/mntname
then rename via normal mv "directoryname " "directoryname"
Yes, it is kind of tricky to deal with these directories.
Especially as they do not have a 8.3 shortname that could be leveraged to at least move files and then delete these directories.
Interestingly using a current Apple device did not allow to rename the directories either.
Seems that Apple fixed that loophole in the meantime.
Just in case anyone else encounteres the same, what finally helped to get rid of the "infected" directories:
mount the SMB share on a linux box (opensuse in wsl
, cifs-utils installed). Options are needed to be able to rename and also process directories with non ascii characters.
mount -t cifs -o vers=1.0,iocharset=utf8,username=<username> //server/share /mnt/mntname
then rename via normal mv "directoryname " "directoryname"
Statistics: Posted by loskexos — 28 Jan 2022, 19:38