Bug 5469 - smbc_getxattr(): Flaky behaviour
smbc_getxattr(): Flaky behaviour
Status: RESOLVED INVALID
Product: Samba 3.0
Classification: Unclassified
Component: libsmbclient
3.0.28a
x64 Linux
: P3 major
: none
Assigned To: Derrell Lipman
Samba QA Contact
http://www.sendspace.com/file/61qe4i
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-05-17 06:21 UTC by Veeral Shah
Modified: 2009-01-03 09:50 UTC (History)
1 user (show)

See Also:


Attachments
tcpdump of smb protocol messages for the success case (664.92 KB, application/octet-stream)
2008-05-21 04:15 UTC, Veeral Shah
no flags Details
Debug messages - for the error case (2.80 KB, application/octet-stream)
2008-05-21 04:16 UTC, Veeral Shah
no flags Details
Debug messges (gzipped text filed) - Success case (7.00 KB, application/octet-stream)
2008-05-21 04:17 UTC, Veeral Shah
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Veeral Shah 2008-05-17 06:21:29 UTC
smbc_getxattr() is behaving a little strangely. I am attempting to get extended attributes for a score of files on a public share (which does not require user_name/passwd credentials to connect to). The name of the attribute that I am interested in is "system.nt_sec_desc.owner+". For first few runs, this API behaved correctly and returned me the correct owner name . But in subsequent runs of my app, the same API invocation results in error. The errno is 61 (ENODATA). Is this a known issue?
Comment 1 Derrell Lipman 2008-05-20 13:00:33 UTC
This is not a known issue.  If you would send me packet traces of a working and a non-working run of your application, I'll see if I can track down what's happening.

If I understand you correctly, you're starting your application *from scratch* each time, and some times it works and some times it doesn't?  If so, I'd certainly expect the same results each time...

To create a packet trace, use this command line:

  tcpdump -s 0 -w mytrace.pcap

(Obviously, if you're creating multiple traces, you'll replace the file name at the end with a new name each time.)

Derrell
Comment 2 Veeral Shah 2008-05-21 04:15:54 UTC
Created attachment 3298 [details]
tcpdump of smb protocol messages for the success case
Comment 3 Veeral Shah 2008-05-21 04:16:27 UTC
Created attachment 3299 [details]
Debug messages - for the error case
Comment 4 Veeral Shah 2008-05-21 04:17:05 UTC
Created attachment 3300 [details]
Debug messges (gzipped text filed) - Success case
Comment 5 Veeral Shah 2008-05-21 04:28:06 UTC
http://www.sendspace.com/file/61qe4i points to the tcpdump of the error case,
Comment 6 Derrell Lipman 2008-05-30 08:34:05 UTC
I don't think you uploaded the correct packet traces.  In the "worked" trace, there is no SMB traffic and in the "didnt_work" trace, there is very little, and no relevant, SMB traffic.  I need to be able to see the get attribute requests and responses in the success and failure cases to be able to make sense of the problem you're having.

Derrell
Comment 7 Derrell Lipman 2009-01-03 09:50:14 UTC
No reply in six months.  Re-open if necessary.

Derrell