Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted

Bug #1600299 reported by Peter Munch-Ellingsen on 2016-07-08
This bug affects 27 people
Affects Status Importance Assigned to Milestone
Déjà Dup
deja-dup (Mandriva)
deja-dup (Ubuntu)

Bug Description

I've got my system set up with off-site backup over sftp. This works fine but the problem is that while deja-dup is gathering files and calculating the backup delta the connection to the server times out. This means that it's not available when deja-dup actually tries to push files to the server and results in this error message:

Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted (16)

By sitting in the file manager and jumping between folders the connection can be kept alive but that's rather annoying and requires my presence. Would really like to see deja-dup actually trying to set up the connection again instead.

Manjaro 16.06.1
deja-dup 34.2-1

Stephan Henningsen (zta77) wrote :

Yes, Deja-dup is indeed gathering files, calculating and doing some really time-consuming work. I can only speculate about what's going on behind the scenes. Fact is that I've had Deja-dup working for years on Ubuntu 14.04 and after I upgraded to 16.04 I'm getting this error. Bummer.

Stephan Henningsen (zta77) wrote :

This bug currently only has a bug heat score of 10. But I since this is a very serious application taking care of very serious business, namely BACKUP, I really think this should have higher priority!

MichaeL. (m-langerhorst-t) wrote :

I have the same effect, have a NAS with an SMB-connection to it.
Under 14.04 everything worked fine with the same NAS. Now I also have this ugly error.

MichaeL. (m-langerhorst-t) wrote :

My error-output is in german and it says:
Nach 5 Versuchen wird aufgegeben. Error: g-io-error-quark: Das Argument ist ungültig (13)

Matej Kovacic (matej-kovacic) wrote :

I have the same problem with DejaDup on Ubuntu 16.04. It is weird, because it is very unlikely that my ssh (sftp) connection drops. Usually it is active all the time.

P. S. Is DejaDup still under active development???

Elias Aarnio (elias-aarnio) wrote :

I am running 64-bit 16.04 and I am getting error message "Giving up after 5 attempts. Error: g-io-error-quark: Toiminto epäonnistui (0)"

Toiminto epäonnistui is Finnish for "function failed" or "activity failed".

I am backing up to a server in home network with good old ftp. SSH cannot be the issue here.

123vier (flowrist) wrote :

"Giving up after 5 attempts. Error:g-io-error-quark:
The specified location is not mounted (16)"

on 16.04.1. Backup via sftp. This error only occurs when trying to backup data more than a few GB. A test with just a few MB succeeds, so this looks a lot like an SSH timeout problem.

Vej (vej) wrote :

Setting to "Confirmed", because this bug affects several users.

Changed in deja-dup:
status: New → Confirmed
Changed in deja-dup (Ubuntu):
status: New → Confirmed
tags: added: xenial
Vej (vej) wrote :

Can someone affected by this please provide the following informations?

1. The distribution of Linux you're using:
    lsb_release -d

2. The version of deja-dup and duplicity:
    (if on Ubuntu or Debian:)
    dpkg-query -W deja-dup duplicity

    (if on Fedora or other RPM-based systems:)
    rpm -q deja-dup duplicity

3. The file /tmp/deja-dup.gsettings after running the following line (you may want to scrub the file of any incriminating file names or details):
    gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

4. The file /tmp/deja-dup.log after running the appropriate line below and replicating the problem (you may want to scrub the log of any incriminating file names or details):

    DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log

Please set the "Status" field back to "Confirmed" after doing this.

Changed in deja-dup (Ubuntu):
status: Confirmed → Incomplete
Changed in deja-dup:
status: Confirmed → Incomplete

➤ lsb_release -d
Description: Mageia 5

➤ rpm -q deja-dup duplicity

Find the deja-dup.gsettings attached, but the deja-dup.log is empty.

Changed in deja-dup:
status: Incomplete → Confirmed

Now I managed to replicate the bug when restoring:

➤ DEJA_DUP_DEBUG=1 deja-dup --restore | tail -n 1000 > /tmp/deja-dup.log

Please find the log attached.

Vej (vej) on 2017-03-12
Changed in deja-dup:
status: Confirmed → Triaged
Changed in deja-dup (Ubuntu):
status: Incomplete → Confirmed
Changed in deja-dup:
importance: Undecided → High
Changed in deja-dup (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Jeroen Evens (loggfreak) wrote :

same issue
backup was working fine 2 weeks ago, now it started giving this error
Ubuntu 18.04

Florian W. (florian-will) wrote :

I see this in journalctl at approx. the time of this "giving up after 5 attempts", I also use sftp: (where XXX is my user name)

Okt 25 17:51:09 XXX kernel: gvfsd-sftp[10782]: segfault at 55b300000002 ip 00007f0a424e63ae sp 00007fffe1c32c00 error 4 in[7f0a4246e000+178000]
Okt 25 17:51:09 XXX kernel: Code: 84 5c ff ff ff 0f 1f 80 00 00 00 00 48 8d 0c 58 0f b7 11 66 85 d2 0f 84 45 ff ff ff 48 8d 04 d8 83 ea 01 4c 8b 80 80 00 00 00 <49> 8b 30 48 89 b0 80 00 00 00 66 8

The most annoying part about this bug is that it leaves the user guessing what's going on. I did not know if it is an issue with local or remote system. Speculating that deleting excluded folders might be triggering the issue etc.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers