ZoneMinder Forums

Hi.

I finally got hit by the 32K ext3 limit as well. I would like to know if there any option to make a smooth, low downtime switch to another FS, without reformatting the whole system (I have 400GB worth of events). Perhaps it is possible to set a XFS, and then set the ZM to work with it like a regular share?

Will appreciate any help on the matter.

I can't help with your query directly. But I thought I'd mention that I will be changing to a different file structure in a version or two to try and prevent this kind of thing from happening.

Phil

Hi.

Great news Phil - there are a lot of people who just install the default ext3 FS, without even knowing about this limit (as I did), and it's complication with ZM.

I have switched to reiser and have had no issues. You might be able to create a new fs on a lvm and then grow it assuming that the other partition is also on a lvm.
I have not tried it.

Regards,
Corey

I would think that a note in the README would be sufficient - a heck of a lot less work than changing the file structure of the application. Also, please do not remove the feature that stores all the individual frames independantly. Legally, these are much more effective than mpeg video, as mpeg is refresh-dependant. I burnt a CD for the cops in the past and they came back and wanted the full frames as well.

I haven't tried this, but QtParted has an option to resize NTFS partitions. I don't know, but you might want to check it out and see if it can convert between file system types. (The last time I used it to split an NTFS partition, I remember seeing something in it that made me think of a similar thread here; senility has set in though and I can't remember what it was.)

Hi.

This might do the trick: convertfs (http://tzukanov.narod.ru/convertfs/). Various references - http://gentoo-wiki.com/HOWTO_Convert_Filesystems, http://directory.fsf.org/sysadmin/misc/ConvertFS.html, http://members.optusnet.com.au/clausen/ ... vertfs.txt.

Any idea how this will work on Fedora?

I will add a note to the README anyway, that's a good idea. I wasn't planning to remove individual JPEG storage but just to do something like moving the events to another level down divided by day or something. So instead of as now

events/MyMonitor/12345

it would be

events/MyMonitor/20051213/12345

or

events/MyMonitor/2005/12/13/10/17/23/12345

to take it to an extreme. This would prevent any directory from getting anywhere near the 32k limit and would also facilitate a couple of other features that are in the pipeline.

Phil

might also allow syncronised playback me thinks )