Bug 2577 - request_oplock_break: pid=523, share_entry->pid=521
Summary: request_oplock_break: pid=523, share_entry->pid=521
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.8
Hardware: Other Windows 2000
: P3 major
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
Depends on:
Reported: 2005-04-05 19:36 UTC by Aaron Tseng
Modified: 2006-04-08 11:52 UTC (History)
1 user (show)

See Also:

log level=10 (115.70 KB, text/plain)
2005-04-05 19:45 UTC, Aaron Tseng
no flags Details
configure file for samba (2.05 KB, text/plain)
2005-04-05 19:49 UTC, Aaron Tseng
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Tseng 2005-04-05 19:36:33 UTC
My environment:

   Target: Arm9 Linux 2.4.18 or 2.4.20 with USB driver from 2.4.26
           a PCI to USB 2.0 card (VIA 6212)
           USB 2.0 Hard disk format as FAT32 file system
    PC: Windows 2000

    Connect Target from PC then copy a file bigger than 400MB to Target,
the Target will get oplock_break failed.

    I check the source code and got 
 request_oplock_break()in oplock.c will compare

  current pid and share_entry->pid

     but this two pids are different

    451 aaron      2060 D   /usr/hddapp/sbin/smbd -D
    466 aaron      2012 S   /usr/hddapp/sbin/smbd -D

    So a oplock_break request is sent to PC, but got no response.

  Would you please give me a hint why the pid 451 go to 'D' state ?

  In the ormal case it should not go to 'D' state and there should not have pid 
466, any comment is appreciate.

   I will attach my log.smbd later.
Comment 1 Aaron Tseng 2005-04-05 19:45:48 UTC
Created attachment 1140 [details]
log level=10

This is a log file created by me, please extract it by winrar or winzip.
Comment 2 Aaron Tseng 2005-04-05 19:49:12 UTC
Created attachment 1141 [details]
configure file for samba

configure file used
Comment 3 Gerald (Jerry) Carter (dead mail address) 2006-04-08 11:52:32 UTC
please reopen if the bug still exists in a current release.
Oplock code has since been rewritten