Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - David McKenna

Pages: 1 2 [3] 4 5 ... 50
31
Networking / Re: Updated Samba Client
« on: January 23, 2024, 03:52:36 pm »
 Paul,

 I should have known about the truncation - sorry about that. Did it again with max log set to 500000 - started at 9:35 and got the OOM at 9:38. I can pretty consistently get it in about 3 minutes now. Attached.

Regards,

32
Networking / Re: Updated Samba Client
« on: January 22, 2024, 10:45:12 pm »
Paul,

 OK, I attached 2 zip files - one with server logs and one with client logs with loglevel=8. I started the server and client at 16:28 and got the OOM condition at 16:31. It's  a bummer and surprising you can't easily get it...

Regards,

33
Networking / Re: Updated Samba Client
« on: January 22, 2024, 12:19:06 pm »
Thanks Paul - now the EA's shown on the client match those on the server. Still get an 'out of memory' eventually...

 Do you think Theseus might help in identifying what is running out of memory?

Regards,

34
Networking / Re: Updated Samba Client
« on: January 21, 2024, 03:21:35 pm »
Paul,

  Attached are:

local.txt - mp3 file on local drive on client
share.txt - same mp3 file after copied to share from client
server.txt - copied mp3 on local drive on server

 All using 4.19 with EA support on both client and server.

Regards,

35
Networking / Re: Updated Samba Client
« on: January 21, 2024, 01:23:54 am »
Thanks Paul,

 Unfortunately, I still eventually get the 'out of memory' error with this one. When I have both server and client set to allow EA's, I see a larger number for EA's with this one than the last one, but still smaller than what is on the server (and not quite the same value (slightly smaller) as with 4.11, but close).

 For example - the MP3 file I mentioned I copied from client to server earlier shows 488 for EA's on my client local drive, but shows 814 directly on the server after copying. With server 4.11, on the client share drive it shows 771 for EA's on that file, and with this latest 4.19 it shows 764 for EA's.

 Another twist I just noticed - if I have the client set to not use EA's, I can play the MP3 file from the share by double clicking it, and the WPS plays it. If I have the client set to support EA's, when I double click it, it opens PM123 and plays it. This happens with both the 4.11 and 4.19 servers. Not clear why...

Regards,

36
Networking / Re: Updated Samba Client
« on: January 20, 2024, 02:22:38 pm »
Hey Paul,

@Dave -  an observation locally...
4.11 Server - EA's visible to client
4.18/4.19 Server - EA's not visible to client.

Same server smb.conf in use.  Do you see the same thing?  I wonder if this is part of the issue with the client.

Client *can* see EA's on a server running 4.18.x under Ubuntu.

 I tested this by copying a file (MP3) with EA's to the shared drive, then viewing on the command line. With server 4.19, as long as 'ea support = Yes' was in smb.conf on the server, I could see the EA's on the share. If set to 'No', then all EA's show '0'. EA support must be 'on' on the client to see EA's......

EDIT: But... It doesn't show the same value on the client that it shows directly on the server! There are many files with a small number of EA's (as seen on the server) that show '0' on the client, and the file I copied shows a larger EA number on the server than shows on the client. Strange...

EDIT2: But2... If I use server 4.11, I can see EA's larger than 0 on the client, but still smaller than what I see directly on the server. So it seems SAMBA does not display the total number of EA's (on the client) in either version 4.11 or 4.19, but shows more in 4.11.

Regards,

37
Networking / Re: Samba Users and Groups
« on: January 19, 2024, 06:07:44 pm »
Neil,

  That's what I've been doing for testing - stop the server, then just unzip over the old files, then restart the server. Keep a zipped backup of the old so you can easily unzip that over the new one if needed.

Regards,

38
Networking / Re: Updated Samba Client
« on: January 19, 2024, 06:04:30 pm »
Paul,
Interesting:
Code: [Select]
[2024/01/19 18:12:12.072000,  3] ../../source3/smbd/smb2_server.c:4033(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_NO_EAS_ON_FILE] || at ../../source3/smbd/smb2_getinfo.c:159

 I'm not seeing that error on either the client (4.19) or server (neither 4.11 nor 4.19). Using log level = 8 on both. All I see on the client side (both 4.11 and 4.19 server) is many dozens of:

[2024/01/19 11:32:59.648000,  3] ../../source3/libsmb/clierror.c:91(cli_status_to_errno)
  cli_status_to_errno: 0xc0000034 -> 2

 On the server side, the logged errors I see are:

[2024/01/19 10:01:17.493000,  2] ../../source3/nmbd/nmbd_winsserver.c:634(initialise_wins)
  initialise_wins: Can't open wins database file wins.dat. Error was No such file or directory**

[2024/01/19 10:01:40.006000,  5] ../../source3/nmbd/nmbd_namequery.c:77(query_name_response)
  query_name_response: On subnet UNICAST_SUBNET - negative response from IP 192.168.21.2 for name IBMPEERS<1b>. Error code was 3.**

[2024/01/19 10:19:00.702000,  0] ../../lib/util/pidfile.c:240(pidfile_unlink)
  Failed to delete pidfile C:\MPTN\ETC/samba/pid/nmbd.pid. Error was No such file or directory.**

[2024/01/19 10:18:30.430000,  3] ../../source3/smbd/smb2_server.c:4033(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_NO_MEMORY] || at ../../source3/smbd/smb2_create.c:360

[2024/01/19 10:18:30.622000,  5] ../../source3/smbd/dosmode.c:418(fget_ea_dos_attribute)
  fget_ea_dos_attribute: Cannot get attribute from EA on file .: Error = Attribute not found

[2024/01/19 10:18:32.229000,  3] ../../source3/smbd/smb2_server.c:4033(smbd_smb2_request_error_ex)
  smbd_smb2_request_error_ex: smbd_smb2_request_error_ex: idx[1] status[NT_STATUS_OBJECT_PATH_NOT_FOUND] || at ../../source3/smbd/smb2_create.c:360


 There were many multiples of each of the above - only one shown.

** Indicate errors seen with both the 4.11 and 4.19 server. The last three are only seen with the 4.19 server.

 One thing I have noticed - I have 'max log size = 2048' in the server smb.conf, but it seems to be ignored because I get logs over 10MB all the time, especially with log level = 8. Maybe a bug?

Thinking out loud:

 wins.dat does exist in the C:\MPTN\ETC\samba\lock directory - maybe the server is looking in the wrong place?

 nmbd.pid is deleted when the server is stopped - maybe that error comes after it has been deleted?

 The 'attribute not found' might be because I have EA's turned off with SET LIBC_UNIX_EAS= on the shared drive?

 The name of the computer at 192.168.21.2 is MAINMACHINE. IBMPEERS is the workgroup. Maybe some kind of confusion?


Regards,

39
Networking / Re: Updated Samba Client
« on: January 19, 2024, 12:12:47 pm »
Paul,

  How do I view EA's? Is that something that can be done directly, or are you looking in a log file?

  I see stuff like this in an smbd log on the server:

os2getxattr : (Software/Windows/DRIVERS:0) user.DOSATTRIB 32
os2getxattr : (Software/Windows/DRIVERS:0) user.DOSATTRIB 32
os2getxattr : (Software/Windows/DRIVERS:0) user.DOSATTRIB 32
os2getxattr : (SOFTWARE:0) user.DOSATTRIB 32
os2getxattr : (SOFTWARE:0) user.DOSATTRIB 32
os2getxattr : (SOFTWARE:0) user.DOSATTRIB 32
os2getxattr : (SOFTWARE/WINDOWS:0) user.DOSATTRIB 32
os2getxattr : (SOFTWARE/WINDOWS:0) user.DOSATTRIB 32
os2getxattr : (SOFTWARE/WINDOWS:0) user.DOSATTRIB 32
os2getxattr : (SOFTWARE/WINDOWS/DRIVERS:0) user.DOSATTRIB 32
os2getxattr : (SOFTWARE/WINDOWS/DRIVERS:0) user.DOSATTRIB 32
os2getxattr : (SOFTWARE/WINDOWS/DRIVERS:0) user.DOSATTRIB 32

 This is with EA's disabled on both client and server, and using Rich's SET LIBC_UNIX_EAS=C,!D to turn off EA's on the shared drive.

Regards,

40
Networking / Re: Updated Samba Client
« on: January 15, 2024, 11:33:15 pm »
 Arggh! Just got the 'out of memory' error again! Rats - thought it was defeated, but apparently not. SMBCLIENT still works without timing out though, so apparently that was unrelated.

Regards,

41
Networking / Re: Updated Samba Client
« on: January 15, 2024, 11:19:25 pm »
Rich,

 Thanks for that! I'll try using it on my shared drive. Hopefully SAMBA won't object...but we'll see.

Regards,

42
Networking / Re: Updated Samba Client
« on: January 15, 2024, 10:19:12 pm »
Hey Dave,

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

Regards,

43
Networking / Re: Updated Samba Client
« 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,

44
Networking / Re: Updated Samba Client
« on: January 14, 2024, 11:30:49 am »
Paul,

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

Regards,

45
Networking / Re: Updated Samba Client
« 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,

Pages: 1 2 [3] 4 5 ... 50