Hi...
My inode is almost 100% full with only 71% usage of the filesystem (ext3). Since I use my ZM server also for a weekly backup of my network documents, is there a way to create a PurgeWhenFull-like filter that checks the inode usage instead of the filesystem usage ('df -i /dev/sda1' command)?
Thanks!!
Inode problem - PurgeWhenFull filter
The good news is that mkfs (actually mkfs.ext3) lets you choose some options during the file system creation. Use mkfs.ext3 with the -T option taking arguments like small, floppy, news, largefile, or largefile4. You probably need small or news. Otherwise you can specify the bytes/inode ratio directly, via option -i.
The bad news are:
it's a lot of easier to do if you keep ZM events on a separate HD, don't you?
mkfs is destructive - it will destroy all your data. Have another disk for the backup.
A somewhat neutral news is that it's better to keep MySQL databases elsewhere and not on the disk where event jpg's are stored. Because - the speed/inode requirements against db and jpeg are quite different.
The bad news are:
it's a lot of easier to do if you keep ZM events on a separate HD, don't you?
mkfs is destructive - it will destroy all your data. Have another disk for the backup.
A somewhat neutral news is that it's better to keep MySQL databases elsewhere and not on the disk where event jpg's are stored. Because - the speed/inode requirements against db and jpeg are quite different.
Yeah...well...when I installed it in my server (dedicated for ZM, by the way) I didn't know ZM recorded the videos frame by frame, so I didn't really thought the inode would be overwhelmed...otherwise I would have used a bigger inode or another filesystem type (ReiserFS, for example)...and I also didn't separate anything...it's all in the same FS, because I thought I would have time to make a new installation after I tried this one...
But now the system is live and running for 6 months so I can't afford to shut it down (and don't have time to do it, also)...so a filter that checks the inode usage instead of the fs usage would be perfect, as I intend to use the extra space for weekly network files backup (30~40 GB)...
Any ideas whatsoever?
Thanks!
But now the system is live and running for 6 months so I can't afford to shut it down (and don't have time to do it, also)...so a filter that checks the inode usage instead of the fs usage would be perfect, as I intend to use the extra space for weekly network files backup (30~40 GB)...
Any ideas whatsoever?
Thanks!