Forums / Developer / Uploading images via WebDAV = wasting harddisc space?

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Uploading images via WebDAV = wasting harddisc space?

Previous topic

Developer

Next topic

Author	Message
Marco Zinn	Saturday 30 October 2004 10:18:35 am Hi, a long time ago, i posted a bug report (see http://ez.no/community/bug_reports/images_remain_in_images_versioned), because i think, there is a bug with image publishing: Files stay in images-versioned, even, after the image object is published. I think "images-versioned" does not get cleaned of unneed files. Now comes WebDAV: The folder /var/webdav/tmp get filled up with load of eZWebDAVUpload_xxxxx files, which don't seems to get removed. I have a customer, who's using Webdav to upload images. The images are published immediatly (by WebDAV) and probably, 98% of them are never edited. Now, this is the current harddisc usage: var/corporate/storage/image is about 14MB large var/corporate/storage/images-versioned is about 12MB large var/corporate/storage/original is almost 0 (36kb) var/webdav/root is 0 var/webdav/tmp is 67 MB large !!!! I'm using ez 3.4.2 with Webdrive beeing the WebDAV client. Please, someone tell me, how this SHOULD work, and if i can delete the var/webdav/tmp dir! Shouldn't the WebDAV server part of ez _move_ the files from the webdav/tmp dir to somewhere in var/storage ? Why is so much data in images-versioned, when we don't have loads of drafts? Also refer to my bug report, as i think, there are 2 problems: One with a bad cleanup of files in images-versioned (see report) and one with the webdav's tmp dir. Any comment? Is this a know bug? Marco http://www.hyperroad-design.com
Marco Zinn	Sunday 03 April 2005 6:57:36 am Hi, i'm kind of bumping this. We do have some ez 3.4 installations (3.4.4 or so), which make heavy use of image galleries. Because of 2 bugs (i think, these ARE bugs), the harddisc usage is very huge: Webdav does not delete it's temp files (this is fixed in 3.5, but still open in 3.4). Additionally, ez makes copies of (original) images files at every new version of the image object. And, as noone closed my bug reports, i'm almost sure, that ez also does not remove image files for deleted object versions. See these bug reports. http://ez.no/community/bugs/images_remain_in_images_versioned http://ez.no/community/bugs/no_cleanup_for_image_attributes So, my question to the users here: Does anyone use ez 3.4 for image galleries (with of without WebDAV) and has fixed these issues? To the ezCrew: At least the WebDav tmp file issue is solved in 3.5 . Will you backport this eo ez 3.4? Maybe this has already been done, but we're using 3.4.4, rev. 9297, and this still has this bug. Marco http://www.hyperroad-design.com

Author

Message

Marco Zinn

Saturday 30 October 2004 10:18:35 am

Hi,
a long time ago, i posted a bug report (see http://ez.no/community/bug_reports/images_remain_in_images_versioned), because i think, there is a bug with image publishing: Files stay in images-versioned, even, after the image object is published.
I think "images-versioned" does not get cleaned of unneed files.

Now comes WebDAV: The folder /var/webdav/tmp get filled up with load of eZWebDAVUpload_xxxxx files, which don't seems to get removed.

I have a customer, who's using Webdav to upload images. The images are published immediatly (by WebDAV) and probably, 98% of them are never edited.

Now, this is the current harddisc usage:
var/corporate/storage/image is about 14MB large
var/corporate/storage/images-versioned is about 12MB large
var/corporate/storage/original is almost 0 (36kb)
var/webdav/root is 0
var/webdav/tmp is 67 MB large !!!!

I'm using ez 3.4.2 with Webdrive beeing the WebDAV client.

Please, someone tell me, how this SHOULD work, and if i can delete the var/webdav/tmp dir!

Shouldn't the WebDAV server part of ez _move_ the files from the webdav/tmp dir to somewhere in var/storage ?
Why is so much data in images-versioned, when we don't have loads of drafts?
Also refer to my bug report, as i think, there are 2 problems: One with a bad cleanup of files in images-versioned (see report) and one with the webdav's tmp dir.

Any comment? Is this a know bug?

Marco
http://www.hyperroad-design.com

Marco Zinn

Sunday 03 April 2005 6:57:36 am

Hi,
i'm kind of bumping this. We do have some ez 3.4 installations (3.4.4 or so), which make heavy use of image galleries.

Because of 2 bugs (i think, these ARE bugs), the harddisc usage is very huge: Webdav does not delete it's temp files (this is fixed in 3.5, but still open in 3.4).
Additionally, ez makes copies of (original) images files at every new version of the image object. And, as noone closed my bug reports, i'm almost sure, that ez also does not remove image files for deleted object versions.

See these bug reports.
http://ez.no/community/bugs/images_remain_in_images_versioned
http://ez.no/community/bugs/no_cleanup_for_image_attributes

So, my question to the users here: Does anyone use ez 3.4 for image galleries (with of without WebDAV) and has fixed these issues?

To the ezCrew: At least the WebDav tmp file issue is solved in 3.5 . Will you backport this eo ez 3.4? Maybe this has already been done, but we're using 3.4.4, rev. 9297, and this still has this bug.

Marco
http://www.hyperroad-design.com