Author Topic: Updated Samba Client  (Read 197070 times)

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2548
  • Karma: +200/-0
    • View Profile
Re: Updated Samba Client
« Reply #90 on: January 12, 2024, 09:16:12 pm »
  BTW, deleting those 55000 files makes the server start MUCH faster. Wonder if there is a way to clean those up before the server is shut down...

https://smedley.id.au/tmp/smbd-4.19.4-20240112.zip improves (but doesn't  completely fix)  the situation.

https://smedley.id.au/tmp/smbd-4.19.4-20240113.zip should correct this. It includes changes to clean up any errant lock files during smbd exit.

David McKenna

  • Hero Member
  • *****
  • Posts: 905
  • Karma: +35/-0
    • View Profile
Re: Updated Samba Client
« Reply #91 on: January 12, 2024, 10:21:21 pm »
 Hey Paul,

  Tried the new 4.19 client and it works great with the 4.11 server with no issues whatever, so I'm leaving that installed on the client.

  Tried the new 4.19 server and I have the same issues as before - eventually I get the 'out of memory' error on the command line, and '0 files' with the WPS. SMBCLIENT will also time out on the \software\os2 directory without the -t 60 directive. All this with the default inetcfg.ini just like yours on server and client, so that isn't the culprit.

  The fact it works for you and not me implies my configuration is somehow different. Need to figure out what - what NICs are you using on the server and client? My server has an Intel NIC, and client has a Realtek.

  I'm interested in any ideas what might influence SAMBA in the OS/2 system that could be changed in the normal course of usage...

Regards,

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2548
  • Karma: +200/-0
    • View Profile
Re: Updated Samba Client
« Reply #92 on: January 13, 2024, 03:02:16 am »
  Tried the new 4.19 client and it works great with the 4.11 server with no issues whatever, so I'm leaving that installed on the client.

  Tried the new 4.19 server and I have the same issues as before - eventually I get the 'out of memory' error on the command line, and '0 files' with the WPS. SMBCLIENT will also time out on the \software\os2 directory without the -t 60 directive. All this with the default inetcfg.ini just like yours on server and client, so that isn't the culprit.

  The fact it works for you and not me implies my configuration is somehow different. Need to figure out what - what NICs are you using on the server and client? My server has an Intel NIC, and client has a Realtek.

  I'm interested in any ideas what might influence SAMBA in the OS/2 system that could be changed in the normal course of usage...

I wish i had more ideas on the cause of this. Do you have access  to smbclient on a linux machine?  Curious if it shows the same behaviour or if it's something OS/2 specific on your client.

My server has an Intel Pro 1000 using the Multimac32-E1000B driver. I think the Virtualbox client is also using the Intel Pro 1000 driver.

Were you able to confirm the fixed smbd.exe from this morning fixes the issues with stray files left in %etc%\samba\lock\msg.lock?

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2548
  • Karma: +200/-0
    • View Profile
Re: Updated Samba Client
« Reply #93 on: January 13, 2024, 08:40:54 am »
eventually I get the 'out of memory' error on the command line, and '0 files' with the WPS.
When this happens, what do tools like the Xcenter sentinel memory watcher say about the state of the system? Is low/high memory actually exhausted? (Edit: found an earlier message where you confirmed the system doesn't actually appear  to be out of ram.

Let's try the following:
- reinstate \ndpsmb.dbg
- edit  smb.conf and increase loglevel to 8 (on the client PC)
- restart ndctl.exe
- recreate the error, note the system timestamp when the error occurs
- zip log.ndpsmb & log.smbc & attach to https://mantis.smedley.id.au/view.php?id=769
- revert loglevel to save your system filling up :)
« Last Edit: January 13, 2024, 08:49:04 am by Paul Smedley »

David McKenna

  • Hero Member
  • *****
  • Posts: 905
  • Karma: +35/-0
    • View Profile
Re: Updated Samba Client
« Reply #94 on: January 13, 2024, 02:21:16 pm »
Hi Paul,

  I uploaded the logs you requested to your Mantis. Can also confirm the \lock\msg.lock directory is cleared when the server is shutdown - thanks for that!

  One thing I think I already mentioned is that I can use the 4.19 server from Windows without losing the connection (so far). I am going to set up a Virtual Box on my Windows machine, install ArcaOS to it and see how it works from there (since that is how you are doing it). Can you try connecting from a bare metal OS/2 install to your server? Wondering if the forwarding by Windows (or Linux as the case may be) is somehow masking the issue...

Regards,

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2548
  • Karma: +200/-0
    • View Profile
Re: Updated Samba Client
« Reply #95 on: January 13, 2024, 10:27:57 pm »
Hey Dave, thanks for the logs,  I'll review later today. I'll also see if I can test on my other bare metal box.

David McKenna

  • Hero Member
  • *****
  • Posts: 905
  • Karma: +35/-0
    • View Profile
Re: Updated Samba Client
« Reply #96 on: January 14, 2024, 01:16:13 am »
Paul,

 I'm seeing some 'Broken Extended Attributes detected for:' messages in some of the server logs for some directories and files. Is that a problem? Is there a way to repair EA's (if they really are broken)?

Regards,

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2548
  • Karma: +200/-0
    • View Profile
Re: Updated Samba Client
« Reply #97 on: January 14, 2024, 04:54:24 am »
Can you send me a sample file (offline) for analysis?

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5491
  • Karma: +133/-1
    • View Profile
Re: Updated Samba Client
« Reply #98 on: January 14, 2024, 05:34:51 am »
Is there a way to repair EA's (if they really are broken)?

Checkout https://88watts.net/download/eaclean-1.3.zip. From the blurb,
Code: [Select]
Displays and cleans EA litter from files. -c or -c1 = clean ea litter only Removes unnecessary UID, GID, MODE, INO, RDEV, GEN, FLAGS EAs. -c2 = same as -c1 plus remove unnecessary .LONGNAME EAs and MR.ED.TXTPOS. -c3 = same as -c2 plus remove .LONGNAME EAs that do not match the file name. Use -c3 with caution and do not use -c3 on boot volumes.

Eaclean displays the name of the file if any EAs were removed. It will display Removed all EAs from filename if it ended up removing all the EAs, or Removed some EAs from filename if only some of the EAs were removed. Eaclean currently cannot process files that are open or locked.

David McKenna

  • Hero Member
  • *****
  • Posts: 905
  • Karma: +35/-0
    • View Profile
Re: Updated Samba Client
« Reply #99 on: January 14, 2024, 11:29:40 am »
Dave,

 Tried eaclean on the shared drive, but it crashes:

[D:\]eaclean -c2 -s *
SYS1808:
The process has stopped.  The software diagnostic
code (exception code) is  0005.

 It works on my desktop though, so this is not a good sign. The shared drive is an old-fashioned rotating drive. I have a 2TB NVMe drive on my desk I'm going to replace the old drive with. Gotta copy all the data first. Of course, this doesn't explain why 4.11 works and 4.19 has trouble...

Regards,

David McKenna

  • Hero Member
  • *****
  • Posts: 905
  • Karma: +35/-0
    • View Profile
Re: Updated Samba Client
« Reply #100 on: January 14, 2024, 11:30:49 am »
Paul,

 Do you want a log or an actual 'broken EA' file?

Regards,

Paul Smedley

  • Hero Member
  • *****
  • Posts: 2548
  • Karma: +200/-0
    • View Profile
Re: Updated Samba Client
« Reply #101 on: January 14, 2024, 11:04:41 pm »
Do you want a log or an actual 'broken EA' file?

Ideally, both

David McKenna

  • Hero Member
  • *****
  • Posts: 905
  • Karma: +35/-0
    • View Profile
Re: Updated Samba Client
« Reply #102 on: January 15, 2024, 10:06:44 pm »
 OK, I replaced the old rotating 2TB drive with a brand new 2TB PCIe 4x4 NVMe drive (plugged into a PCIe 4 slot). Went to my backup drive and ran 'eaclean -c2 -s *' on it. It removed a good many EA's. Copied the cleaned data on the backup drive onto the new drive via ndpsmb 4.19 to the new drive on the SAMBA 4.11 server. EA support was off on the client, server was default (which I believe is to support EA's). Used 'xcopy D: N: /H /O /T /S /E /R /V' and everything got copied back over via SAMBA in about 30 minutes.

 Then on the server I ran 'eaclean -c2 -s *' on the copied data on the shared drive and it removed A LOT of EA's! I didn't think EA's would be copied (because support was off on the client), and even so, I had already cleaned all the files before copying. Maybe I misunderstand what 'EA support' does. Can anyone explain?

 Anyway, the real punch line is that now it works with the 4.19 server. SMBCLIENT does not time out, it works. I don't know if it is because the new drive is so much faster, or because 'broken EA's' are gone. Still early, but so far I have not got an out of memory condition, and it is very much faster to display files in the WPS.

 Has EA support been changed since 4.11? Maybe something there is slowing things down - like checking EA's - in 4.19 it didn't do in 4.11?

Regards,

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5491
  • Karma: +133/-1
    • View Profile
Re: Updated Samba Client
« Reply #103 on: January 15, 2024, 10:17:23 pm »
Hi David, any libc program will add a bunch of EA's, namely UID, GID, MODE, INO, RDEV, GEN, FLAGS EAs.
So Samba, being built with GCC and Libc will add all those EA's.

David McKenna

  • Hero Member
  • *****
  • Posts: 905
  • Karma: +35/-0
    • View Profile
Re: Updated Samba Client
« Reply #104 on: January 15, 2024, 10:19:12 pm »
Hey Dave,

 Do you know if there is a way to turn that off?

Regards,