moddect stops after 32000 events

Support and queries relating to all previous versions of ZoneMinder
Locked
nickcol
Posts: 26
Joined: Tue Sep 06, 2005 10:08 am
Location: devon,uk

moddect stops after 32000 events

Post by nickcol »

Hi,

Im trying zoneminder 1.21.3 fc3 cd distro.
With 4 x 4port ebay cards btv848 all set to 320x240 on modect.
with 900gb drive storage in a warehouse.

One of our cameras has got 32,000 events on after about 2-3 weeks of recording and the /dev/video2 part is now orange and it will not record anything else even if i restart it.

Is this a limit and can we get around it.?

I do need to keep all the event as I think 30 days worth would be around 65,000 events on most of the cameras.

Does zm support >32000 or is it a mysql table problem which needs bigint.

Thanks

Nick
jameswilson
Posts: 5111
Joined: Wed Jun 08, 2005 8:07 pm
Location: Midlands UK

Post by jameswilson »

i think this is a file system issue as a folder can only hold 32000 folders. I think its an ext2 limitation but i assume ext3 is affected by this too.
BTW 32000 alarms is a lot for mocord. What are you using ay your section length. as 10 mins default = 222 days

James
nickcol
Posts: 26
Joined: Tue Sep 06, 2005 10:08 am
Location: devon,uk

Post by nickcol »

Hi
This camera is in a warehouse at one of the entrances so we do get a lot of store people passing it between 8am and 6-7pm everyday. the other 15 cameras are all up to 20,000+ events and are dotted around the store. So will have the same problem very soon. They hope to keep 1 months data. This camera has run for about 26 days before it hit the 32,000 events.

The section length=600, frame skip=0

image buffer size= 40
warmup frames=25
pre event buffer + post =10


I have tried to mkdir test in the events folder for the camera and got

mkdir: cannot create directory `test': Too many links so it looks like a filesystem.

Are archived events stored in a different folder ? or can I make a filter to
purge some of the events when it gets to 31.000.

Any ideas.

Thanks

Nick
SyRenity
Posts: 301
Joined: Mon Jan 24, 2005 2:43 pm

Post by SyRenity »

Hi.

I think that perhaps converting the FS to ReiserFS might solve the problem. Here is also a link to a similar discussion:

http://www.linuxforums.org/forum/post-305622.html
jameswilson
Posts: 5111
Joined: Wed Jun 08, 2005 8:07 pm
Location: Midlands UK

Post by jameswilson »

you could use mocord as your rwecord type instead of modect and set your frame skip high if your zones are setup correctly
User avatar
zoneminder
Site Admin
Posts: 5215
Joined: Wed Jul 09, 2003 2:07 pm
Location: Bristol, UK
Contact:

Post by zoneminder »

It's not an ext2 limitation per se, but most of the time the filesystem is configured for a comprimise between fewer large files and more smaller ones. You can (when you build a filesystem) specify that you want it more oriented towards one or the other and this can give you the facility to store more files in a directory.

Having said that I think I should look at changing the filesystem storage to prevent this kind of thing happening.

Phil
User avatar
cordel
Posts: 5210
Joined: Fri Mar 05, 2004 4:47 pm
Location: /USA/Washington/Seattle

Post by cordel »

Or maybe just put in the readme the potentail issues, and a small blip about how to optimize a partition for one or the other. Obviously anyone that is running a 1 tair or larger raid system would already be aware of these issues and know how to create the appropriate fs.
We could also put a link here if someone comes accross a good resorce that explain everything and has a good howto.
Regards,
Cordel
Locked