Highlighted
Absent Member.
Absent Member.
768 views

nss over nfs shows files in dos format

Hi,

I'm trying to move files from my old NetWare server to OES11. I've mounted that NW NSS volume over NFS on OES11 server. The problem is that several directories are shown in DOS name space format (folder~1 instead of FolderName) which is unacceptable. If accessing the NetWare volume from Windows client or on the server itself, all folders are shown correct way - in LONG name space format. All attributes looks the same on problem and good folders.
Please give me a clue to fix that bug.

Regards,
Michael
Labels (2)
0 Likes
7 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: nss over nfs shows files in dos format

mmoskalev wrote:

> I'm trying to move files from my old NetWare server to OES11.


Have you looked at Migrating File Systems to OES 11 SP3?
https://www.novell.com/documentation/oes11/mig_tools_lx/data/bgr318y.html

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: nss over nfs shows files in dos format

This way is involving SMS which quite complicating.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: nss over nfs shows files in dos format

Am 04.02.2017 um 00:06 schrieb mmoskalev:
>
> This way is involving SMS which quite complicating.
>
>

Seriously? SMS which is almost a core function of every netware server
and needs nothing more than loading a single NLS is more complicated
than NFS, which is a truly awkward and alien addition with hardly any
functionality on Netware?

No, seriously. Don't use NFS. Are you aware that beside the migration,
OES11 comes with a full featured Novell Client? More precisely,
including ncpfs, even two of them?

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: nss over nfs shows files in dos format

I meant that copying files more simple than backup/restore via SMS.
Thanks for Novell Client suggestion, I'll try this one.

Regards,
Michael
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: nss over nfs shows files in dos format

Hello,

what Kevin and Massimo meant is that if you would like to follow the
link
https://www.novell.com/documentation/oes11/mig_tools_lx/data/bgr318y.html
you will not have to backup/restore but if you use the miggui for
instance you can just copy the files (and maybe also the trustees if
both servers are in the same tree and have NSS file systems) from
Netware server to OES11 server (SMS/TSAFS should be up and running on
both servers of course). Even i am able to do so.

Regards Burkhard

OES Admin
Debeka Versicherungen Koblenz
Germany
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: nss over nfs shows files in dos format

wiegandb wrote:

> Debeka


Hi Debeka,

Good catch.

After seeing your post I again read the whole thread and agree that
Michael likely missed the point. Your post may save him a significant
amount of work. 🙂

--
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Absent Member.
Absent Member.

Re: nss over nfs shows files in dos format

This reply is quite late and probably no longer helpful, but I wanted to reply for the benefit of anyone finding this thread in the future.

When accessing a NetWare NSS volume with NFS, you should be seeing entries as they exist in the NFS name space of the NSS volume. This name space usually is a close match for the LONG name space (which you see from Windows). However, since it is a *separate* name space, it can contain different names than LONG name space. Depending on the history of how individual entries were created and/or modified, (i.e. someone accessing the system through DOS name space might have created or renamed some of these) there could be cases where NFS namespace was populated differently. In your case, it seems that some entries have populated based on DOS name space instead of LONG, which can be normal for some sequences of events.

If you are curious to check the NFS name space vs other name spaces, I believe you do that with the NWADMIN management utility. Double-click on the volume. Browse to the directory you want to check, right click on the directory, select 'Details...' and check the 'Identification' page. Or maybe there is a "properties" page? It's hard to remember, and I don't have access to one right now. There may be other tools that can do this as well, but being able to check the name in all namespaces, from one tool, is not necessarily a common feature. But even so, I don't think you can do anything other than VIEW these in nwadmin.

You said it was "several directories" so I assume it is not "all directories", rather it is isolated to a few cases. If this was an older non-NSS volume, I might suggest that you remove the NFS name space and add it back, which would theoretically repopulate from LONG name space. But that approach is not possible on NSS, and even on non-NSS volumes it might have an unexpected side effect.

If the number of directories involved is not too large, you might be able to rename directories (from windows ncp client or from imanager), and the changes might proliferate into NFS name space. From the viewpoint of windows or imanager, you'd be renaming a directory to a different name and then back to it's original name, an in theory the would proliferate to other name spaces. That might do the trick. But I suspect you have more of these than you want to deal with manually. So some of the other non-NFS suggestions in this thread might be better.
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.