Not 100% sure, but I think it might use some temp space during scan for changes and then cleans up after itself before it completes. Maybe this just stopped when it filled up the filesystem and never cleaned up.
Is growing the FS and trying a snapvault update an option? Since you have a baseline of 60TB, you might want to wait for a few other comments before trying something that might worsen your situation.
Good luck and good weekend.
--Jordan
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Jeff Cleverley Sent: Friday, April 11, 2014 4:42 PM To: Toasters@teaparty.net Subject: OSSV server database cleanup
Greetings, I was hoping for a quick fix since it is Friday afternoon. If nothing works out I may open a call or just wipe everything out. We have OSSV3.0 running on a linux server. It is installed on / and filled up / today. I found a -checksums file dated today that is 30G. There is another one for the same date last month of the same size. No other checksums file is larger than 10G. The file system that backups up on the 11th of the month is smaller and has considerably fewer inodes in use than most others. There is no reason it should be 3x the size of any other checksums file. There are no current snapvault transfers running and I've stopped/started snapvault. I have several checksums files on dated when backups don't even run. I also found out that / is not backed up so I have no old backups of the database.
Is there a way to do a purge or cleanup of the database? If not, I guess I'll just uninstall and start fresh. Unfortunately that is a baseline of 60+TB. I'll install snapvault somewhere other than / also :-) Thanks,
Jeff
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611