http://permalink.gmane.org/gmane.comp.archivers.amanda.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39230 <pre>Hi Jean-Louis, amvault has finished without errors and segmentation fault this morning. Thank you another time, Dennis Am 15.05.2012 15:16, schrieb Jean-Louis Martineau: </pre> Dennis Benndorf 2012-05-16T10:26:25 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39229 <pre>Dennis, The attached patch make amvault to check if a log file already exists and abort in this case. It will abort if amdump is already running. Jean-Louis On 05/15/2012 09:16 AM, Jean-Louis Martineau wrote: </pre> Jean-Louis Martineau 2012-05-15T14:18:27 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39228 <pre>Really big thanks to you, I tested amrecover and it works now. The test of amvault will be available tommorow. I will send another email then. Kind Regards, Dennis </pre> Dennis Benndorf 2012-05-15T13:57:06 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39227 <pre>Dennis, The attached patch fix the crash. You have log corruption because of amdump and amvault running simultaneously. Jean-Louis On 05/15/2012 08:20 AM, Dennis Benndorf wrote: </pre> Jean-Louis Martineau 2012-05-15T13:16:39 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39226 <pre>I never saw amanda print this message. Can you run gdb again and get the value of the second argument to g_string_chunk_insert_const. Send me /usr/local/etc/amanda/daily/catalog/log.20120506180002.0 and /usr/local/etc/amanda/daily/catalog/log.20120505180458.0 Jean-Louis </pre> Jean-Louis Martineau 2012-05-15T12:14:43 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39225 <pre>Hello Jean-Louis, the debug file is really short: amanda&lt; at &gt;dl380-54:~$ cat /tmp/amanda/server/daily/amvault.20120515134859.debug Tue May 15 13:48:59 2012: thd-0x2230400: amvault: pid 10772 ruid 1001 euid 1001 version 3.3.1.svn.4721: start at Tue May 15 13:48:59 2012 Tue May 15 13:48:59 2012: thd-0x2230400: amvault: Arguments: -olabelstr=^D1[0-9]*$ --src-timestamp latest --dst-changer l700-robot-MRO --label-template D1%%%% daily Tue May 15 13:48:59 2012: thd-0x2230400: amvault: config_overrides: labelstr ^D1[0-9]*$ Tue May 15 13:48:59 2012: thd-0x2230400: amvault: pid 10772 ruid 1001 euid 1001 version 3.3.1.svn.4721: rename at Tue May 15 13:48:59 2012 Tue May 15 13:48:59 2012: thd-0x2230400: amvault: chg-robot: using statefile '/usr/local/var/amanda/chg-robot-dev-L700-MRU-CHANGER' Here is what gdb tells us: amanda&lt; at &gt;dl380-54:~$ gdb perl GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later &lt;http://gnu.org/l</pre> Dennis Benndorf 2012-05-15T11:54:23 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39224 <pre>Dennis, Post the amvault.&lt;datastamp&gt;.debug file. Can you run amvault inside gdb? $gdb perl (gdb) run /path/to/amvault [amvault arg] And get a backtrace of all threads? (gdb) info threads Then for each threads: (gdb) thread &lt;thread id&gt; (gdb) where Jean-Louis On 05/15/2012 03:21 AM, Dennis Benndorf wrote: </pre> Jean-Louis Martineau 2012-05-15T11:44:41 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39223 <pre>Hello Jean-Louis, got annother segmentation fault this morning now running amanda 3.3.1.svn.4721. Regards, Dennis Am 14.05.2012 16:14, schrieb Jean-Louis Martineau: </pre> Dennis Benndorf 2012-05-15T07:21:14 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39222 <pre> no, it is related to the new version of glib Use the HEAD of the svn 3-3 branch or the latest 3.3 snapshot from http://www.zmanda.com/community-builds.php Jean-Louis </pre> Jean-Louis Martineau 2012-05-14T14:14:41 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39221 <pre>Hello &lt; at &gt;all, after updating our backup server to Ubuntu Server 12.04 and recompiling amanda 3.3.1 amvault fails with segmentation fault everytime it is started. Might this have something to do with the removal of g_queue_free_full, which was needed to compile it? Which logfiles do you need? Best regards, Dennis </pre> Dennis Benndorf 2012-05-14T12:26:30 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39220 <pre>It turns out I have been running on 4.0.0alpha-4692 for a while, all the newer ones have a broken build: libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../config -I../gnulib -fno-strict-aliasing -D_GNU_SOURCE - pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -Wextra -Wparentheses -Wdeclaration- after-statement -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Wformat -Wformat-security -Wsign-compare -Wfloat-equal -Wold-style-definition -Wno-strict-aliasing -Wno-unknown-pragmas -g -O2 -fno- strict-aliasing -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -MT util.lo -MD -MP -MF .deps/util.Tpo -c util.c -fPIC -DPIC -o .libs/util.o util.c: In function 'portable_readdir': util.c:1150:9: error: #pragma GCC diagnostic not allowed inside functions util.c:1151:9: error: #pragma GCC diagnostic not allowed inside functions util.c:1152:5: warning: missing initializer util.c:1152:5: warning: (near initialization for 'mutex.unused') util.c:1153:9: error: #pragma GCC diagnostic not allowed ins</pre> gene heskett 2012-05-13T02:48:39 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39219 <pre> If you're simply adding/removing disks to be backed-up, you'll want to edit the file that contains your DLE's. After removing/adding the appropriate entries (don't forget the appropriate dump type) be sure to run an amcheck afterwards to verify your changes. If all goes well, amanda will create the index files and perform a level 0 dump of the new disks on the next run for that configuration. If you want to add/remove holding disks you'll need, if the mountpoints will be different, to edit your configuration files to change the information about the holding disks (including reserve amount, mountpoint, etc). I would recommend checking to make sure that there isn't any data in the holding disk first, by doing an amflush. Good luck! ~~Mike </pre> Mike Neimoyer 2012-05-09T13:29:30 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39218 <pre>Hi Sven, Send me the log.&lt;datastamp&gt;.* files for the three tapes. Jean-Louis On 05/09/2012 11:43 AM, Sven Rudolph wrote: </pre> Jean-Louis Martineau 2012-05-09T17:16:57 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39217 <pre>Hello, I have a problem with amrecover: amrecover&gt; add cpio.ry Added file /cpio.ry amrecover&gt; list TAPE Set1-2011-18:1;Set1K-2011-13:15,16;Set1K-2011-14:1,2,3,4,5,6,7,8,9,10 LEVEL 0 DATE 2012-01-01-03-08-50 /cpio.ry amrecover&gt; extract Extracting files using tape drive changer on host uxrs74. The following tapes are needed: Set1-2011-18 Set1K-2011-13 Set1K-2011-14 Extracting files using tape drive changer on host uxrs74. Load tape Set1-2011-18 now Continue [?/Y/n/s/d]? y Specified file list matches multiple dumps; cannot continue recovery Got no header and data from server, check in amidxtaped.*.debug and amandad.*.debug files on server amrecover&gt; Set1-2011-18 is the original tape, the DLE dump resides on this tape only. Set1K-2011-13 and Set1K-2011-14 are the copies made with amvault. I had to enable splitting in order to use amvault, so the dump is split in several 40G-sized parts. And some of these parts are on one tape and the other on the next tape. I did</pre> Sven Rudolph 2012-05-09T15:43:00 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39216 <pre> Just for the record: When writing data the second drive indeed was slower than the first. I swapped the two drives (in amanda.conf), and amvault finished in acceptable time. Thank you for the hints! I was sure the drives were OK... Sven </pre> Sven Rudolph 2012-05-09T13:55:26 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39215 <pre>On Wed May 09 2012 14:01:42 GMT+0200 gtcopeland&lt; at &gt;gmail.com (Greg Copeland) wrote: If you are talking about disks to backup (DLEs), just edit your disklist as required. I'd suggest to run amcheck afterwards to make sure you don't have any typos in the file. Amanda will recognize the new DLEs and force a level 0 dump of them and will simply omit removed DLEs on future runs. If you need to remove holding discs, make sure you don't have any data left on the old discs (run amflush) before removing them from the configuration. Adding new holdings discs shouldn't require any prerequisites. Jens </pre> Jens Berg 2012-05-09T13:10:19 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39214 <pre>I have a need to add a new disk and remove an existing disk. Can this be safely done by simply adding and removing the definitions in the configuration? Thanks, </pre> Greg Copeland 2012-05-09T12:01:42 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39213 <pre>Tue, 01 May 2012 kirjutas Paul Crittenden &lt;paul.crittenden&lt; at &gt;simpson.edu&gt;: amrmtape YourConfig TapeLabel </pre> Toomas Aas 2012-05-04T04:52:20 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39212 <pre>What is the proper way of removing a failed tape from the tape rotation? Paul Crittenden Computer System Manager Simpson College Indianola, IA direct: 515-961-1680 www.simpson.edu </pre> Paul Crittenden 2012-05-01T16:52:43 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39211 <pre>Thanks a Jean, "amrmtape --erase --cleanup DailySet1 backup_data01" Did exactly what I needed. Thanks! Best regards, Kervin Adevsoft Inc Business Software Development http://adevsoft.com/ </pre> Kervin L. Pierre 2012-05-01T16:19:07 http://permalink.gmane.org/gmane.comp.archivers.amanda.user/39210 <pre>amrmtape --erase yes, but amanda might not know you removed them, you must also remove the label from the tapelist file. amrmtape --erase Jean-Louis </pre> Jean-Louis Martineau 2012-05-01T15:56:18 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.archivers.amanda.user