asked on

Broken Bar/Pipe Character cannot copy to CIFS NetApp share.

This is a tough one I am trying to solve for a month already.
I receive data from some clients and some of them come from non-windows OS. Broken pipe/bars as folders or file names. Windows shares take these characters just fine. However when trying to copy to NetApp CIFS it rejects.
Now the interesting thing...I am able to rename a file successfully on my vFiler. It took the names without issue. I then manually created a file with the broken bar and copied to vFilers without issue. It seems there are other hidden characters in the files clients sent me. I can actually delete the broken bar and then using the ASCII code (Hold ALT, then type 0166, release ALT, and the Broken Bar will be created) to create a new broken bar, and it will then copy to the NAS. I attached a rar file to have an idea.
Anyone familiar with issue?
BrokePipe.zip

ASKER CERTIFIED SOLUTION

Paul Solovyovsky

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

tiras gans

ASKER

Thanks Paul. The case with NetApp is already opened and they doing some lab analysis on this. This is rate first case for them also they say.
Interesting idea on enabling mixed mode. My environment is Windows only. No NSF shares. Only data comes from Linux.

SOLUTION

Paul Solovyovsky

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

tiras gans

ASKER

We cannot export a share for both CIFS and NFS. We can create an NFS export for our Linux VM, but it would be the only one that could access.

tiras gans

ASKER

My storage admins saying you cannot enable mixed mode in only windows environment. Just not possible. Not sure how to tackle it here. Weird.

tiras gans

ASKER

Thank you!