GNOME Bugzilla – Bug 557835
Erroneous mount error when mounting large (1TB) volume over slow (USB1.1) bus due to DBus timeout
Last modified: 2018-09-21 16:29:42 UTC
Please describe the problem: Nautilus is prematurely (and incorrectly) reporting that it failed to mount my 1TB external HDD because DBus times out waiting for a reply. Even though the mount is eventually successful, it's a large NTFS volume over a slow bus (USB1.1) so the mount takes a little longer than most other mounts (manually mounting with mount takes just as long), causing DBus to raise a 'No Reply' error prematurely. There don't appear to be any other effects. Not sure which package is responsible but I was directed to gvfs by the Ubuntu bug team. Steps to reproduce: 1. Connect external HDD and let it automount. Actual results: Nautilus reports this error: Unable to mount 1000.2 GB Media DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. The mount is in fact successful after a few seconds longer. Expected results: No error unless there really is an error mounting the filesystem. Does this happen every time? Yes. Other information: Perhaps, instead of reporting an error when DBus times out waiting for a reply, bring up a 'Waiting...' dialog like metacity shows when an application is taking too long to close, just in case nothing is wrong and things are just slow.
How long does it take ?
Running 'time mount ...' reports it consistently takes 30.5 seconds to mount, of which 90% is spent in iowait. Manual timing with a stopwatch of the nautilus/gvfs mount also takes 31 seconds, with DBus complaining about no reply after about 25 seconds. Incidentally, mounting on a *much* older machine, but with USB2.0, takes only 10 seconds, which together with the reported time spent in iowait, confirms the slow bus to be the cause. Of course this isn't really all that important as this isn't what the bug is about :)
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/68.