Bug 424120 - nautilus crashes when copying a 4G file on a vfat volume
nautilus crashes when copying a 4G file on a vfat volume
Status: NEW
Product: gnome-vfs
Classification: Deprecated
Component: Module: file
2.18.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
:
: 456847 (view as bug list)
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2007-03-29 13:58 UTC by Sebastien Bacher
Modified: 2010-10-16 05:44 UTC (History)
3 users (show)

See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments

Description Sebastien Bacher 2007-03-29 13:58:12 UTC
The bug has been opened on https://launchpad.net/bugs/70535

"Occurred while copying an 8GB backup file from an internal HD to a USB HD. The Nautilus process crashed while unattended, likely after the screensaver had kicked in. ("Blank Screen" was selected for the screensaver to reduce CPU load.)
...
 Core was generated by `nautilus --no-default-window --sm-client-id default2'.
 Program terminated with signal 25, File size limit exceeded.
 #0  0xffffe410 in __kernel_vsyscall ()
 .
 Thread 2 (process 4481):
 #0  0xffffe410 in __kernel_vsyscall ()
 No symbol table info available.
 #1  0xb73df803 in poll () from /lib/tls/i686/cmov/libc.so.6
 No symbol table info available.
 #2  0xb75ac813 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
 No symbol table info available.
 #3  0xb75acb89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
 No symbol table info available.
 #4  0xb7ae9574 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
 No symbol table info available.
 #5  0x0807bb4a in POA_Nautilus_MetafileMonitor__init ()
 No symbol table info available.
 #6  0xb73318cc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 No symbol table info available.
 #7  0x08067621 in ?? ()
 No symbol table info available.
 .
 Thread 1 (process 4893):
 #0  0xffffe410 in __kernel_vsyscall ()
 No symbol table info available.
 #1  0xb761b37b in __write_nocancel () from /lib/tls/i686/cmov/libpthread.so.0
 No symbol table info available.
 #2  0xb661b16a in vfs_module_shutdown ()
    from /usr/lib/gnome-vfs-2.0/modules/libfile.so
 No symbol table info available.
 #3  0xb781ca17 in gnome_vfs_find_directory () from /usr/lib/libgnomevfs-2.so.0
 No symbol table info available.
 #4  0xb7814cf8 in gnome_vfs_write_cancellable ()
    from /usr/lib/libgnomevfs-2.so.0
 No symbol table info available.
 #5  0xb782bde1 in gnome_vfs_write () from /usr/lib/libgnomevfs-2.so.0
 No symbol table info available.
 #6  0xb783b0a2 in gnome_vfs_xfer_delete_list ()
    from /usr/lib/libgnomevfs-2.so.0
 No symbol table info available.
 #7  0xb783bbe5 in gnome_vfs_xfer_delete_list ()
    from /usr/lib/libgnomevfs-2.so.0
 No symbol table info available.
 #8  0xb783caf0 in gnome_vfs_xfer_delete_list ()
    from /usr/lib/libgnomevfs-2.so.0
 No symbol table info available.
 #9  0xb783d344 in gnome_vfs_xfer_uri () from /usr/lib/libgnomevfs-2.so.0
 No symbol table info available.
 #10 0xb781f198 in gnome_vfs_job_get_count () from /usr/lib/libgnomevfs-2.so.0
 No symbol table info available.
 #11 0x08969440 in ?? ()
 No symbol table info available.
 #12 0x08954190 in ?? ()
 No symbol table info available.
 #13 0x00000008 in ?? ()
 No symbol table info available.
 #14 0x00000001 in ?? ()
 No symbol table info available.
 #15 0x00000001 in ?? ()
 No symbol table info available.
 #16 0xb781e4e0 in gnome_vfs_job_get_count () from /usr/lib/libgnomevfs-2.so.0
 No symbol table info available.
 #17 0x08947028 in ?? ()
 No symbol table info available.
 #18 0x080f2010 in nautilus_directory_ref ()
 No symbol table info available.
 #19 0xb781dfce in gnome_vfs_async_set_job_limit ()
    from /usr/lib/libgnomevfs-2.so.0
 No symbol table info available.
..."

Debug backtrace on GNOME 2.18.0 (https://launchpad.net/bugs/98577)

".

    
Comment 1 Pedro Villavicencio 2007-08-08 13:13:50 UTC
*** Bug 456847 has been marked as a duplicate of this bug. ***
Comment 2 Yann Rouillard 2007-10-19 23:07:47 UTC
This bug will corrected on the linux kernel side, when a filesystem size limit is reached, an EFBIG error code will be returned instead of a SIGXFSZ being generated.

For more details, see the launchpad bug: https://launchpad.net/bugs/70535

So I think this bug can be closed.
Comment 3 frini123 2010-10-16 05:44:36 UTC
I think that the bug is not a bug,because vfat file systems can´t work with files bigger than 2GB.

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