[Bug 743280] Re: Folder-watching is broken

[Bug Watch Updater]

** Changed in: samba
       Status: Unknown => Fix Released

** Changed in: samba
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/743280

Title:
  Folder-watching is broken

Status in Samba:
  Fix Released
Status in “samba” package in Ubuntu:
  Fix Released
Status in “samba” source package in Lucid:
  Confirmed
Status in “samba” source package in Maverick:
  Confirmed

Bug description:
  Binary package hint: samba

  # lsb_release -rd
  Description:    Ubuntu 10.04.2 LTS
  Release:        10.04

  # apt-cache policy samba
  samba:
    Installiert: 2:3.4.7~dfsg-1ubuntu3.5
    Kandidat: 2:3.4.7~dfsg-1ubuntu3.5

  
  I have my music stored on a samba-share. I'm using foobar2000 wich monitors my music. Every time I change some files on my share I get errors in foobar2000.

  I did some research and found the problem. This is the way you can reproduce and monitor it on my pc:
  - Add a share to the foobar200 library
  - Start Wireshark, and filter the view by "smb.nt.function == 4".
  - Start Process Monitor, filter everything out except foobar2000.exe. Perhaps go to "Filter > Highlight" and exclude "Result" in "SUCCESS", "FAST IO DISALLOWED" and "NAME NOT FOUND", to see the interesting lines more easily.
  - Rename one of the files in the monitored folder.

  Now if it's broken:
  - The status of the ML directory changes to "Error!".
  - Message like "Folder watching failure: The specified server cannot perform the requested operation." is logged to the console.
  - Process Monitor log contains "0xC00000C3" result code for the "NotifyChangeDirectory" call.
  - Wireshark captured a "NT Trans Response, FID: 0x????, NT NOTIFY" with the change notification. It contains at least two parameters, like RENAMED_OLD_NAME and RENAMED_NEW_NAME, and the first has "File Name Len" not divisible by 4 and "Next Entry Offset" neither.
  - There are no further "NT NOTIFY" responses because the connection is closed due to error by the Win7 client.

  Here's how that part should be implemented:
  http://msdn.microsoft.com/en-us/library/ee441569(v=prot.13).aspx
  "Each entry in the list MUST be DWORD aligned (32-bit aligned), so NextEntryOffset MUST be a multiple of 4."

  And according to samba this is a bug and it got fixed in one of their newer releases:
  http://www.samba.org/samba/history/samba-3.5.6.html
  "BUG  7662: Align change notify replies on 4-byte boundary"
  http://www.samba.org/samba/history/samba-3.5.6.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/samba/+bug/743280/+subscriptions