I'm getting dumps that are the same size regardless of dump level. Happening on all clients, all DLEs. The file's timestamps (mtime and ctime) and inode nums are not changing, which could cause them
Author: Paul Bijnens <paul.bijnens AT xplanation DOT com>
Date: Fri, 02 Jun 2006 23:10:10 +0200
Jon LaBadie schreef: I'm getting dumps that are the same size regardless of dump level. Happening on all clients, all DLEs. The file's timestamps (mtime and ctime) and inode nums are not changing, wh
That is good to know, I never looked at the gnutar-list directory before. But I considered permissions. Look alright to me: $ ls -la total 3728 drwxr-xr-x 2 amandabackup disk 4096 Jun 2 04:37 . drwxr
<snip> ... Following up to my own reply: I checked the most recent debug files and they show the "*.new" files are being used. For example, corresponding to the last listing above, two lines from sen
Author: Jean-Louis Martineau <martineau AT zmanda DOT com>
Date: Fri, 02 Jun 2006 20:28:40 -0400
I checked the most recent debug files and they show the "*.new" files are being used. For example, corresponding to the last listing above, two lines from sendbackup...debug: sendbackup-gnutar: time
Nothing about failure to rename, just failure to open the *_0 file. Here is a section from one of the clients. sendbackup: time 0.005: got all connections sendbackup: time 0.006: spawning /usr/bin/gz
Author: Jean-Louis Martineau <martineau AT zmanda DOT com>
Date: Sat, 03 Jun 2006 11:22:16 -0400
Jon LaBadie wrote: On Fri, Jun 02, 2006 at 08:28:40PM -0400, Jean-Louis Martineau wrote: Jon LaBadie wrote: Following up to my own reply: I checked the most recent debug files and they show the "*.ne
I noted it was a "section" of the file. I'm unable to relocate the file my sample above was from. But in a nearly identical file (and many others) there were two more lines. No "parsed backup message