Bug 200452 - smbd crashes periodically with SIGIO, causes "Delayed Write Failed"
Summary: smbd crashes periodically with SIGIO, causes "Delayed Write Failed"
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: samba
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jay Fenlason
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-27 19:21 UTC by Orion Poplawski
Modified: 2014-08-31 23:28 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2006-07-27 21:30:13 UTC


Attachments (Terms of Use)


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

Description Orion Poplawski 2006-07-27 19:21:24 UTC
Description of problem:

On FC4 server with samba-3.0.23a-1.fc4.1 and kernel 2.6.17-1.2142_FC4, we are
seeing smbd crash periodically with SIGIO.  This causes the windows client to
report "Delayed Write Failed".  It appears that it recovers and reconnects
afterwards, but apparently data could be lost.

Example strace:

21136 13:06:09 getegid32()              = 0
21136 13:06:09 setgroups32(3, [1001, 1002, 1020]) = 0
21136 13:06:09 setresgid32(-1, 1001, -1) = 0
21136 13:06:09 getegid32()              = 1001
21136 13:06:09 setresuid32(1017, 1017, -1) = 0
21136 13:06:09 geteuid32()              = 1017
21136 13:06:09 fcntl64(11, F_SETLKW64, {type=F_UNLCK, whence=SEEK_SET,
start=7124, len=1}, 0xbfb424a4) = 0
21136 13:06:09 --- SIGIO (I/O possible) @ 0 (0) ---
21136 13:06:09 +++ killed by SIGIO +++

A mention on the mailing list extists as well:

http://lists.samba.org/archive/samba-technical/2006-February/045477.html
Version-Release number of selected component (if applicable):


How reproducible:
Very.  Every few hours.

Comment 1 Orion Poplawski 2006-07-27 21:30:13 UTC
This is actually a kernel bug with fcntl(F_SETSIG) no longer working.  I'll file
a kernel bug shortly.


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