Bug 7536 - Error logs involving not yet implemented call_nt_transact_ioctl calls
Summary: Error logs involving not yet implemented call_nt_transact_ioctl calls
Status: NEW
Alias: None
Product: Samba 3.5
Classification: Unclassified
Component: File services (show other bugs)
Version: 3.5.3
Hardware: All Linux
: P3 normal
Target Milestone: ---
Assignee: Volker Lendecke
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-29 19:02 UTC by John H Terpstra (mail address dead(
Modified: 2011-07-27 12:55 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John H Terpstra (mail address dead( 2010-06-29 19:02:29 UTC 
Error logs of the following type are being generated on many Samba servers. The error report is misleading people into thinking that the failure of Samba to support the ioctl call may be the real cause of the problem they are seeking a resolution for.

Here is an example log fragment:
Jun 28 17:38:24 may smbd[19068]: [2010/06/28 17:38:24.944483,  0] smbd/nttrans.c:2200(call_nt_transact_ioctl) 
Jun 28 17:38:24 may smbd[19068]:   call_nt_transact_ioctl(0x900eb): Currently not implemented.

Suggestions:
a) Increase the debug level so that this message will only be generated at log level 4 and above.

b) Change the "Currently not implemented" message so that the administrator is not mislead into thinking that it is in fact necessary to implement it.

The ioctl 0x900eb means: FSCTL_READ_FILE_USN_DATA - an operation that apparently is meaningless in an Ext4 file system (or any UNIX/Linux file system).

Thank you Jeremy for decoding the IOCTL and for this suggestion!
Comment 1 Marat Denenberg 2011-07-27 12:55:41 UTC 
This is still an issue, especially for those of us who monitor our logs daily. Thank you!