Bug 580079 - [abrt] crash in gvfs-smb-1.4.3-7.fc12: Process /usr/libexec/gvfsd-smb was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gvfs-smb-1.4.3-7.fc12: Process /usr/libexec/gvfsd-smb was kil...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4d98fce2194e18b44e6d747418d...
: 569102 572804 587597 594908 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-07 12:43 UTC by Alexey Kazakov
Modified: 2015-03-03 22:46 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 16:14:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (8.62 KB, text/plain)
2010-04-07 12:43 UTC, Alexey Kazakov
no flags Details

Description Alexey Kazakov 2010-04-07 12:43:43 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-smb --spawner :1.7 /org/gtk/gvfs/exec_spaw/4
component: gvfs
executable: /usr/libexec/gvfsd-smb
kernel: 2.6.32.10-90.fc12.x86_64
package: gvfs-smb-1.4.3-7.fc12
rating: 4
reason: Process /usr/libexec/gvfsd-smb was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

comment
-----
I was copying a very large number of files (several hundred thounsands files amounting to 144Gb)
 to Windows Server 2007 share. At some point I got this error and SMB share was no longer mounted.

Comment 1 Alexey Kazakov 2010-04-07 12:43:45 UTC
Created attachment 404945 [details]
File: backtrace

Comment 2 smashfedorabugz 2010-04-09 06:02:47 UTC

How to reproduce
-----
1. Samba file transfer of over 3 GB caused this somehow
2.
3.

Comment 3 Tomáš Bžatek 2010-04-09 10:17:38 UTC
(In reply to comment #2)
> 
> How to reproduce
> -----
> 1. Samba file transfer of over 3 GB caused this somehow
> 2.
> 3.    

Can you be more specific? What file manager did you use? What is the server running on? Can you grab output of `GVFS_DEBUG=1 /usr/libexec/gvfsd -r`?

Comment 4 Niels 2010-04-11 14:26:10 UTC

Comment
-----
I copied a directory with thousands of files (multiple GB of pictures) to my NAS.
With smaller numbers, there was no problem. With big numbers it crashes quite often.

Comment 5 Alexey Kazakov 2010-04-12 08:23:58 UTC
(In reply to comment #3)
> 
> Can you be more specific? What file manager did you use? What is the server
> running on? Can you grab output of `GVFS_DEBUG=1 /usr/libexec/gvfsd -r`?    

In my case I used Nautilus file manager (v. 2.28.4 - current stable one from Fedora 12), server running Win Server 2007, and as for grabbing output of command given - I fear that I need a bit more detailed instructions on how to do it.

Do I need to run it in the terminal and then reproduce the error - will it generate the output that interests you?

Comment 6 smashfedorabugz 2010-04-12 23:04:39 UTC

How to reproduce
-----
1. Init SMB file transfer of multiple directories and files from Windows 2008 server running DFS
2. transfer gets half-way through then fails.
3.

Comment 7 Tomáš Bžatek 2010-04-13 11:30:43 UTC
(In reply to comment #5)
> Do I need to run it in the terminal and then reproduce the error - will it
> generate the output that interests you?    
Yes please. Can you also post version of the libsmbclient package?

Comment 8 Alexey Kazakov 2010-04-19 08:32:09 UTC

How to reproduce
-----
Copy some large amount of files using Nautilus to SMB share.
Sometimes (not very often) you'll get this error.

Comment
-----
Server OS is Windows Server 2008 service pack 2 (sorry for misspelling it last time).
libsmbclient package version is 3.4.7-58.fc12 (x86_64) -- must be current version from Fedora 12 stable repository.
'GVFS_DEBUG=1 /usr/libexec/gvfsd -r' output is (about two last pages of it):

=============

Queued new job 0x7f4e40091810 (GVfsJobSetAttribute)
send_reply(0x7f4e40091810), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:Push
Remove Source: false
Queued new job 0x7f4e40091bd0 (GVfsJobPush)
send_reply(0x7f4e40091bd0), failed=1 (Действие не поддерживается драйвером)
backend_dbus_handler org.gtk.vfs.Mount:QueryInfo
Queued new job 0x16ae1e0 (GVfsJobQueryInfo)
send_reply(0x16ae1e0), failed=1 (Нет такого файла или каталога)
backend_dbus_handler org.gtk.vfs.Mount:MakeDirectory
Queued new job 0x16bbca0 (GVfsJobMakeDirectory)
send_reply(0x16bbca0), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:Push
Remove Source: false
Queued new job 0x7f4e40091d10 (GVfsJobPush)
send_reply(0x7f4e40091d10), failed=1 (Действие не поддерживается драйвером)
backend_dbus_handler org.gtk.vfs.Mount:OpenForWrite
Queued new job 0x16babf0 (GVfsJobOpenForWrite)
send_reply(0x16babf0), failed=0 ()
Added new job source 0x7f4e40091810 (GVfsWriteChannel)
Queued new job 0x16b9180 (GVfsJobWrite)
job_write send reply
backend_dbus_handler org.gtk.vfs.Mount:QueryInfo
Queued new job 0x7f4e40091e50 (GVfsJobQueryInfo)
send_reply(0x7f4e40091e50), failed=0 ()
Queued new job 0x16b94e0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a5180 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a54e0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a52a0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a5450 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9450 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9450 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a5450 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a52a0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a54e0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a5180 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b94e0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9180 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9450 (GVfsJobWrite)
job_write send reply
Queued new job 0x16bbd20 (GVfsJobCloseWrite)
job_close_write send reply
backend_dbus_handler org.gtk.vfs.Mount:QuerySettableAttributes
Queued new job 0x16b9600 (GVfsJobQueryAttributes)
send_reply(0x16b9600), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:QueryWritableNamespaces
Queued new job 0x16a5330 (GVfsJobQueryAttributes)
send_reply(0x16a5330), failed=1 (Действие не поддерживается драйвером)
backend_dbus_handler org.gtk.vfs.Mount:SetAttribute
Queued new job 0x7f4e40091a90 (GVfsJobSetAttribute)
send_reply(0x7f4e40091a90), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:Push
Remove Source: false
Queued new job 0x7f4e40091b30 (GVfsJobPush)
send_reply(0x7f4e40091b30), failed=1 (Действие не поддерживается драйвером)
backend_dbus_handler org.gtk.vfs.Mount:OpenForWrite
Queued new job 0x16bacb0 (GVfsJobOpenForWrite)
send_reply(0x16bacb0), failed=0 ()
Added new job source 0x7f4e400919f0 (GVfsWriteChannel)
Queued new job 0x16cb8c0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b90f0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a53c0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a5720 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9060 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a5570 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9720 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9330 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a5690 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9330 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9720 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a5570 (GVfsJobWrite)
job_write send reply
Queued new job 0x16be210 (GVfsJobCloseWrite)
job_close_write send reply
backend_dbus_handler org.gtk.vfs.Mount:QuerySettableAttributes
Queued new job 0x16b9060 (GVfsJobQueryAttributes)
send_reply(0x16b9060), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:QueryWritableNamespaces
Queued new job 0x16a5720 (GVfsJobQueryAttributes)
send_reply(0x16a5720), failed=1 (Действие не поддерживается драйвером)
backend_dbus_handler org.gtk.vfs.Mount:SetAttribute
Queued new job 0x7f4e400919f0 (GVfsJobSetAttribute)
send_reply(0x7f4e400919f0), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:Push
Remove Source: false
Queued new job 0x16ae6e0 (GVfsJobPush)
send_reply(0x16ae6e0), failed=1 (Действие не поддерживается драйвером)
backend_dbus_handler org.gtk.vfs.Mount:OpenForWrite
Queued new job 0x16bad70 (GVfsJobOpenForWrite)
send_reply(0x16bad70), failed=0 ()
Added new job source 0x16ae0a0 (GVfsWriteChannel)
Queued new job 0x16a53c0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16be110 (GVfsJobCloseWrite)
job_close_write send reply
backend_dbus_handler org.gtk.vfs.Mount:QuerySettableAttributes
Queued new job 0x16cb8c0 (GVfsJobQueryAttributes)
send_reply(0x16cb8c0), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:QueryWritableNamespaces
Queued new job 0x16b9600 (GVfsJobQueryAttributes)
send_reply(0x16b9600), failed=1 (Действие не поддерживается драйвером)
backend_dbus_handler org.gtk.vfs.Mount:SetAttribute
Queued new job 0x7f4e40091950 (GVfsJobSetAttribute)
send_reply(0x7f4e40091950), failed=0 ()
backend_dbus_handler org.gtk.vfs.Mount:Push
Remove Source: false
Queued new job 0x16ae500 (GVfsJobPush)
send_reply(0x16ae500), failed=1 (Действие не поддерживается драйвером)
backend_dbus_handler org.gtk.vfs.Mount:OpenForWrite
Queued new job 0x16bae30 (GVfsJobOpenForWrite)
send_reply(0x16bae30), failed=0 ()
Added new job source 0x16ae0a0 (GVfsWriteChannel)
Queued new job 0x16cb8c0 (GVfsJobWrite)
job_write send reply
backend_dbus_handler org.gtk.vfs.Mount:QueryInfo
Queued new job 0x7f4e40091c70 (GVfsJobQueryInfo)
send_reply(0x7f4e40091c70), failed=0 ()
Queued new job 0x16a53c0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9060 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a5570 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9720 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9330 (GVfsJobWrite)
job_write send reply
Queued new job 0x16b9330 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a53c0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16cb8c0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16a53c0 (GVfsJobWrite)
job_write send reply
Queued new job 0x16bbe20 (GVfsJobCloseWrite)
job_close_write send reply

==================

Words in parentheses are:
Действие не поддерживается драйвером = Action isn't supported by driver - (multiple entries)
Нет такого файла или каталога = There is no such file or folder - (once, close to the top)

I tried to reproduce this error for about three or five days - and had no success in it (all operations were completed successfully).
This time I was trying to copy 2 folders (10 685 objects, 44,3 Gb total) -- again I have successfully copied jast the same two folders on several previous attempts.

Comment 9 Alexey Kazakov 2010-04-19 08:44:28 UTC
A bit more info: 
When this error happens mountpoint for network share in Nautilus (in Places menu) disappears, and the nautilus process gets 100% CPU load until you kill it.

Comment 10 Karel Klíč 2010-05-25 10:09:45 UTC
*** Bug 569102 has been marked as a duplicate of this bug. ***

Comment 11 Karel Klíč 2010-05-25 10:09:50 UTC
*** Bug 572804 has been marked as a duplicate of this bug. ***

Comment 12 Karel Klíč 2010-05-25 10:09:54 UTC
*** Bug 587597 has been marked as a duplicate of this bug. ***

Comment 13 Karel Klíč 2010-05-25 10:09:58 UTC
*** Bug 594908 has been marked as a duplicate of this bug. ***

Comment 14 Bug Zapper 2010-11-03 17:41:27 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 15 Niels 2010-11-03 19:43:00 UTC
Well, I don't manage to reproduce this with Fedora 13, so I guess this is fixed by now.

Comment 16 Alexey Kazakov 2010-11-11 14:07:38 UTC
(In reply to comment #15)

Niels, I haven't really tried to reproduce it, but just now have got a crash with very similar features -- at least from what I can see happening in UI.
I filed it with abrt, it's bug 652258.

One more notion: it was quite hard to reproduce last time (in april). I've tried for several days and have copied gygabytes of data without any errors - and at last had got it again -- but again just once.

If bug 652258 has any relation to this one -- then I've got this error (or two very similar-looking errors) just twice in my normal workflow. I'm not using samba _very_ intensively, but I have to copy some data there and back again quite often.

I.e. that error is quite rare, if it's reproduceable at all.

Comment 17 Niels 2010-11-11 16:44:53 UTC
For me that error was really frequent. I.e. it happened every time I tried to copy more than a few hundred files at once.
Now it doesn't happen at all for me (or it is really infrequent, so that I don't see it anymore).

Comment 18 Bug Zapper 2010-12-03 16:14:01 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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