[Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2016-02-06 Thread Adam Niedling
I don't have this issue anymore. Something has changed, either on the client or on the server side. ** Changed in: gvfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu.

[Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-10-19 Thread Adam Niedling
** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1408107 Title: Can't remove huge files from samba share on first attempt - Input/output error To manage

[Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-03-08 Thread Ross Lagerwall
I've seen at least once before an embedded Samba server which crashed due to the client's access pattern, even though the client was sending valid commands. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu.

[Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-02-22 Thread Adam Niedling
This issue of timing out does not happen when I use Windows and delete the files from there the router being an attached network drive. So I believe the problem is not on the server side, there must be something wrong in Ubuntu. -- You received this bug notification because you are a member of

[Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-02-18 Thread Ross Lagerwall
Unfortunately, gvfs can't control the timeouts that libsmbclient uses. I recommend filing a bug at https://bugzilla.samba.org/ or asking a question on the mailing list: https://lists.samba.org/mailman/listinfo/samba Alternatively, you could try poke about on the router and see what is happening,

[Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-02-17 Thread Adam Niedling
The timeout happens in about 10 seconds. It does not happen if I upload/download something to/from the server. It's a Samba server running on a Asus RT-N66U router. (Firmware: 3.0.0.4.376_3754 (latest), the Samba server is stock) -- You received this bug notification because you are a member

[Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-02-17 Thread Ross Lagerwall
I don't think this is a gvfs issue, the timeout is coming from libsmbclient which gvfs uses to communicate with the server. Deleting a file should be quick though so timing out is strange. How long does it take to timeout? Maybe there's something strange happening like the server crashing which

[Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-02-16 Thread Adam Niedling
There you go. ** Attachment added: log.txt https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1408107/+attachment/4320625/+files/log.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu.

[Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-02-16 Thread Adam Niedling
I just realized that the error messages are in Hungarian in that log file. Let me know if you want me to change the system language back to English and redo the test. However I see a timeout error message: send_reply(0x8b3940), failed=1 (Időtúllépés a kapcsolatban) meaning: timeout in the

[Bug 1408107] Re: Can't remove huge files from samba share on first attempt - Input/output error

2015-02-01 Thread Ross Lagerwall
Please run the following in a terminal: pkill gvfs; GVFS_DEBUG=all GVFS_SMB_DEBUG=10 `find /usr/lib* -name 'gvfsd'` ~/log.txt Then mount the smb share, reproduce the problem, and then upload log.txt in your home directory so we can see a log of what is happening. -- You received this bug