Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: IOError(6, 'No such device or address') #88

Open
jjumpm2 opened this issue Feb 1, 2015 · 2 comments
Open

Error: IOError(6, 'No such device or address') #88

jjumpm2 opened this issue Feb 1, 2015 · 2 comments

Comments

@jjumpm2
Copy link

jjumpm2 commented Feb 1, 2015

Hi,

CentOS 7, trying to set up a server backup and get the following:

0 0% 0.00B/s 0:00:00DEBUG: IOError(6, 'No such device or address'): File "/usr/lib/python2.7/site-packages/libgsync/crawler.py", line 150, in run
self._walk(srcpath, self._walkCallback, self._dev)
File "/usr/lib/python2.7/site-packages/libgsync/crawler.py", line 124, in _walk
self._sync(f)
File "/usr/lib/python2.7/site-packages/libgsync/sync/init.py", line 31, in call
self._sync(path)
File "/usr/lib/python2.7/site-packages/libgsync/sync/init.py", line 197, in _sync
self.dst.update(dstPath, srcFile)
File "/usr/lib/python2.7/site-packages/libgsync/sync/file/init.py", line 325, in update
self.updateFile(path, srcObj)
File "/usr/lib/python2.7/site-packages/libgsync/sync/file/__init
.py", line 227, in updateFile
self._updateFile(path, src)
File "/usr/lib/python2.7/site-packages/libgsync/sync/file/remote/__init
.py", line 110, in _updateFile
info = drive.update(path, info, src.getUploader(), progress)
File "/usr/lib/python2.7/site-packages/libgsync/sync/file/local/init.py", line 18, in getUploader
f = open(path, "r")

Error: IOError(6, 'No such device or address')
sent 1668508191 bytes received 0 bytes 4076189.77 bytes/sec

@nilesr
Copy link

nilesr commented Apr 26, 2016

Having this error too, arch linux. Seems to be just one file in my home directory, when I try to sync other directories it works.

@nilesr
Copy link

nilesr commented Apr 26, 2016

Ok turns out the file was called .MumbleOverlayPipe, and was probably a pipe, explains why it couldn't be read.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants