Is anyone using the data in the bcfg2_reports database on spock? If I don't get any replies I'm going to archive it and clear it out. ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055 ----- Forwarded Message ----- From: "root" <[email protected]> To: [email protected] Sent: Monday, June 21, 2010 10:55:48 PM GMT -06:00 US/Canada Central Subject: [backup-admins] MySQL@spock backup mysqldump: Got errno 28 on write gzip: /sandbox/backup/mysql_dbs/bcfg2_reports.20100621220002.dump.gz: No space left on device mysqldump: Got errno 28 on write gzip: /sandbox/backup/mysql_dbs/mysql.20100621220002.dump.gz: No space left on device Backup # 1 = bcfg2_reports.20100621220002.dump -> 46809354240 bytes Backup # 2 = bcfg2_reports.20100620220001.dump -> deleted Backup # 1 = information_schema.20100621220002.dump.gz -> 465 bytes Backup # 2 = information_schema.20100620220001.dump.gz -> deleted Backup # 1 = mysql.20100621220002.dump -> 0 bytes Backup # 2 = mysql.20100620220001.dump -> deleted
there is a new compressor/deduplicator command in bcfg2-1.1.0rc3 that you might try running on the db; it should really cut down on the amount of data that is stored. -nld On Jun 22, 2010, at 8:07 AM, Dan Olson wrote:
Is anyone using the data in the bcfg2_reports database on spock? If I don't get any replies I'm going to archive it and clear it out.
---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055
----- Forwarded Message ----- From: "root" <[email protected]> To: [email protected] Sent: Monday, June 21, 2010 10:55:48 PM GMT -06:00 US/Canada Central Subject: [backup-admins] MySQL@spock backup
mysqldump: Got errno 28 on write
gzip: /sandbox/backup/mysql_dbs/bcfg2_reports.20100621220002.dump.gz: No space left on device mysqldump: Got errno 28 on write
gzip: /sandbox/backup/mysql_dbs/mysql.20100621220002.dump.gz: No space left on device Backup # 1 = bcfg2_reports.20100621220002.dump -> 46809354240 bytes Backup # 2 = bcfg2_reports.20100620220001.dump -> deleted Backup # 1 = information_schema.20100621220002.dump.gz -> 465 bytes Backup # 2 = information_schema.20100620220001.dump.gz -> deleted Backup # 1 = mysql.20100621220002.dump -> 0 bytes Backup # 2 = mysql.20100620220001.dump -> deleted
Ok, I'll give that a shot first. ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055 ----- Original Message ----- From: "Narayan Desai" <[email protected]> To: "Dan Olson" <[email protected]> Cc: [email protected] Sent: Tuesday, June 22, 2010 8:10:21 AM GMT -06:00 US/Canada Central Subject: Re: [backup-admins] MySQL@spock backup there is a new compressor/deduplicator command in bcfg2-1.1.0rc3 that you might try running on the db; it should really cut down on the amount of data that is stored. -nld On Jun 22, 2010, at 8:07 AM, Dan Olson wrote:
Is anyone using the data in the bcfg2_reports database on spock? If I don't get any replies I'm going to archive it and clear it out.
---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055
----- Forwarded Message ----- From: "root" <[email protected]> To: [email protected] Sent: Monday, June 21, 2010 10:55:48 PM GMT -06:00 US/Canada Central Subject: [backup-admins] MySQL@spock backup
mysqldump: Got errno 28 on write
gzip: /sandbox/backup/mysql_dbs/bcfg2_reports.20100621220002.dump.gz: No space left on device mysqldump: Got errno 28 on write
gzip: /sandbox/backup/mysql_dbs/mysql.20100621220002.dump.gz: No space left on device Backup # 1 = bcfg2_reports.20100621220002.dump -> 46809354240 bytes Backup # 2 = bcfg2_reports.20100620220001.dump -> deleted Backup # 1 = information_schema.20100621220002.dump.gz -> 465 bytes Backup # 2 = information_schema.20100620220001.dump.gz -> deleted Backup # 1 = mysql.20100621220002.dump -> 0 bytes Backup # 2 = mysql.20100620220001.dump -> deleted
You can run this with "bcfg2-admin reports scrub", but it only showed up after rc2, so you'll need to grab the latest tarball from ftp://ftp.mcs.anl.gov/pub/bcfg/bcfg2-1.1.0rc3.tar.gz -nld On Jun 22, 2010, at 8:24 AM, Dan Olson wrote:
Ok, I'll give that a shot first.
---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055
----- Original Message ----- From: "Narayan Desai" <[email protected]> To: "Dan Olson" <[email protected]> Cc: [email protected] Sent: Tuesday, June 22, 2010 8:10:21 AM GMT -06:00 US/Canada Central Subject: Re: [backup-admins] MySQL@spock backup
there is a new compressor/deduplicator command in bcfg2-1.1.0rc3 that you might try running on the db; it should really cut down on the amount of data that is stored. -nld
On Jun 22, 2010, at 8:07 AM, Dan Olson wrote:
Is anyone using the data in the bcfg2_reports database on spock? If I don't get any replies I'm going to archive it and clear it out.
---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055
----- Forwarded Message ----- From: "root" <[email protected]> To: [email protected] Sent: Monday, June 21, 2010 10:55:48 PM GMT -06:00 US/Canada Central Subject: [backup-admins] MySQL@spock backup
mysqldump: Got errno 28 on write
gzip: /sandbox/backup/mysql_dbs/bcfg2_reports.20100621220002.dump.gz: No space left on device mysqldump: Got errno 28 on write
gzip: /sandbox/backup/mysql_dbs/mysql.20100621220002.dump.gz: No space left on device Backup # 1 = bcfg2_reports.20100621220002.dump -> 46809354240 bytes Backup # 2 = bcfg2_reports.20100620220001.dump -> deleted Backup # 1 = information_schema.20100621220002.dump.gz -> 465 bytes Backup # 2 = information_schema.20100620220001.dump.gz -> deleted Backup # 1 = mysql.20100621220002.dump -> 0 bytes Backup # 2 = mysql.20100620220001.dump -> deleted
participants (2)
-
Dan Olson -
Narayan Desai