gjw1 Absent Member.
Absent Member.
5085 views

Linux NFS clients report 'Unknown Error 526'

Server is Novell Netware 6.5 SP5 Cluster
The NFS clients are Red Hat Enterprise 3 and Solaris 8

The problem is that when a filename contains certain characters, the Linux clients return the error 'unknown error 526' if you try and list the directory contents.

Solaris clients just report the directory as being empty.

Windows clients see the directory perfectly fine.

If I copy said files off the server and onto some removable media using a Windows machine, and then take that media to the Liunux clients, I get the expected '?' where said characters are.

So although the character support is clearly missing from the NFS clients, it seems to me as though the Netware servers are causing an extra problem that stops the direcory being accessed at all from the NFS clients, and this happens on all Servers company wide.

The biggest issue is that if one of these files exists in a fiarly high level directory, it stops users seeing all subdirectories below it.

Any help is much appreciated as I am completely stumped.
Labels (1)
0 Likes
4 Replies
Marcel_Cox Absent Member.
Absent Member.

Re: Linux NFS clients report 'Unknown Error 526'

I don't know if the option also helps in the case of NFS, but try using the following command:

NSS /NCPDisplayNonTranslatableNames
0 Likes
gjw1 Absent Member.
Absent Member.

Re: Linux NFS clients report 'Unknown Error 526'

Hi there,

That sounds like a reasonable suggestion there.

First I need to point out that I have informed you slightly wrong on the first post - it is actually rsync that gives the 'Unknown Error 526' when it tried to do something with directories in question, ls actually gives an input output error.

Anyway, I just tried running this command on our Netware 6.5 SP5 lcuster node, and then offlined and onlined the volume but it didn't seem to make any difference - Should I try adding it to the autoexec.ncf and rebooting?
0 Likes
gjw1 Absent Member.
Absent Member.

Re: Linux NFS clients report 'Unknown Error 526'

gjw;1532593 wrote:
First I need to point out that I have informed you slightly wrong on the first post - it is actually rsync that gives the 'Unknown Error 526' when it tried to do something with directories in question, ls actually gives an input output error.


Further correction....

It depends on the Red Hat version.

ls on Red Hat Enterprise 3 gives Input/Ouput error
ls on Red Hat Enterprise 5 gives Unknown Error 526

Not impartant, just clearing up my mistake.
0 Likes
W_Prindl Absent Member.
Absent Member.

Re: Linux NFS clients report 'Unknown Error 526'

The problem with NFS on Netware is, that it is using the codepage 437
or 850 or whatever you have set your server to on the server side and
you do not use these code-pages in Linux under normal circumstances on
the client side. If your server is set to use UTF-8 at the server side
your Netware NFS server will try to translate that to your codepage and
fail.

In fact NFS on a Netware server is absolutely unusable on any recent
Linux distribution if you have any non standard characters in your
file-names - it simply does not work. You can get it to display those
files with incorrect or missing characters on your WS - but beware of
doing any changes to those files - you will end up with totally weird
filenames if looking at the same file from a Windows WS or from a Linux
WS using smbfs or novfs from NCL.

NFS is only usable for standard English characters and numbers in the
filename - everything beyond the character 128 (0x80) is condemned to
fail.
--
W. Prindl


gjw wrote:

>
>gjw;1532593 Wrote:
>> First I need to point out that I have informed you slightly wrong
>>on the first post - it is actually rsync that gives the 'Unknown
>>Error 526' when it tried to do something with directories in
>>question, ls actually gives an input output error.

>
>Further correction....
>
>It depends on the Red Hat version.
>
>ls on Red Hat Enterprise 3 gives Input/Ouput error
>ls on Red Hat Enterprise 5 gives Unknown Error 526
>
>Not impartant, just clearing up my mistake.


W. Prindl
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.