Storage limited to 195.86 GB

[DACS]

I have been using ZoneMinder for some time but have just rebuilt my system with a 1.5 TB HDD as well as the original 0.5 TB HDD. I want to use the 1.5 TB to store event recordings.

The initial installation set up the default storage, /var/cache/zoneminder/events and shows it to be limited t 195.86 GB. I have tried adding a second storage at /var/cache/zoneminder/events2 but this too is limited to 195.86 GB.

Does anyone know where this limit is coming from. Is it a Linux limit or part of Zoneminder and how can I change it?

Also, the original stroage area was showng 94% full on the system health information which was reasonable as I have the default PurgeWhenFull filter set to 95%. However, as soon as I set two of my four cameras to use the new storage area it too jumped to 94% full. Any ideas?

[Magic919]

It's not a ZM limitation.

How have you configured this? Have you switched to the new location?

[DACS]

I have now found that the new storage area appears to be unlimited as it is using more than 195.86 MB.

The statistics from ZoneMinder are very confusing. The system health line reads "Storage: Default: 94% , NewStorage: 94%". NewStorage read 94% before any monitors were assigned to it. The Storage page has the following:
Name DiskSpace Events
Default 183.6GB of 195.86GB 0 using 0B
NewStorage 183.6GB of 195.86GB 41 using 655.72MB

According to Linux, Default occupies 163 GB and NewStorage 662 MB which seem reasonable.

I have four monitors and switched two of them to use NewStorage. Despite the number of events in Default showing as 0, I can still see recordings from the two monitors assigned to Default and the older events from the other two monitors which have been reassigned to NewStorage.

I do not have the quota software installed on my system so I cannot see how Linux can be enforcing any limits.

Anyway, I now have a storage area which appears to be unlimited so I will probably stop using Default and delete once the recordings are ready to be aged off.

[Magic919]

My take is that ZM works best when storage presented once. You can abstract away multiple areas under it,as long as ZM doesn't see those.

Regarding space, I get this -

Code: Select all

621.18GB of 4.42TB

Nothing I can think of created the 621.18GB. Could be a high tide mark for all I know. It has a total of 3.9T free at this time.


This bit shows my events and is correct.

Code: Select all

1012 using 211.32GB

[Andyrh]

Post the output from df To me it looks like your are not pointing to the 2nd HD.

[DACS]

Thanks for your replies.

I have been checking my disk allocation and have discovered a problem with my partitioning. The bulk of my disk space is currently inaccessible. I will sort this out and then see how ZoneMinder behaves.

[DACS]

Here is an update as I have resolved my storage problem.

I installed Ubuntu on a 1.5TB HDD. I configured a Volume Group with just the one HDD as I have another HDD that I may add later. I also configured a Logical Volume which ended up as 1.36 TiB. My storage areas for ZoneMinder were on this LV.

I found today that the File System on the LV was only 205 GB. I do not know where this size came from but I have resized it using resize2fs and it is now 1.36 TiB as required.

Thanks again for your replies.