#17 — errant files in var/blobstorage prevents packing the ZODB

by John Samuel Anderson — last modified Mar 17, 2009 09:39 AM

State	Rejected
Version:	1.0
Area	Functionality
Issue type	Bug
Severity	Medium
Submitted by	John Samuel Anderson
Submitted on	Mar 16, 2009
Responsible	—
Target release:	—

Return to tracker

When non-hex-code filenames are present in the same directory where blobs are stored, the database pack fails. There are two likely causes:

1. The ".layout" file - sometimes blobstorage itself puts a .layout file in this directory. 2. Other processes may put files in this directory, including backup tar-balls, cron jobs, and random user files.

This bug and the location of the problem are nailed down in this document:

http://plone.org/[…]/nailing-down-the-bug

Possible fixes: 1. Just ignore non-hex-code filenames. 2. Include a README.txt document that details the problem. (And ignore this file, of course.) 3. Have a better explanation than the "blobstorage has insecure mode setting" warning on zope startup.

Steps to reproduce:: 1. Put an errant file or directory in var/blobstorage.
2. Try to pack the ZODB, either via the ZMI or zeopack.py.
3. It will fail silently, leaving only this cryptic message in the logs: "Odd-length string"

Added by Andreas Zeidler on Mar 17, 2009 09:39 AM

Issue state: Unconfirmed → Rejected

hi john,

unfortunately this is nothing `plone.app.blob` can fix — the problem is related to the ZODB itself. iow, you should really report this bug at https://launchpad.net/zodb

cheers,

andi

No responses can be added.