Re: huge (1G) planning files (amdump.n)
(Chris Beggy ) [EMAIL PROTECTED] writes: Joshua Baker-LePain [EMAIL PROTECTED] writes: On Tue, 20 Nov 2001 at 12:09am, [EMAIL PROTECTED] wrote on gnu/linux glibc. I am dumping about 24 partitions, 12G total, no bigger than 2G per partition, in a 1 wk cycle on 12 2G tapes. Wow! Mine are no bigger than ~200K, running 2.4.2p2 and dumping about 45 partitions at 50G total. Glad to hear that! There's hope for my situation. I wiped out the entire curindex info directories, crossed my fingers, and started backing up from scratch. The files are indeed no larger than 250K. Thanks for the help everyone. Chris
Re: huge (1G) planning files (amdump.n)
On Tue, 20 Nov 2001 00:09:05 -0500 Chris Beggy [EMAIL PROTECTED] wrote: Hello. I've checked the archives, but haven't seen this issue. My planning files, (amdump.1 (1G), amdump.2, amdump.3 (0.7G)...) have become huge over time. I am running amanda version 2.4.1p1 on gnu/linux glibc. I am dumping about 24 partitions, 12G total, no bigger than 2G per partition, in a 1 wk cycle on 12 2G tapes. In the last month the planning files have become huge on the amanda master, relative to what I am dumping. Is there anything I can do to reduce the size? What does the content look like? Is it sensible, readable or is it all zeroes? I found a bug in amreport some weeks ago, which was caused by a wrong configuration for 'columnspec' in amanda.conf. The report files where filled with zeroes until all diskspace was consumed. Look for 'amreport:' as subject in the archive. Maybe it is the same kind of bug. -- Volker Apelt volker_apelt .@. yahoo.de (remove the dots, please) Dipl. Chem.+49 6172 31126
Re: huge (1G) planning files (amdump.n)
On Tue, 20 Nov 2001 at 12:09am, [EMAIL PROTECTED] wrote Hello. I've checked the archives, but haven't seen this issue. My planning files, (amdump.1 (1G), amdump.2, amdump.3 (0.7G)...) have become huge over time. I am running amanda version 2.4.1p1 on gnu/linux glibc. I am dumping about 24 partitions, 12G total, no bigger than 2G per partition, in a 1 wk cycle on 12 2G tapes. Wow! Mine are no bigger than ~200K, running 2.4.2p2 and dumping about 45 partitions at 50G total. In the last month the planning files have become huge on the amanda master, relative to what I am dumping. Is there anything I can do to reduce the size? My first question would be -- what's in them? Does it all look kosher? Also, did anything change in your config around the time the files blew up? -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: huge (1G) planning files (amdump.n)
On Tue, 20 Nov 2001 at 11:05am, [EMAIL PROTECTED] wrote Joshua Baker-LePain [EMAIL PROTECTED] writes: Wow! Mine are no bigger than ~200K, running 2.4.2p2 and dumping about 45 partitions at 50G total. Glad to hear that! There's hope for my situation. Now I didn't say that... ;) My first question would be -- what's in them? Does it all look kosher? Things looked normal, but I never spent much time looking at them when they were small. Is there anything odd about the amdumps and/or their reports? Are they taking a really long time? Also, did anything change in your config around the time the files blew up? Yes, I added two tapes to the tapecycle. I have no idea how that would affect this, but that's not saying much. You obviously don't want to remove the tapes. Maybe this would be a good time to upgrade to 2.4.2p2... -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
