Bug 445332 - close_our_files erroneously closes FD for gencache.tdb
close_our_files erroneously closes FD for gencache.tdb
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: samba (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Simo Sorce
Depends On:
  Show dependency treegraph
Reported: 2008-05-06 04:38 EDT by Stephen J. Gowdy
Modified: 2012-06-20 11:59 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 11:59:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch from Samba Bugzilla (1.06 KB, patch)
2008-05-06 04:38 EDT, Stephen J. Gowdy
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Samba Project 3327 None None None Never

  None (edit)
Description Stephen J. Gowdy 2008-05-06 04:38:31 EDT
Description of problem:

Errors while having a windows file system mounted.

Version-Release number of selected component (if applicable):


How reproducible:

Mount a windows filesystem from XP (probably any).

Steps to Reproduce:
1. See Above.
2. Watch /var/log/messages.
Actual results:

mount.smbfs[2841]:   tdb(/var/cache/samba/gencache.tdb): 
tdb_lock failed on list 112 ltype=1 (Bad file descriptor) 

Expected results:

No such errors.

Additional info:

Patch from https://bugzilla.samba.org/show_bug.cgi?id=3327 applies cleanly, I've
attached it here too.
Comment 1 Stephen J. Gowdy 2008-05-06 04:38:31 EDT
Created attachment 304609 [details]
Patch from Samba Bugzilla
Comment 2 Jiri Pallich 2012-06-20 11:59:32 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

Note You need to log in before you can comment on or make changes to this bug.