pyexiv2 fails on cifs shares served by win2k8-servers
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyexiv2 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
first off, i do not think that this is pyexiv's fault, but i do think that this issue should be reported somewhere …
this code:
meta_source = pyexiv2.
meta_dest = pyexiv2.
print "hier …"
print "… hängt es"
hangs at meta_dest.write() iff:
- out_fn points to a file on a cifs share mounted from a win2k8 server
- the jpeg file referenced by meta_dest is larger than ~100kb
meta_dest.write() does not hang if:
- meta_dest is bigger than 100k and resides on a cifs share served by a samba server or a local file system
- meta_dest is smaller than 100k and resides on either cifs share
- meta_dest is bigger than 100k, resides on a cifs share served by the infamous win2k8 server and the python process executing the script is being strace'd
- meta_dest is bigger than 100k, resides on a cifs share served by the infamous win2k8 server and the share is mounted with mount.cifs' "cache=none"-option
a look at self._image.
the pyexiv2 version i am using is the one in the debian wheezy repositores (0.3.2-5 linked against libexiv2-12 0.23-1).
with kind regards,
t.
Thanks for the detailed report. pyexiv2 is not actively maintained any longer, it has been deprecated in favour of https:/ /wiki.gnome. org/Projects/ gexiv2.
As you point out, it looks like the issue could be in exiv2 itself. You might want to file a bug with all those details at http:// dev.exiv2. org/projects/ exiv2/issues.