"[Errno 11] Resource temporarily unavailable" retrieving file attributes

37 views
Skip to first unread message

Robert Edmonds

unread,
Sep 19, 2013, 8:09:51 PM9/19/13
to bup-...@googlegroups.com
hi,

i'm backing up a file server that happens to be running a samba server.
i just got the following error from a backup run:

Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 237, in <module>
update_index(rp, excluded_paths)
File "/usr/lib/bup/cmd/bup-index", line 132, in update_index
meta = metadata.from_path(path, statinfo=pst)
File "/usr/lib/bup/bup/metadata.py", line 751, in from_path
result._add_linux_attr(path, st)
File "/usr/lib/bup/bup/metadata.py", line 528, in _add_linux_attr
attr = get_linux_file_attr(path)
OSError: [Errno 11] Resource temporarily unavailable: '/srv/share/os/debian-fsi.iso'

that looks like a file that one of our SMB/CIFS clients has open:

# lsof -n | grep debian-fsi
smbd 10252 root 26r REG 9,0 15656960 2359366 /srv/share/os/debian-fsi.iso

i would guess samba is doing some sort of locking that's preventing bup
from retrieving the file attributes. this is a read-only file share, so
i'm going to try setting "locking = no" in the samba config, but maybe
there's something bup needs to do too.

--
Robert Edmonds
edm...@debian.org

Rob Browning

unread,
Sep 20, 2013, 2:09:54 PM9/20/13
to bup-...@googlegroups.com
Robert Edmonds <edm...@debian.org> writes:

> that looks like a file that one of our SMB/CIFS clients has open:
>
> # lsof -n | grep debian-fsi
> smbd 10252 root 26r REG 9,0 15656960 2359366 /srv/share/os/debian-fsi.iso
>
> i would guess samba is doing some sort of locking that's preventing bup
> from retrieving the file attributes. this is a read-only file share, so
> i'm going to try setting "locking = no" in the samba config, but maybe
> there's something bup needs to do too.

Perhaps also related:

https://bugzilla.redhat.com/show_bug.cgi?id=839294

...which seems to suggest there are timeout related options you can set
too.

Offhand, I'm not sure we should try to special case this, and even if
so, that's likely to be a lot more work, and not something we'd want to
attempt before 0.25.

For whatever it's worth, a quick grep of the tar source doesn't indicate
that it has any specific accommodations for EAGAIN or EWOULDBLOCK.

--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
Reply all
Reply to author
Forward
0 new messages