Author Topic: NetDrive traps - since latest LIBCX drop...  (Read 2097 times)

Dariusz Piatkowski

  • Sr. Member
  • ****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 499
    • View Profile
NetDrive traps - since latest LIBCX drop...
« on: April 29, 2018, 05:57:24 pm »
Since the latest libcx/libc release (0.6.2-1.oc00 / 0.6.6-36.oc00) I started to see a consistent NetDrive crashes:

Code: [Select]
------------------------------------------------------------
04-28-2018  18:44:32  SYS3175  PID 0021  TID 0003  Slot 0061
G:\UTIL\NDFS\NDCTL.EXE
c0000005
1e754d45
P1=00000001  P2=2105002c  P3=XXXXXXXX  P4=XXXXXXXX 
EAX=0289f92c  EBX=006f5380  ECX=00000001  EDX=00000004
ESI=2105002c  EDI=0289f92c 
DS=0053  DSACC=f0f3  DSLIM=ffffffff 
ES=0053  ESACC=f0f3  ESLIM=ffffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1e754d45  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:0289f8ac  SSACC=f0f3  SSLIM=ffffffff
EBP=0289f8d0  FLG=00010212

LIBC066.DLL 0001:00054d45
------------------------------------------------------------

Has anyone else noticed anything similar to this?

I wonder whether the newly introduced 'SET LIBCX_HIGHMEM' option is causing some problems?

Currently the whole OS install runs with the default, which I believe is to do memhigh allocation whenever possible. I have not tried defaulting to 'SET LIBCX_HIGHMEM=2' instead, although that is my next test to see if NetDrive is impacted in any way.

Thanks!

guzzi

  • Sr. Member
  • ****
  • Thank You
  • -Given: 0
  • -Receive: 15
  • Posts: 290
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #1 on: April 29, 2018, 07:01:16 pm »
Here Netdrive works fine with the same libc.

Rene Hvidsoe

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 32
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #2 on: April 29, 2018, 07:27:39 pm »
Hi Dariusz,

Here my netdrive works.

I have all the updates to ArcaOS installed via ANPM, so same libcx as you.


Ben

  • Full Member
  • ***
  • Thank You
  • -Given: 0
  • -Receive: 3
  • Posts: 182
  • Know Thyself
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #3 on: April 30, 2018, 03:52:06 pm »
Same here, Darius, nary a problem with Netdrive...

nor any issues with anything for that matter, with the last Libc installed on two machines, using ANPM to install.

roberto

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 7
  • Posts: 441
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #4 on: May 03, 2018, 03:36:48 pm »
Well, I have not had any trap, but I've had a lot of problems and weird things.
The open office in two computers does not open any application. A computer with arca502 and another with arca501.
The thunderbird, when opening an attachment in pdf and another attachment in txt, opened the files with the same pid number, and soon after I had to restart it.
It is not possible to return to the previous version, because it says that phyton276 ..., and if I try to install an earlier version of the phyton, it also gives me another error.
But if I update I can not use the vbox.
saludos

roberto

  • Sr. Member
  • ****
  • Thank You
  • -Given: 16
  • -Receive: 7
  • Posts: 441
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #5 on: May 04, 2018, 05:11:12 pm »
It seems that one of them works only by updating the fat32 for the latest version. And I suppose that the other one plows him when adding him in the config.sys what of high memory.SET LIBCX_HIGHMEM=2
Saludos

Dariusz Piatkowski

  • Sr. Member
  • ****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 499
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #6 on: May 25, 2018, 09:56:14 pm »
A bit of an update...I think I have things stabilized now.

OK, so 1st thing 1st...it is my understanding that out there (in the OS/2 world) we effectively have two setups:

1) SERVER
2) CLIENT

In my case, I am relying on SAMBA client functionality, but using NetDrive exclusively as my GUI front-end.

So, back in early 2015 I had originaly installed the following:
rpmsubset4smb.zip         Feb 08, 2015
samba-1-1-4-804.wpi         Feb 08, 2015

Sometime later on in 2017 I upgraded with the following:
openldap-2.4.44-os2-20160503.zip   Mar 24, 2017
ndpsmb-3.2-samba46-20170317.zip   Mar 24, 2017
heimdal-1.5.3-os2-20160723.zip      Mar 24, 2017

...and finally in 2018 I deployed this:
smbclut-1_3_0-1054.zip
smbcln46-4.6.0-20170312.zip

I belive it is this last part (smbcln46-4.6.0-20170312.zip) that caused the problem. This is supposed to be the SAMBA client package for the 4.6 release, meanwhile sbmclut-1_3_0-1054.zip is the command line package for Samba 3.6.25.

My intent in deploying smbcln46-4.6.0-20170312.zip was to update the EXEs so that the NetDrive plugin will not run into any issues connecting to other machines.

Specifically, my NetDrive Samba plugin is:

Code: [Select]
[G:\util\NDFS\ndplugs]bldlevel ndpsmb.dll
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature:       @#netlabs:3.2.x#@##1## 12 Mar 2017 19:26:06     ECS85332116::en
::::@@NDPSMB - SMBFS NetDrive External Plugin Build beta-date
Vendor:          netlabs
Revision:        3.02.x
Date/Time:       12 Mar 2017 19:26:06
Build Machine:   ECS85332116
Language Code:   en
File Version:    3.2
Description:     NDPSMB - SMBFS NetDrive External Plugin Build beta-date

OK, that was the wrong upgrade. I should have kept things at the updated 3.x release. Eventually, when I back-leveled the issues were mostly resolved. However...there was a bit more to be gained from performance perspective.

I tuned my smb.conf file a tad, all of these I think are well known and documented settings. On my system specifically I now have a pretty well functioning setup, see the attached smb.conf for details. I get a consistent 50Meg/s throughput between my NAS box (ZyXel 325V2 with a really OLD WD test drive). Once I get my new ED Red NAS drives in there in a RAID-0 config (yeah, I know, but I have external USB nightly backup, so my focus here is on getting everyone in the house plenty of speed) I will update this thread with new numbers, not sure if the HD speed will have any effect on this or not, but I would have expected to get close to the theoretical 1Gig LAN limit (so 100 Mbyte/sec throughput).



Paul Smedley

  • Sr. Member
  • ****
  • Thank You
  • -Given: 11
  • -Receive: 52
  • Posts: 392
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #7 on: May 26, 2018, 11:42:24 am »
Hi Dariusz,

Sorry - I'm confused - how exactly did you resolve your issues? Backlevelling ndpsmb.dll and matching smbclnxx.dll? I'd rather fix the issue in current builds if it still exists.

If you want to test latest builds:
Netdrive plugin: http://smedley.id.au/tmp/ndpsmb-3.3-samba47-20170924.zip
Samba code: http://smedley.id.au/tmp/smbcln47-4.7.7-20180428.zip

Cheers,

Paul

Dariusz Piatkowski

  • Sr. Member
  • ****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 499
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #8 on: May 26, 2018, 09:31:15 pm »
Hi Paul,

...Sorry - I'm confused - how exactly did you resolve your issues? Backlevelling ndpsmb.dll and matching smbclnxx.dll? I'd rather fix the issue in current builds if it still exists...

Well, I simply reverted back to the smbclut-1_3_0-1054.zip package and made no other changes to the NetDrive samba plugin, I left that as it was, with the bldlevel info I showed in my last update.

Some months ago you made some changes to the NetDrive plugin based on the issues I was experiencing. I deployed that setup, the last set of filenames I deployed were:

1) ndpsmb-3.2-samba46-20170317.zip   
2) ndpsmb-fix1.zip

...with #2 being the last test release you made, which addressed the issues I was seeing on my system. I left things that way, probably expecting that eventually you (or bitwise works?) would release the final version. Not sure if that ever happened, maybe it did and I missed it?

More importantly, I am confused as to which is the proper set of CLUs to use:

1) smbclut-1_3_0-1054.zip

OR

2) smbcln46-4.6.0-20170312.zip

I am NOT running an OS/2 Samba server, only client, so given the description at the Samba wiki (http://trac.netlabs.org/samba/wiki), I ended up using smbclut-1_3_0-1054.zip.

In your previous post you listed two files, which I downloaded and will test out. However, I am still confused whether smbcln47-4.7.7-20180428.zip or smbclut-1_3_0-1054.zip should be used for a client-only install?

As best as I can tell it all comes down to which version of Samba client the particular CLU implements, right now, given the latest releases discussed here, these are:

1) smbclut-1_3_0-1054.zip (Version 3.6.25-OS/2 and OS/2-based systems v1.3.0-1054)

2) SMBCLN47-4.7.7-20180428 (Version 4.7.7)

Now, maybe if you are running an OS/2 server that matters a lot, which is perhaps why the wiki says they officially ONLY support the 3.6.25 release. But if all you want is the Samba client, does that open things up to running something like your latest test relase above, which is 4.7.7?

I will test this out and report back.
« Last Edit: May 26, 2018, 09:47:50 pm by Dariusz Piatkowski »

Dariusz Piatkowski

  • Sr. Member
  • ****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 499
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #9 on: May 26, 2018, 10:30:31 pm »
OK, test results are (NOTE: these are now outdated, skip to 'EDIT #2' below for final results):

1) the updated NetDrive Samba plugin does not work, my NetDrive does not even recognize it...so if I attempt to map a resource I do not even get a Samba plugin listed as one of the choices

2) the SMBCLN47-4.7.7-20180428 (Version 4.7.7) CLU works fine with the previous NetDrive beta plugin

So all in all, I see that I can use the 4.7.7 client side stuff, but no-go on the updated NetDrive Samaba plugin...what can I do to troubleshoot further? Do you want me to log a ticket for this Paul?

Thanks!

EDIT #1
======
Sorry, looks like I jumped the gun here on my testing. While accessing remote shares appears to work successfully, I could read the files, contents, play media, etc., I unfortunately could NOT write to the remote media. Backlevelling to smbclut-1_3_0-1054.zip was the only way to get this working again. So maybe this has some bearing on the result I saw with NetDrive not recognizing the Samba plugin as well?

EDIT #2
======
Well, not one to 'let things sit' I plugged away some more at troubleshooting this. Happy to report ALL IS GOOD!

So the key thing here is that my Samba client install only has the entry in the CONFIG.SYS PATH, nothing in the LIBPATH points to it. In this latest SMBCLN47-4.7.7-20180428 package there are now two DLLs which must be located somewhere in the LIBPATH, I did not have this done, nor did I copy them manually anywhere else. Looking at the ndpsmb.dll NetDrive plugin in DLLTree I realized it was failing to load the smbcln47.dll DLL. Subsequently, the NetDrive plugin wasn't finding the DLL it needed, and I am guessing this is why my copy TO a Samba share was failing. Once I made these DLLs accessible to all processes both the NetDrive plugin worked successfuly as well as copying TO and FROM a Samba share.
« Last Edit: May 27, 2018, 06:26:50 pm by Dariusz Piatkowski »

Roderick Klein

  • Sr. Member
  • ****
  • Thank You
  • -Given: 0
  • -Receive: 10
  • Posts: 280
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #10 on: May 30, 2018, 04:40:14 pm »
Since the latest libcx/libc release (0.6.2-1.oc00 / 0.6.6-36.oc00) I started to see a consistent NetDrive crashes:

Code: [Select]
------------------------------------------------------------
04-28-2018  18:44:32  SYS3175  PID 0021  TID 0003  Slot 0061
G:\UTIL\NDFS\NDCTL.EXE
c0000005
1e754d45
P1=00000001  P2=2105002c  P3=XXXXXXXX  P4=XXXXXXXX 
EAX=0289f92c  EBX=006f5380  ECX=00000001  EDX=00000004
ESI=2105002c  EDI=0289f92c 
DS=0053  DSACC=f0f3  DSLIM=ffffffff 
ES=0053  ESACC=f0f3  ESLIM=ffffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:1e754d45  CSACC=f0df  CSLIM=ffffffff
SS:ESP=0053:0289f8ac  SSACC=f0f3  SSLIM=ffffffff
EBP=0289f8d0  FLG=00010212

LIBC066.DLL 0001:00054d45
------------------------------------------------------------

Has anyone else noticed anything similar to this?

I wonder whether the newly introduced 'SET LIBCX_HIGHMEM' option is causing some problems?

Currently the whole OS install runs with the default, which I believe is to do memhigh allocation whenever possible. I have not tried defaulting to 'SET LIBCX_HIGHMEM=2' instead, although that is my next test to see if NetDrive is impacted in any way.

Thanks!

Did you open a ticket with BWW about this ?

Roderick Klein

Dariusz Piatkowski

  • Sr. Member
  • ****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 499
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #11 on: May 30, 2018, 07:04:36 pm »
Hi Roderick!

Did you open a ticket with BWW about this ?

No, I did not. I normally take the approach of investigating the issue on my own, when I get stuck I reach out to the forum, if still stuck I them move on to logging a ticket.

Given Paul's feedback re: NetDrive and 4.7.7 client versions, I now have a working environment, so logging a ticket seems like just another issue going into a bucket where, I get the feeling, the resources are already spread pretty thin.

Dariusz Piatkowski

  • Sr. Member
  • ****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 499
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #12 on: June 06, 2018, 02:48:11 pm »
Paul,

...
If you want to test latest builds:
Netdrive plugin: http://smedley.id.au/tmp/ndpsmb-3.3-samba47-20170924.zip
Samba code: http://smedley.id.au/tmp/smbcln47-4.7.7-20180428.zip
...

Well, despite the initial results - which are great for READs and small WRITEs - I came to discover that the 4.7.7 client version introduced a pretty serious error: when copying whole directories and their contents TO the Samba share storage, if a given target directory already exists with a matching name (but it is located somewhere else in the directory tree structure) the resulting copy operation puts the files being copied in BOTH locations, that creates a pile of a mess. I discovered this as I proceeded with my photo and video album migration to the NAS.

Anyways, this is hard to explain, so I'm going to log a ticket at the Samba Netlabs.org project page.

Thanks again!

EDIT #1
======
Created Samba ticket #322, please see trac.netlabs.org/samba/ticket/322.
« Last Edit: June 06, 2018, 03:26:32 pm by Dariusz Piatkowski »

Andi B.

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 20
  • Posts: 412
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #13 on: June 06, 2018, 04:33:15 pm »
Quote
Anyways, this is hard to explain, so I'm going to log a ticket at the Samba Netlabs.org project page.
For Pauls built? Guess Pauls mantis page would be more appropriate.

Dariusz Piatkowski

  • Sr. Member
  • ****
  • Thank You
  • -Given: 13
  • -Receive: 9
  • Posts: 499
    • View Profile
Re: NetDrive traps - since latest LIBCX drop...
« Reply #14 on: June 06, 2018, 10:15:04 pm »
Hey Andi,

Quote
Anyways, this is hard to explain, so I'm going to log a ticket at the Samba Netlabs.org project page.
For Pauls built? Guess Pauls mantis page would be more appropriate.

Yeah, I know what you mean, I struggled with this a bit but went Netlabs route because I think their Samba releases are viewed as the core OS/2 releases and I understand that there is a bit of cross work behind the scenes.

I was very up-front about this in my ticket and actually stated that if looking at the issue I'm seeing in Paul's test 4.7.7 release is of no benefit to the bigger OS/2 Samba project they can certainly go ahead and close the ticket. I leave it up to that team to determine the best route. Meanwhile, if Paul checks-in on this thread I'm sure he'll provide his feedback if he sees a better way.