Re: amflush problem
* Jean-Louis Martineau [20130703 13:29]:
> Jean-Francois,
>
> There a is bug with overwrite with name with '-'
> (flush-threshold-dumped and flush-threshold-scheduled).
> This bug already fixed.
>
> From ChangeLog:
> 2013-04-18 Jean-Louis Martineau
> * common-src/conffile.c: Fix parsing command overwrite with '-'.
> Fix small --print-source bug.
>
> The only workaround is to set them in amanda.conf.
Thanks Jean-Louis for the info.
jf
>
> Jean-Louis
>
> btw. 3.3.4 will be out very soon.
>
> Jean-Louis
>
> On 07/03/2013 12:03 PM, Jean-Francois Malouin wrote:
> >Replying to myself...
> >
> >* Jean-Francois Malouin [20130627
> >12:08]:
> >>Hi,
> >>
> >>It's been a while since I had to flush a dump from the holddisk to
> >>tape. I use a bash script that contains:
> >>
> >>amflush -f -b -oflush-threshold-dumped=0 -oflush-threshold-scheduled=0
> >>-otaperflush=0 $conf
> >>
> >>Whwn invoked as the amanda user I get the error:
> >>
> >>"/opt/amanda-3.3.2/etc/amanda/top/disklist", line 79: disk device name
> >>expected
> >>amflush: errors processing config file
> >>
> >>Line 79 is the 'app-amgtar' below:
> >>
> >>edgar /opt/amanda {
> >>#tar-calc
> >> app-amgtar
> >> estimate server
> >> record no
> >> index no
> >> strategy noinc
> >>}
> >>
> >>When invoked without any option overrides amflush runs ok.
> >>
> >>Any hint? It used to work prior to 3.x
> >>
> >>Regards,
> >>jf
> >I had time to investigate a little further this morning. Still no go.
> >
> >Here is an example using only 1 DLE in the disklist.
> >
> >~# su amanda -c "~amanda/sbin/flush-and-log.sh down"
> >"/opt/amanda-3.3.2/etc/amanda/down/disklist", line 1: disk dumptype
> >'app-amgtar-span' not found
> >amflush: errors processing config file
> >Use of uninitialized value $OF in ref-to-glob cast at /opt/amanda/sbin/amtoc
> >line 48, line 157.
> >ERROR: while ejecting volume: Tape device /dev/nst0 is not ready or is empty
> >
> >(btw, /opt/amanda-3.3.2 points to /opt/amanda, the homedir of the user
> >'amanda'.
> >
> >The little flush script and other info follows∵
> >
> >~# cat ~amanda/sbin/flush-and-log.sh
> >
> >#!/bin/sh
> >
> >conf="$1"
> >if [ "$conf" = "" ]; then
> > echo "you must provide a config name as an argument!"
> > exit 1
> >else
> > /opt/amanda/sbin/amflush -f -b -oflush-threshold-dumped=0
> > -oflush-threshold-scheduled=0 -otaperflush=0 $conf
> > logdir=`/opt/amanda/sbin/amgetconf $conf logdir`
> > log=`ls -1t $logdir/log.*.[0-9] | head -1`
> > /opt/amanda/sbin/amtoc -t -a $log
> > /opt/amanda/sbin/amtape $conf eject
> >fi
> >
> >The disklist ~amanda/etc/amanda/down/disklist: (edited to include only one
> >DLE)
> >
> >tutor /raid/data8 app-amgtar-span
> >
> >The dumptype 'app-amgtar-span' is defined in the files included in
> >amanda.conf:
> >
> >includefile "/opt/amanda/common/applications.conf"
> >includefile "/opt/amanda/common/dumptype.conf"
> >
> >/opt/amanda/common/applications.conf:
> >
> >define application-tool "app-amgtar" {
> > plugin "amgtar"
> > property "CHECK-DEVICE" "NO"
> > property "IGNORE" ": Directory is new$"
> > property append "IGNORE" ": Directory has been renamed"
> > property append "IGNORE" ": file changed as we read it$"
> > property append "IGNORE" ": socket ignored$"
> > property append "IGNORE" ": Cannot stat: No such file or directory$"
> >}
> >
> >/opt/amanda/common/dumptype.conf:
> >
> >define dumptype "app-amgtar-span" {
> > "global"
> > program "APPLICATION"
> > application "app-amgtar"
> > priority high
> > allow-split
> > holdingdisk required
> > compress none
> > comment "tape-spanning user partitions dumped with amgtar"
> >}
> >
> >In the end it boils down to:
> >
> >~# su amanda -c "~amanda/sbin/amadmin down disklist"
> >line 1 (/opt/amanda/etc/amanda/down/disklist):
> > host tutor:
> > interface default
> > disk /raid/data8:
> > program "APPLICATION"
> > application "app-amgtar"
> > COMMENT "tape-spanning user partitions dumped with
> > amgtar"
> > PROGRAM "APPLICATION"
> > SERVER-CUSTOM-COMPRESS ""
> > CLIENT-CUSTOM-COMPRESS ""
> > SERVER-ENCRYPT ""
> > CLIENT-ENCRYPT ""
> > AMANDAD-PATH""
> > CLIENT-USERNAME ""
> > SSH-KEYS""
> > AUTH"BSDTCP"
> > EXCLUDE LIST
> > EXCLUDE FILE
> > INCLUDE LIST
> > INCLUDE FILE
> > PRIORITYHIGH
> > DUMPCYCLE 10
> > MAXDUMPS6
> > MAXPROMOTEDAY 1
> > BUMPPERCENT 10
> > BUMPSIZE10240K
> > BUMPDAYS2
> > BUMPMULT2.0
> > STARTTIME000
> > STRATEGYSTANDARD
> >
Re: amflush problem
Jean-Francois,
There a is bug with overwrite with name with '-' (flush-threshold-dumped
and flush-threshold-scheduled).
This bug already fixed.
From ChangeLog:
2013-04-18 Jean-Louis Martineau
* common-src/conffile.c: Fix parsing command overwrite with '-'.
Fix small --print-source bug.
The only workaround is to set them in amanda.conf.
Jean-Louis
btw. 3.3.4 will be out very soon.
Jean-Louis
On 07/03/2013 12:03 PM, Jean-Francois Malouin wrote:
Replying to myself...
* Jean-Francois Malouin [20130627
12:08]:
Hi,
It's been a while since I had to flush a dump from the holddisk to
tape. I use a bash script that contains:
amflush -f -b -oflush-threshold-dumped=0 -oflush-threshold-scheduled=0
-otaperflush=0 $conf
Whwn invoked as the amanda user I get the error:
"/opt/amanda-3.3.2/etc/amanda/top/disklist", line 79: disk device name expected
amflush: errors processing config file
Line 79 is the 'app-amgtar' below:
edgar /opt/amanda {
#tar-calc
app-amgtar
estimate server
record no
index no
strategy noinc
}
When invoked without any option overrides amflush runs ok.
Any hint? It used to work prior to 3.x
Regards,
jf
I had time to investigate a little further this morning. Still no go.
Here is an example using only 1 DLE in the disklist.
~# su amanda -c "~amanda/sbin/flush-and-log.sh down"
"/opt/amanda-3.3.2/etc/amanda/down/disklist", line 1: disk dumptype
'app-amgtar-span' not found
amflush: errors processing config file
Use of uninitialized value $OF in ref-to-glob cast at /opt/amanda/sbin/amtoc line 48,
line 157.
ERROR: while ejecting volume: Tape device /dev/nst0 is not ready or is empty
(btw, /opt/amanda-3.3.2 points to /opt/amanda, the homedir of the user 'amanda'.
The little flush script and other info follows∵
~# cat ~amanda/sbin/flush-and-log.sh
#!/bin/sh
conf="$1"
if [ "$conf" = "" ]; then
echo "you must provide a config name as an argument!"
exit 1
else
/opt/amanda/sbin/amflush -f -b -oflush-threshold-dumped=0
-oflush-threshold-scheduled=0 -otaperflush=0 $conf
logdir=`/opt/amanda/sbin/amgetconf $conf logdir`
log=`ls -1t $logdir/log.*.[0-9] | head -1`
/opt/amanda/sbin/amtoc -t -a $log
/opt/amanda/sbin/amtape $conf eject
fi
The disklist ~amanda/etc/amanda/down/disklist: (edited to include only one DLE)
tutor /raid/data8 app-amgtar-span
The dumptype 'app-amgtar-span' is defined in the files included in amanda.conf:
includefile "/opt/amanda/common/applications.conf"
includefile "/opt/amanda/common/dumptype.conf"
/opt/amanda/common/applications.conf:
define application-tool "app-amgtar" {
plugin "amgtar"
property "CHECK-DEVICE" "NO"
property "IGNORE" ": Directory is new$"
property append "IGNORE" ": Directory has been renamed"
property append "IGNORE" ": file changed as we read it$"
property append "IGNORE" ": socket ignored$"
property append "IGNORE" ": Cannot stat: No such file or directory$"
}
/opt/amanda/common/dumptype.conf:
define dumptype "app-amgtar-span" {
"global"
program "APPLICATION"
application "app-amgtar"
priority high
allow-split
holdingdisk required
compress none
comment "tape-spanning user partitions dumped with amgtar"
}
In the end it boils down to:
~# su amanda -c "~amanda/sbin/amadmin down disklist"
line 1 (/opt/amanda/etc/amanda/down/disklist):
host tutor:
interface default
disk /raid/data8:
program "APPLICATION"
application "app-amgtar"
COMMENT "tape-spanning user partitions dumped with amgtar"
PROGRAM "APPLICATION"
SERVER-CUSTOM-COMPRESS ""
CLIENT-CUSTOM-COMPRESS ""
SERVER-ENCRYPT ""
CLIENT-ENCRYPT ""
AMANDAD-PATH""
CLIENT-USERNAME ""
SSH-KEYS""
AUTH"BSDTCP"
EXCLUDE LIST
EXCLUDE FILE
INCLUDE LIST
INCLUDE FILE
PRIORITYHIGH
DUMPCYCLE 10
MAXDUMPS6
MAXPROMOTEDAY 1
BUMPPERCENT 10
BUMPSIZE10240K
BUMPDAYS2
BUMPMULT2.0
STARTTIME000
STRATEGYSTANDARD
ESTIMATECLIENT
COMPRESSNONE
ENCRYPT NONE
SERVER-DECRYPT-OPTION "-d"
CLIENT-DECRYPT-OPTION "-d"
COMPRATE0.5 0.5
TAPE-SPLITSIZE 0K
FALLBACK-SPLITSIZE 10240K
SPLIT-DISKBUFFER""
RECORD yes
SKIP-INCR no
SKIP-FULL no
HOLDINGDISK REQUIRED
KENCRYPTno
IGNORE no
INDEX yes
APPLICATION
Re: amflush problem
* Debra S Baddorf [20130703 13:04]:
> This probably isn't applicable to your problem, but my backups were ignoring
> DLEs on the holding disk
> and not autoflushing them
> until I learned that AUTOFLUSH now has three options -- no, yes, and all.
> "yes" only means "flush thing with the same DLE as on your current amdump
> command" (paraphrased)
> "all" means autoflush from any DLE that you find on the holding disk.
> Deb
Thanks for the reply Debra.
I had autoflush set to yes and I get the same problem when I set it to
'all'.
cheers,
jf
>
> On Jul 3, 2013, at 11:03 AM, Jean-Francois Malouin wrote:
>
> > Replying to myself...
> >
> > * Jean-Francois Malouin [20130627
> > 12:08]:
> >> Hi,
> >>
> >> It's been a while since I had to flush a dump from the holddisk to
> >> tape. I use a bash script that contains:
> >>
> >> amflush -f -b -oflush-threshold-dumped=0 -oflush-threshold-scheduled=0
> >> -otaperflush=0 $conf
> >>
> >> Whwn invoked as the amanda user I get the error:
> >>
> >> "/opt/amanda-3.3.2/etc/amanda/top/disklist", line 79: disk device name
> >> expected
> >> amflush: errors processing config file
> >>
> >> Line 79 is the 'app-amgtar' below:
> >>
> >> edgar /opt/amanda {
> >> #tar-calc
> >>app-amgtar
> >>estimate server
> >>record no
> >>index no
> >>strategy noinc
> >> }
> >>
> >> When invoked without any option overrides amflush runs ok.
> >>
> >> Any hint? It used to work prior to 3.x
> >>
> >> Regards,
> >> jf
> >
> > I had time to investigate a little further this morning. Still no go.
> >
> > Here is an example using only 1 DLE in the disklist.
> >
> > ~# su amanda -c "~amanda/sbin/flush-and-log.sh down"
> > "/opt/amanda-3.3.2/etc/amanda/down/disklist", line 1: disk dumptype
> > 'app-amgtar-span' not found
> > amflush: errors processing config file
> > Use of uninitialized value $OF in ref-to-glob cast at
> > /opt/amanda/sbin/amtoc line 48, line 157.
> > ERROR: while ejecting volume: Tape device /dev/nst0 is not ready or is empty
> >
> > (btw, /opt/amanda-3.3.2 points to /opt/amanda, the homedir of the user
> > 'amanda'.
> >
> > The little flush script and other info follows∵
> >
> > ~# cat ~amanda/sbin/flush-and-log.sh
> >
> > #!/bin/sh
> >
> > conf="$1"
> > if [ "$conf" = "" ]; then
> >echo "you must provide a config name as an argument!"
> >exit 1
> > else
> >/opt/amanda/sbin/amflush -f -b -oflush-threshold-dumped=0
> > -oflush-threshold-scheduled=0 -otaperflush=0 $conf
> >logdir=`/opt/amanda/sbin/amgetconf $conf logdir`
> >log=`ls -1t $logdir/log.*.[0-9] | head -1`
> >/opt/amanda/sbin/amtoc -t -a $log
> >/opt/amanda/sbin/amtape $conf eject
> > fi
> >
> > The disklist ~amanda/etc/amanda/down/disklist: (edited to include only one
> > DLE)
> >
> > tutor /raid/data8 app-amgtar-span
> >
> > The dumptype 'app-amgtar-span' is defined in the files included in
> > amanda.conf:
> >
> > includefile "/opt/amanda/common/applications.conf"
> > includefile "/opt/amanda/common/dumptype.conf"
> >
> > /opt/amanda/common/applications.conf:
> >
> > define application-tool "app-amgtar" {
> >plugin "amgtar"
> >property "CHECK-DEVICE" "NO"
> >property "IGNORE" ": Directory is new$"
> >property append "IGNORE" ": Directory has been renamed"
> >property append "IGNORE" ": file changed as we read it$"
> >property append "IGNORE" ": socket ignored$"
> >property append "IGNORE" ": Cannot stat: No such file or directory$"
> > }
> >
> > /opt/amanda/common/dumptype.conf:
> >
> > define dumptype "app-amgtar-span" {
> >"global"
> >program "APPLICATION"
> >application "app-amgtar"
> >priority high
> >allow-split
> >holdingdisk required
> >compress none
> >comment "tape-spanning user partitions dumped with amgtar"
> > }
> >
> > In the end it boils down to:
> >
> > ~# su amanda -c "~amanda/sbin/amadmin down disklist"
> > line 1 (/opt/amanda/etc/amanda/down/disklist):
> >host tutor:
> >interface default
> >disk /raid/data8:
> >program "APPLICATION"
> >application "app-amgtar"
> >COMMENT "tape-spanning user partitions dumped with
> > amgtar"
> >PROGRAM "APPLICATION"
> >SERVER-CUSTOM-COMPRESS ""
> >CLIENT-CUSTOM-COMPRESS ""
> >SERVER-ENCRYPT ""
> >CLIENT-ENCRYPT ""
> >AMANDAD-PATH""
> >CLIENT-USERNAME ""
> >SSH-KEYS""
> >AUTH"BSDTCP"
> >EXCLUDE LIST
> >EXCLUDE FILE
> >INCLUDE LIST
> >INCLUDE FILE
> >PRIORITYHIGH
> >DUMPCYCLE 10
> >MAXDUMPS6
> >MAXPROMOTEDAY 1
> >BUMPPERCENT 10
> >BUMPSIZE10240K
> >BUMPDAYS2
> >BUMPMULT2.0
> >STARTTI
Re: amflush problem
Replying to myself...
* Jean-Francois Malouin [20130627
12:08]:
> Hi,
>
> It's been a while since I had to flush a dump from the holddisk to
> tape. I use a bash script that contains:
>
> amflush -f -b -oflush-threshold-dumped=0 -oflush-threshold-scheduled=0
> -otaperflush=0 $conf
>
> Whwn invoked as the amanda user I get the error:
>
> "/opt/amanda-3.3.2/etc/amanda/top/disklist", line 79: disk device name
> expected
> amflush: errors processing config file
>
> Line 79 is the 'app-amgtar' below:
>
> edgar /opt/amanda {
> #tar-calc
> app-amgtar
> estimate server
> record no
> index no
> strategy noinc
> }
>
> When invoked without any option overrides amflush runs ok.
>
> Any hint? It used to work prior to 3.x
>
> Regards,
> jf
I had time to investigate a little further this morning. Still no go.
Here is an example using only 1 DLE in the disklist.
~# su amanda -c "~amanda/sbin/flush-and-log.sh down"
"/opt/amanda-3.3.2/etc/amanda/down/disklist", line 1: disk dumptype
'app-amgtar-span' not found
amflush: errors processing config file
Use of uninitialized value $OF in ref-to-glob cast at /opt/amanda/sbin/amtoc
line 48, line 157.
ERROR: while ejecting volume: Tape device /dev/nst0 is not ready or is empty
(btw, /opt/amanda-3.3.2 points to /opt/amanda, the homedir of the user
'amanda'.
The little flush script and other info follows∵
~# cat ~amanda/sbin/flush-and-log.sh
#!/bin/sh
conf="$1"
if [ "$conf" = "" ]; then
echo "you must provide a config name as an argument!"
exit 1
else
/opt/amanda/sbin/amflush -f -b -oflush-threshold-dumped=0
-oflush-threshold-scheduled=0 -otaperflush=0 $conf
logdir=`/opt/amanda/sbin/amgetconf $conf logdir`
log=`ls -1t $logdir/log.*.[0-9] | head -1`
/opt/amanda/sbin/amtoc -t -a $log
/opt/amanda/sbin/amtape $conf eject
fi
The disklist ~amanda/etc/amanda/down/disklist: (edited to include only one DLE)
tutor /raid/data8 app-amgtar-span
The dumptype 'app-amgtar-span' is defined in the files included in amanda.conf:
includefile "/opt/amanda/common/applications.conf"
includefile "/opt/amanda/common/dumptype.conf"
/opt/amanda/common/applications.conf:
define application-tool "app-amgtar" {
plugin "amgtar"
property "CHECK-DEVICE" "NO"
property "IGNORE" ": Directory is new$"
property append "IGNORE" ": Directory has been renamed"
property append "IGNORE" ": file changed as we read it$"
property append "IGNORE" ": socket ignored$"
property append "IGNORE" ": Cannot stat: No such file or directory$"
}
/opt/amanda/common/dumptype.conf:
define dumptype "app-amgtar-span" {
"global"
program "APPLICATION"
application "app-amgtar"
priority high
allow-split
holdingdisk required
compress none
comment "tape-spanning user partitions dumped with amgtar"
}
In the end it boils down to:
~# su amanda -c "~amanda/sbin/amadmin down disklist"
line 1 (/opt/amanda/etc/amanda/down/disklist):
host tutor:
interface default
disk /raid/data8:
program "APPLICATION"
application "app-amgtar"
COMMENT "tape-spanning user partitions dumped with amgtar"
PROGRAM "APPLICATION"
SERVER-CUSTOM-COMPRESS ""
CLIENT-CUSTOM-COMPRESS ""
SERVER-ENCRYPT ""
CLIENT-ENCRYPT ""
AMANDAD-PATH""
CLIENT-USERNAME ""
SSH-KEYS""
AUTH"BSDTCP"
EXCLUDE LIST
EXCLUDE FILE
INCLUDE LIST
INCLUDE FILE
PRIORITYHIGH
DUMPCYCLE 10
MAXDUMPS6
MAXPROMOTEDAY 1
BUMPPERCENT 10
BUMPSIZE10240K
BUMPDAYS2
BUMPMULT2.0
STARTTIME000
STRATEGYSTANDARD
ESTIMATECLIENT
COMPRESSNONE
ENCRYPT NONE
SERVER-DECRYPT-OPTION "-d"
CLIENT-DECRYPT-OPTION "-d"
COMPRATE0.5 0.5
TAPE-SPLITSIZE 0K
FALLBACK-SPLITSIZE 10240K
SPLIT-DISKBUFFER""
RECORD yes
SKIP-INCR no
SKIP-FULL no
HOLDINGDISK REQUIRED
KENCRYPTno
IGNORE no
INDEX yes
APPLICATION "app-amgtar"
CLIENT-PORT ""
DATA-PATH AMANDA
ALLOW-SPLIT yes
RECOVERY-LIMIT
DUMP-LIMIT SERVER
MAX-WARNINGS20
spindle -1
jf
Re: amflush problem with 2.5.2-20070508
Just to confirm that this is fixed with 2.5.2-20070523. jf * Jean-Francois Malouin <[EMAIL PROTECTED]> [20070524 09:59]: > My first attempt at flushing the holdding disk > with Amanda-2.5.2-20070508 fails: > > su amanda -c "/opt/amanda/amanda4/sbin/amflush stk_80-conf4"Scanning > /holddisk/conf4/stk_80... > 20070408091512: found Amanda directory. > 20070507221512: found Amanda directory. > 20070509221513: found Amanda directory. > 2007051514: found Amanda directory. > > Multiple Amanda directories, please pick one by letter: > A. 20070408091512 > B. 20070507221512 > C. 20070509221513 > D. 2007051514 > Select directories to flush [A..D]: [ALL] > Could not find any valid dump image, check directory. > > Looking at the content of the holdding disk: > > drwx--2 amanda sys 4096 May 24 02:12 ./ > drwxr-xr-x6 amanda sys 90 May 24 09:51 ../ > -rw---1 amanda sys 63488 May 23 09:56 > yorick._data_ado_ado1_slsj_subjects.2 > -rw---1 amanda sys 0 May 23 17:00 > yorick._data_ado_ado1_slsj_transfer.2 > -rw---1 amanda sys 0 May 23 20:07 yorick.ado1.1 > -rw---1 amanda sys2480128 May 23 11:08 yorick.ado1_slsj.1 > -rw---1 amanda sys 0 May 24 01:17 yorick.mril4_2.1 > -rw---1 amanda sys 135168 May 23 09:17 yorick.mril4_3.1 > -rw---1 amanda sys 7268272128 May 23 07:11 yorick.mril4_4.0 > > ... > > Any thoughts? > Thanks, > jf -- <° ><
Re: amflush problem with 2.5.2-20070508
* Dustin J. Mitchell <[EMAIL PROTECTED]> [20070524 10:38]: > On Thu, May 24, 2007 at 09:58:44AM -0400, Jean-Francois Malouin wrote: > > My first attempt at flushing the holdding disk > > with Amanda-2.5.2-20070508 fails: > > > > su amanda -c "/opt/amanda/amanda4/sbin/amflush stk_80-conf4"Scanning > > /holddisk/conf4/stk_80... > > 20070408091512: found Amanda directory. > > 20070507221512: found Amanda directory. > > 20070509221513: found Amanda directory. > > 2007051514: found Amanda directory. > > > > Multiple Amanda directories, please pick one by letter: > > A. 20070408091512 > > B. 20070507221512 > > C. 20070509221513 > > D. 2007051514 > > Select directories to flush [A..D]: [ALL] > > Could not find any valid dump image, check directory. > > > > Looking at the content of the holdding disk: > > Which directory is this? There should be four subdirectories of stk_80, > one with each of the timestamps above. yes, that was the listing in D. 2007051514 > > > drwx--2 amanda sys 4096 May 24 02:12 ./ > > drwxr-xr-x6 amanda sys 90 May 24 09:51 ../ > > -rw---1 amanda sys 63488 May 23 09:56 > > yorick._data_ado_ado1_slsj_subjects.2 > > -rw---1 amanda sys 0 May 23 17:00 > > yorick._data_ado_ado1_slsj_transfer.2 > > -rw---1 amanda sys 0 May 23 20:07 yorick.ado1.1 > > -rw---1 amanda sys2480128 May 23 11:08 yorick.ado1_slsj.1 > > -rw---1 amanda sys 0 May 24 01:17 yorick.mril4_2.1 > > -rw---1 amanda sys 135168 May 23 09:17 yorick.mril4_3.1 > > -rw---1 amanda sys 7268272128 May 23 07:11 yorick.mril4_4.0 > > Have you recently changed your 'usetimestamps' setting? A mismatch > between the timestamp or datestamp in each dumpfile and the timstamp > (never a datestamp) that is the name of the directory can cause an error > like the one you're seeing. no I haven't changed usetimestamps. > > Can you run the following at the bash prompt and send us the result? make that tcsh prompt :) > > for i in `find /holddisk/conf4/stk_80 -type f`; do > echo $i; head -n1 $i; > done See attached. Just tested the latest snapshot (2.5.2-20070523) and it seems to flush ok. thanks, jf > > Dustin > > -- > Dustin J. Mitchell > Storage Software Engineer, Zmanda, Inc. > http://www.zmanda.com/ -- <° ><
Re: amflush problem with 2.5.2-20070508
On Thu, May 24, 2007 at 09:58:44AM -0400, Jean-Francois Malouin wrote: > My first attempt at flushing the holdding disk > with Amanda-2.5.2-20070508 fails: > > su amanda -c "/opt/amanda/amanda4/sbin/amflush stk_80-conf4"Scanning > /holddisk/conf4/stk_80... > 20070408091512: found Amanda directory. > 20070507221512: found Amanda directory. > 20070509221513: found Amanda directory. > 2007051514: found Amanda directory. > > Multiple Amanda directories, please pick one by letter: > A. 20070408091512 > B. 20070507221512 > C. 20070509221513 > D. 2007051514 > Select directories to flush [A..D]: [ALL] > Could not find any valid dump image, check directory. > > Looking at the content of the holdding disk: Which directory is this? There should be four subdirectories of stk_80, one with each of the timestamps above. > drwx--2 amanda sys 4096 May 24 02:12 ./ > drwxr-xr-x6 amanda sys 90 May 24 09:51 ../ > -rw---1 amanda sys 63488 May 23 09:56 > yorick._data_ado_ado1_slsj_subjects.2 > -rw---1 amanda sys 0 May 23 17:00 > yorick._data_ado_ado1_slsj_transfer.2 > -rw---1 amanda sys 0 May 23 20:07 yorick.ado1.1 > -rw---1 amanda sys2480128 May 23 11:08 yorick.ado1_slsj.1 > -rw---1 amanda sys 0 May 24 01:17 yorick.mril4_2.1 > -rw---1 amanda sys 135168 May 23 09:17 yorick.mril4_3.1 > -rw---1 amanda sys 7268272128 May 23 07:11 yorick.mril4_4.0 Have you recently changed your 'usetimestamps' setting? A mismatch between the timestamp or datestamp in each dumpfile and the timstamp (never a datestamp) that is the name of the directory can cause an error like the one you're seeing. Can you run the following at the bash prompt and send us the result? for i in `find /holddisk/conf4/stk_80 -type f`; do echo $i; head -n1 $i; done Dustin -- Dustin J. Mitchell Storage Software Engineer, Zmanda, Inc. http://www.zmanda.com/
Re: amflush problem with 2.5.2-20070508
* Jean-Louis Martineau <[EMAIL PROTECTED]> [20070524 10:23]: > Bug fixed 2007-05-15. Try latest snapshot. Need more coffee! Just noticed it... Thanks jf > > Jean-Louis > > Jean-Francois Malouin wrote: > >My first attempt at flushing the holdding disk > >with Amanda-2.5.2-20070508 fails: > > > >su amanda -c "/opt/amanda/amanda4/sbin/amflush stk_80-conf4"Scanning > >/holddisk/conf4/stk_80... > > 20070408091512: found Amanda directory. > > 20070507221512: found Amanda directory. > > 20070509221513: found Amanda directory. > > 2007051514: found Amanda directory. > > > >Multiple Amanda directories, please pick one by letter: > > A. 20070408091512 > > B. 20070507221512 > > C. 20070509221513 > > D. 2007051514 > >Select directories to flush [A..D]: [ALL] > >Could not find any valid dump image, check directory. > > > >Looking at the content of the holdding disk: > > > >drwx--2 amanda sys 4096 May 24 02:12 ./ > >drwxr-xr-x6 amanda sys 90 May 24 09:51 ../ > >-rw---1 amanda sys 63488 May 23 09:56 > >yorick._data_ado_ado1_slsj_subjects.2 > >-rw---1 amanda sys 0 May 23 17:00 > >yorick._data_ado_ado1_slsj_transfer.2 > >-rw---1 amanda sys 0 May 23 20:07 yorick.ado1.1 > >-rw---1 amanda sys2480128 May 23 11:08 yorick.ado1_slsj.1 > >-rw---1 amanda sys 0 May 24 01:17 yorick.mril4_2.1 > >-rw---1 amanda sys 135168 May 23 09:17 yorick.mril4_3.1 > >-rw---1 amanda sys 7268272128 May 23 07:11 yorick.mril4_4.0 > > > >... > > > >Any thoughts? > >Thanks, > >jf > > -- <° ><
Re: amflush problem with 2.5.2-20070508
Bug fixed 2007-05-15. Try latest snapshot. Jean-Louis Jean-Francois Malouin wrote: My first attempt at flushing the holdding disk with Amanda-2.5.2-20070508 fails: su amanda -c "/opt/amanda/amanda4/sbin/amflush stk_80-conf4"Scanning /holddisk/conf4/stk_80... 20070408091512: found Amanda directory. 20070507221512: found Amanda directory. 20070509221513: found Amanda directory. 2007051514: found Amanda directory. Multiple Amanda directories, please pick one by letter: A. 20070408091512 B. 20070507221512 C. 20070509221513 D. 2007051514 Select directories to flush [A..D]: [ALL] Could not find any valid dump image, check directory. Looking at the content of the holdding disk: drwx--2 amanda sys 4096 May 24 02:12 ./ drwxr-xr-x6 amanda sys 90 May 24 09:51 ../ -rw---1 amanda sys 63488 May 23 09:56 yorick._data_ado_ado1_slsj_subjects.2 -rw---1 amanda sys 0 May 23 17:00 yorick._data_ado_ado1_slsj_transfer.2 -rw---1 amanda sys 0 May 23 20:07 yorick.ado1.1 -rw---1 amanda sys2480128 May 23 11:08 yorick.ado1_slsj.1 -rw---1 amanda sys 0 May 24 01:17 yorick.mril4_2.1 -rw---1 amanda sys 135168 May 23 09:17 yorick.mril4_3.1 -rw---1 amanda sys 7268272128 May 23 07:11 yorick.mril4_4.0 ... Any thoughts? Thanks, jf
Re: Amflush Problem - Again!
Hello: About your questions about clipping the contents - No, that's the full uncensored log/output of amflush :) And about the problem, I found the solution - a weird one. I moved stuff from 20060216 out of the holding space to some other place and then amflush worked. I am wondering what could be going wrong here. I haven't still tried amflushing 20060216 contents to the tape yet, but I feel it might just work too. I post the results to this list soon. But, what is making amflush not flush data to tape? Incase if it is facing problems maybe from OS or with something else, shouldn't it complain? Regards, Rohit - Original Message - From: "Gene Heskett" <[EMAIL PROTECTED]> To: Sent: Friday, March 03, 2006 10:22 PM Subject: Re: Amflush Problem - Again! On Friday 03 March 2006 09:01, Jon LaBadie wrote: I have no suggestion Rohit, But a question for developers. Amflush output: -bash-2.05b$ /usr/sbin/amflush -f DailySet1 Scanning /backup/amanda_hold/DailySet1... 20060216: found Amanda directory. 20060223: found Amanda directory. 20060302: found Amanda directory. Multiple Amanda directories, please pick one by letter: A. 20060216 B. 20060223 C. 20060302 Select directories to flush [A..C]: [ALL] B C Today is: 20060303 Flushing dumps in 20060223, 20060302 to tape drive "/dev/nst0". Expecting tape TLS-Set-1-05 or a new tape. (The last dumps were to tape TLS-Set -1-04) Are you sure you want to do this [yN]? y amflush: datestamp 20060303 driver: pid 15642 executable driver version 2.4.3 driver: send-cmd time 0.005 to taper: START-TAPER 20060303 driver: adding holding disk 0 dir /backup/amanda_hold/DailySet1 size 2234040 reserving 2234040 out of 2234040 for degraded-mode dumps taper: pid 15643 executable taper version 2.4.3 taper: page size is 4096 taper: buffer size is 32768 taper: buffer[00] at 0x400d5000 taper: buffer[01] at 0x400dd000 taper: buffer[02] at 0x400e5000 taper: buffer[03] at 0x400ed000 taper: buffer[04] at 0x400f5000 taper: buffer[05] at 0x400fd000 taper: buffer[06] at 0x40105000 taper: buffer[07] at 0x4010d000 taper: buffer[08] at 0x40115000 taper: buffer[09] at 0x4011d000 taper: buffer[10] at 0x40125000 taper: buffer[11] at 0x4012d000 taper: buffer[12] at 0x40135000 taper: buffer[13] at 0x4013d000 taper: buffer[14] at 0x40145000 taper: buffer[15] at 0x4014d000 taper: buffer[16] at 0x40155000 taper: buffer[17] at 0x4015d000 taper: buffer[18] at 0x40165000 taper: buffer[19] at 0x4016d000 taper: buffer structures at 0x40175000 for 240 bytes taper: read label `TLS-Set-1-05' date `X' taper: wrote label `TLS-Set-1-05' date `20060303' Why is so much detail being shown to the user of amflush? Do they really care about the taper buffers? Do they really care that the driver is starting taper? Aren't those messages more suitable for a silent log file or a debug file? BTW driver seems like it is doing unneeded things for an amflush, like setting a degraded mode, allocating holding disk, ... I agree Jon, this is too much detail and not enough info at the same time. To the original poster Rohit: Did you purchance clip it off just about the place where it might have gotten interesting? I feel that what we want to know may be there, but we didn't get to see it. -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: Amflush Problem - Again!
On Friday 03 March 2006 09:01, Jon LaBadie wrote: >I have no suggestion Rohit, But a question for developers. > >> Amflush output: >> -bash-2.05b$ /usr/sbin/amflush -f DailySet1 >> Scanning /backup/amanda_hold/DailySet1... >> 20060216: found Amanda directory. >> 20060223: found Amanda directory. >> 20060302: found Amanda directory. >> >> Multiple Amanda directories, please pick one by letter: >> A. 20060216 >> B. 20060223 >> C. 20060302 >> Select directories to flush [A..C]: [ALL] B C >> >> Today is: 20060303 >> Flushing dumps in 20060223, 20060302 to tape drive "/dev/nst0". >> Expecting tape TLS-Set-1-05 or a new tape. (The last dumps were to >> tape TLS-Set >> -1-04) >> Are you sure you want to do this [yN]? y >> amflush: datestamp 20060303 >> driver: pid 15642 executable driver version 2.4.3 >> driver: send-cmd time 0.005 to taper: START-TAPER 20060303 >> driver: adding holding disk 0 dir /backup/amanda_hold/DailySet1 size >> 2234040 reserving 2234040 out of 2234040 for degraded-mode dumps >> taper: pid 15643 executable taper version 2.4.3 >> taper: page size is 4096 >> taper: buffer size is 32768 >> taper: buffer[00] at 0x400d5000 >> taper: buffer[01] at 0x400dd000 >> taper: buffer[02] at 0x400e5000 >> taper: buffer[03] at 0x400ed000 >> taper: buffer[04] at 0x400f5000 >> taper: buffer[05] at 0x400fd000 >> taper: buffer[06] at 0x40105000 >> taper: buffer[07] at 0x4010d000 >> taper: buffer[08] at 0x40115000 >> taper: buffer[09] at 0x4011d000 >> taper: buffer[10] at 0x40125000 >> taper: buffer[11] at 0x4012d000 >> taper: buffer[12] at 0x40135000 >> taper: buffer[13] at 0x4013d000 >> taper: buffer[14] at 0x40145000 >> taper: buffer[15] at 0x4014d000 >> taper: buffer[16] at 0x40155000 >> taper: buffer[17] at 0x4015d000 >> taper: buffer[18] at 0x40165000 >> taper: buffer[19] at 0x4016d000 >> taper: buffer structures at 0x40175000 for 240 bytes >> taper: read label `TLS-Set-1-05' date `X' >> taper: wrote label `TLS-Set-1-05' date `20060303' > >Why is so much detail being shown to the user of amflush? >Do they really care about the taper buffers? >Do they really care that the driver is starting taper? >Aren't those messages more suitable for a silent log file >or a debug file? > >BTW driver seems like it is doing unneeded things for >an amflush, like setting a degraded mode, allocating >holding disk, ... I agree Jon, this is too much detail and not enough info at the same time. To the original poster Rohit: Did you purchance clip it off just about the place where it might have gotten interesting? I feel that what we want to know may be there, but we didn't get to see it. -- Cheers, Gene People having trouble with vz bouncing email to me should add the word 'online' between the 'verizon', and the dot which bypasses vz's stupid bounce rules. I do use spamassassin too. :-) Yahoo.com and AOL/TW attorneys please note, additions to the above message by Gene Heskett are: Copyright 2006 by Maurice Eugene Heskett, all rights reserved.
Re: Amflush Problem - Again!
I have no suggestion Rohit, But a question for developers. > > Amflush output: > -bash-2.05b$ /usr/sbin/amflush -f DailySet1 > Scanning /backup/amanda_hold/DailySet1... > 20060216: found Amanda directory. > 20060223: found Amanda directory. > 20060302: found Amanda directory. > > Multiple Amanda directories, please pick one by letter: > A. 20060216 > B. 20060223 > C. 20060302 > Select directories to flush [A..C]: [ALL] B C > > Today is: 20060303 > Flushing dumps in 20060223, 20060302 to tape drive "/dev/nst0". > Expecting tape TLS-Set-1-05 or a new tape. (The last dumps were to tape > TLS-Set > -1-04) > Are you sure you want to do this [yN]? y > amflush: datestamp 20060303 > driver: pid 15642 executable driver version 2.4.3 > driver: send-cmd time 0.005 to taper: START-TAPER 20060303 > driver: adding holding disk 0 dir /backup/amanda_hold/DailySet1 size 2234040 > reserving 2234040 out of 2234040 for degraded-mode dumps > taper: pid 15643 executable taper version 2.4.3 > taper: page size is 4096 > taper: buffer size is 32768 > taper: buffer[00] at 0x400d5000 > taper: buffer[01] at 0x400dd000 > taper: buffer[02] at 0x400e5000 > taper: buffer[03] at 0x400ed000 > taper: buffer[04] at 0x400f5000 > taper: buffer[05] at 0x400fd000 > taper: buffer[06] at 0x40105000 > taper: buffer[07] at 0x4010d000 > taper: buffer[08] at 0x40115000 > taper: buffer[09] at 0x4011d000 > taper: buffer[10] at 0x40125000 > taper: buffer[11] at 0x4012d000 > taper: buffer[12] at 0x40135000 > taper: buffer[13] at 0x4013d000 > taper: buffer[14] at 0x40145000 > taper: buffer[15] at 0x4014d000 > taper: buffer[16] at 0x40155000 > taper: buffer[17] at 0x4015d000 > taper: buffer[18] at 0x40165000 > taper: buffer[19] at 0x4016d000 > taper: buffer structures at 0x40175000 for 240 bytes > taper: read label `TLS-Set-1-05' date `X' > taper: wrote label `TLS-Set-1-05' date `20060303' > Why is so much detail being shown to the user of amflush? Do they really care about the taper buffers? Do they really care that the driver is starting taper? Aren't those messages more suitable for a silent log file or a debug file? BTW driver seems like it is doing unneeded things for an amflush, like setting a degraded mode, allocating holding disk, ... -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amflush problem
On Wed, Oct 20, 2004 at 01:04:12PM -0400, Jon LaBadie wrote: > On Thu, Oct 14, 2004 at 11:10:47AM -0400, Frederic Medery wrote: > > Hello, > > every time I do a amflush i received this report : > > > > The dumps were flushed to tape daily-05. > > The next tape Amanda expects to use is: daily-02. > > > > > > STATISTICS: > > Total Full Daily > > > > Estimate Time (hrs:min)0:00 > > Run Time (hrs:min) 0:01 > > Dump Time (hrs:min)0:00 0:00 0:00 > > Output Size (meg) 0.00.00.0 > > Original Size (meg) 0.00.00.0 > > Avg Compressed Size (%) -- -- -- > > Filesystems Dumped0 0 0 > > Avg Dump Rate (k/s) -- -- -- > > > > Tape Time (hrs:min)0:00 0:00 0:00 > > Tape Size (meg) 0.00.00.0 > > Tape Used (%) 0.00.00.0 > > Filesystems Taped 0 0 0 > > Avg Tp Write Rate (k/s) -- -- -- > > > > USAGE BY TAPE: > > Label Time Size %Nb > > daily-05 0:00 0.00.0 0 > > > > > > How can i troubleshoot amflush (I run it as amanda user) > > > > I just took a guess and did an experiment ... > > First, did you get some initial comments by amflush saying > something like "todays date is xx"? Then asking if you > really want to do this? > > == OR == > > Did you get something like: > > A. some_date > B. some_date > ... > > Then amflush asked which dumps or all do you want to flush? > > > My guess is the former; that is based on my experiment. > > I had nothing to flush, but I ran amflush. It gave me the > first dialog then "wasted" a tape and gave me a report full > of zeros like you show. > > An interesting side-effect of this was the creation of a > directory named with today's date in each of my holding disks. > They were removed at the end of the amflush run, but if amflush > were terminated early, it might appear there were dumps left > in the holding disk because of the directories existence. > > > I feel this is improper behavior on the part of amflush. > If nothing was detected that could be flushed, it seems to > me that amflush should say so and exit. But maybe there is > an explanation of which I'm unaware. I will ask on the > hacker's list if someone could explain the behavior and/or > adjust this behavior. > Just a follow-up. I posted the note to the hacker's list and JLM supplied a patch that corrected the behavior. I'm sure it will be comming to a source repository near you real soon now. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amflush problem
On Thu, Oct 14, 2004 at 11:10:47AM -0400, Frederic Medery wrote: > Hello, > every time I do a amflush i received this report : > > The dumps were flushed to tape daily-05. > The next tape Amanda expects to use is: daily-02. > > > STATISTICS: > Total Full Daily > > Estimate Time (hrs:min)0:00 > Run Time (hrs:min) 0:01 > Dump Time (hrs:min)0:00 0:00 0:00 > Output Size (meg) 0.00.00.0 > Original Size (meg) 0.00.00.0 > Avg Compressed Size (%) -- -- -- > Filesystems Dumped0 0 0 > Avg Dump Rate (k/s) -- -- -- > > Tape Time (hrs:min)0:00 0:00 0:00 > Tape Size (meg) 0.00.00.0 > Tape Used (%) 0.00.00.0 > Filesystems Taped 0 0 0 > Avg Tp Write Rate (k/s) -- -- -- > > USAGE BY TAPE: > Label Time Size %Nb > daily-05 0:00 0.00.0 0 > > > How can i troubleshoot amflush (I run it as amanda user) > I just took a guess and did an experiment ... First, did you get some initial comments by amflush saying something like "todays date is xx"? Then asking if you really want to do this? == OR == Did you get something like: A. some_date B. some_date ... Then amflush asked which dumps or all do you want to flush? My guess is the former; that is based on my experiment. I had nothing to flush, but I ran amflush. It gave me the first dialog then "wasted" a tape and gave me a report full of zeros like you show. An interesting side-effect of this was the creation of a directory named with today's date in each of my holding disks. They were removed at the end of the amflush run, but if amflush were terminated early, it might appear there were dumps left in the holding disk because of the directories existence. I feel this is improper behavior on the part of amflush. If nothing was detected that could be flushed, it seems to me that amflush should say so and exit. But maybe there is an explanation of which I'm unaware. I will ask on the hacker's list if someone could explain the behavior and/or adjust this behavior. Jon -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amflush problem
On Friday 15 October 2004 14:06, Frederic Medery wrote: >[EMAIL PROTECTED] daily]# du -sh * >11G 20040823 >117M20040910 >31G 20041012 >25G 20041014 > > >Our drive is using LTO ultrium 100/200 GB cartridge + tape Ok, that blows my alibi, so I'll go quietly, officer. :) -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.27% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: amflush problem
[EMAIL PROTECTED] daily]# du -sh * 11G 20040823 117M20040910 31G 20041012 25G 20041014 Our drive is using LTO ultrium 100/200 GB cartridge + tape Frederic Medery System Administrator LexUM, University of Montreal Gene Heskett wrote: I see that you are using a 1GB chunk size setting, and just a rather cursory mental addup of one of them indicates it would take about a 21 to 22GB tape to actually hold just the dump of pisa.lan.lexum.pri._home_projets Are your tapes that big? We apparently neglected to specifically ask that. Since amanda cannot span an individual dump (all those chunks added together again) over more than one tape, it probably totals things up and throws up its hands in defeat since the backup is bigger than the tape. The design of amanda tends to want its disklist to be rather lengthy, and broken up such that no one backup image is more than say 10% of a tape, and with a few that may be only a few megabytes, which can then allow amanda to juggle its scheduleing to facilitate a consistent amount of data (on the tape, after any gzip compression if used) each night. I have had it fill the tapes to 97+% many nights in a row without ever hitting the dreaded EOT here. Unless the budget has the sheckles for a bigger drive, I think I'd be rather inclined to rm -fR all of this, and breakup the disklist entries into smaller sized pieces and more of them. Start with the biggest one tonight, making 4 or 5 pieces (disklist entries) out of it, do the next biggest one tomorrow night, etc till you have it carved down into gigabyte or smaller hunks per entry. Or get a larger drive, much larger. See sheckles above...
Re: amflush problem
--On Friday, October 15, 2004 11:35:59 -0400 Frederic Medery <[EMAIL PROTECTED]> wrote: > > ok :) > > here is the output of amanda/daily : > total 24 > drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 . > drwxr-xr-x7 root root 4096 Aug 23 13:27 .. > drwx--2 amanda disk 4096 Aug 25 14:19 20040823 > drwx--2 amanda disk 4096 Oct 12 10:30 20040910 > drwx--2 amanda disk 4096 Oct 13 16:28 20041012 > drwx--2 amanda disk 4096 Oct 15 08:30 20041014 > > ./20040823: > total 11258772 > drwx--2 amanda disk 4096 Aug 25 14:19 . > drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 .. > -rw---1 amanda disk 1073741824 Aug 24 09:18 > sassari.lan.lexum.pri._home_workdata_archie_.1 > -rw---1 amanda disk 1073741824 Aug 24 09:18 > sassari.lan.lexum.pri._home_workdata_archie_.1.1 > -rw---1 amanda disk 1073741824 Aug 24 09:18 > sassari.lan.lexum.pri._home_workdata_archie_.1.2 > -rw---1 amanda disk 1073741824 Aug 24 09:18 > sassari.lan.lexum.pri._home_workdata_archie_.1.3 > -rw---1 amanda disk 1073741824 Aug 24 09:18 > sassari.lan.lexum.pri._home_workdata_archie_.1.4 > -rw---1 amanda disk 1073741824 Aug 24 09:18 > sassari.lan.lexum.pri._home_workdata_archie_.1.5 > -rw---1 amanda disk 1073741824 Aug 24 09:18 > sassari.lan.lexum.pri._home_workdata_archie_.1.6 > -rw---1 amanda disk 1073741824 Aug 24 09:18 > sassari.lan.lexum.pri._home_workdata_archie_.1.7 > -rw---1 amanda disk 1073741824 Aug 24 09:29 > sassari.lan.lexum.pri._home_workdata_archie_.1.8 > -rw---1 amanda disk 530968564 Aug 24 09:32 > sassari.lan.lexum.pri._home_workdata_archie_.1.9.tmp The above one is incomplete (it should get renamed without the .tmp whaen Amanda finishes the dump). > -rw---1 amanda disk 1073741824 Aug 24 11:32 > urbino.lan.lexum.pri._home_web_canlii_web.1 > -rw---1 amanda disk 213549056 Aug 24 11:35 > urbino.lan.lexum.pri._home_web_canlii_web.1.1.tmp Same here. The daily report from this run should have told you the above two didn't complete and given some indication of why it failed . > -rw---1 amanda disk 17739324 Aug 24 01:22 > urbino.lan.lexum.pri._var_lib_pgsql.1 > -rw---1 amanda disk 17984275 Aug 24 02:37 > urbino.lan.lexum.pri._var_spool_mail.0 > > ./20040910: > total 118824 > drwx--2 amanda disk 4096 Oct 12 10:30 . > drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 .. > -rw---1 amanda disk 113950 Sep 11 02:17 > modena.dmz.lexum.pri._etc_courier.0 > -rw---1 amanda disk33426 Sep 11 02:17 > modena.dmz.lexum.pri._etc_httpd.1 > -rw---1 amanda disk 48062501 Sep 11 03:11 > modena.dmz.lexum.pri._home.2 > -rw---1 amanda disk37002 Sep 11 02:17 > modena.dmz.lexum.pri._usr_lib_courier.1 > -rw---1 amanda disk 67833381 Sep 11 03:04 > modena.dmz.lexum.pri._var.0 > -rw---1 amanda disk 5428247 Sep 11 03:02 > sassari.lan.lexum.pri._home_workdata_archie_.2 > > ./20041012: > total 32444796 > drwx--2 amanda disk 4096 Oct 13 16:28 . > drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 .. > -rw---1 amanda disk 1073741824 Oct 13 04:38 > pisa.lan.lexum.pri._home_projets.0 > -rw---1 amanda disk 1073741824 Oct 13 04:41 > pisa.lan.lexum.pri._home_projets.0.1 > -rw---1 amanda disk 1073741824 Oct 13 05:01 > pisa.lan.lexum.pri._home_projets.0.10 > -rw---1 amanda disk 1073741824 Oct 13 05:03 > pisa.lan.lexum.pri._home_projets.0.11 > -rw---1 amanda disk 1073741824 Oct 13 05:05 > pisa.lan.lexum.pri._home_projets.0.12 > -rw---1 amanda disk 1073741824 Oct 13 05:07 > pisa.lan.lexum.pri._home_projets.0.13 > -rw---1 amanda disk 1073741824 Oct 13 05:09 > pisa.lan.lexum.pri._home_projets.0.14 > -rw---1 amanda disk 1073741824 Oct 13 05:11 > pisa.lan.lexum.pri._home_projets.0.15 > -rw---1 amanda disk 1073741824 Oct 13 05:14 > pisa.lan.lexum.pri._home_projets.0.16 > -rw---1 amanda disk 1073741824 Oct 13 05:16 > pisa.lan.lexum.pri._home_projets.0.17 > -rw---1 amanda disk 1073741824 Oct 13 05:18 > pisa.lan.lexum.pri._home_projets.0.18 > -rw---1 amanda disk 141387973 Oct 13 05:18 > pisa.lan.lexum.pri._home_projets.0.19 > -rw---1 amanda disk 1073741824 Oct 13 04:43 > pisa.lan.lexum.pri._home_projets.0.2 > -rw---1 amanda disk 1073741824 Oct 13 04:45 > pisa.lan.lexum.pri._home_projets.0.3 > -rw---1 amanda disk 1073741824 Oct 13 04:47 > pisa.lan.lexum.pri._home_projets.0.4 > -rw---1 amanda disk 1073741824 Oct 13 04:49 > pisa.lan.lexum.pri._home_projets.0.5 > -rw---1 amanda disk 1073741824 Oct 13 04:5
Re: amflush problem
On Friday 15 October 2004 11:35, Frederic Medery wrote: >ok :) > >here is the output of amanda/daily : >total 24 >drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 . >drwxr-xr-x7 root root 4096 Aug 23 13:27 .. >drwx--2 amanda disk 4096 Aug 25 14:19 20040823 >drwx--2 amanda disk 4096 Oct 12 10:30 20040910 >drwx--2 amanda disk 4096 Oct 13 16:28 20041012 >drwx--2 amanda disk 4096 Oct 15 08:30 20041014 Humm, what would a 'du .' show? >./20040823: >total 11258772 >drwx--2 amanda disk 4096 Aug 25 14:19 . >drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 .. >-rw---1 amanda disk 1073741824 Aug 24 09:18 >sassari.lan.lexum.pri._home_workdata_archie_.1 >-rw---1 amanda disk 1073741824 Aug 24 09:18 >sassari.lan.lexum.pri._home_workdata_archie_.1.1 >-rw---1 amanda disk 1073741824 Aug 24 09:18 >sassari.lan.lexum.pri._home_workdata_archie_.1.2 >-rw---1 amanda disk 1073741824 Aug 24 09:18 >sassari.lan.lexum.pri._home_workdata_archie_.1.3 >-rw---1 amanda disk 1073741824 Aug 24 09:18 >sassari.lan.lexum.pri._home_workdata_archie_.1.4 >-rw---1 amanda disk 1073741824 Aug 24 09:18 >sassari.lan.lexum.pri._home_workdata_archie_.1.5 >-rw---1 amanda disk 1073741824 Aug 24 09:18 >sassari.lan.lexum.pri._home_workdata_archie_.1.6 >-rw---1 amanda disk 1073741824 Aug 24 09:18 >sassari.lan.lexum.pri._home_workdata_archie_.1.7 >-rw---1 amanda disk 1073741824 Aug 24 09:29 >sassari.lan.lexum.pri._home_workdata_archie_.1.8 >-rw---1 amanda disk 530968564 Aug 24 09:32 >sassari.lan.lexum.pri._home_workdata_archie_.1.9.tmp >-rw---1 amanda disk 1073741824 Aug 24 11:32 >urbino.lan.lexum.pri._home_web_canlii_web.1 >-rw---1 amanda disk 213549056 Aug 24 11:35 >urbino.lan.lexum.pri._home_web_canlii_web.1.1.tmp >-rw---1 amanda disk 17739324 Aug 24 01:22 >urbino.lan.lexum.pri._var_lib_pgsql.1 >-rw---1 amanda disk 17984275 Aug 24 02:37 >urbino.lan.lexum.pri._var_spool_mail.0 > >./20040910: >total 118824 >drwx--2 amanda disk 4096 Oct 12 10:30 . >drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 .. >-rw---1 amanda disk 113950 Sep 11 02:17 >modena.dmz.lexum.pri._etc_courier.0 >-rw---1 amanda disk33426 Sep 11 02:17 >modena.dmz.lexum.pri._etc_httpd.1 >-rw---1 amanda disk 48062501 Sep 11 03:11 >modena.dmz.lexum.pri._home.2 >-rw---1 amanda disk37002 Sep 11 02:17 >modena.dmz.lexum.pri._usr_lib_courier.1 >-rw---1 amanda disk 67833381 Sep 11 03:04 >modena.dmz.lexum.pri._var.0 >-rw---1 amanda disk 5428247 Sep 11 03:02 >sassari.lan.lexum.pri._home_workdata_archie_.2 > >./20041012: >total 32444796 >drwx--2 amanda disk 4096 Oct 13 16:28 . >drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 .. >-rw---1 amanda disk 1073741824 Oct 13 04:38 >pisa.lan.lexum.pri._home_projets.0 >-rw---1 amanda disk 1073741824 Oct 13 04:41 >pisa.lan.lexum.pri._home_projets.0.1 >-rw---1 amanda disk 1073741824 Oct 13 05:01 >pisa.lan.lexum.pri._home_projets.0.10 >-rw---1 amanda disk 1073741824 Oct 13 05:03 >pisa.lan.lexum.pri._home_projets.0.11 >-rw---1 amanda disk 1073741824 Oct 13 05:05 >pisa.lan.lexum.pri._home_projets.0.12 >-rw---1 amanda disk 1073741824 Oct 13 05:07 >pisa.lan.lexum.pri._home_projets.0.13 >-rw---1 amanda disk 1073741824 Oct 13 05:09 >pisa.lan.lexum.pri._home_projets.0.14 >-rw---1 amanda disk 1073741824 Oct 13 05:11 >pisa.lan.lexum.pri._home_projets.0.15 >-rw---1 amanda disk 1073741824 Oct 13 05:14 >pisa.lan.lexum.pri._home_projets.0.16 >-rw---1 amanda disk 1073741824 Oct 13 05:16 >pisa.lan.lexum.pri._home_projets.0.17 >-rw---1 amanda disk 1073741824 Oct 13 05:18 >pisa.lan.lexum.pri._home_projets.0.18 >-rw---1 amanda disk 141387973 Oct 13 05:18 >pisa.lan.lexum.pri._home_projets.0.19 >-rw---1 amanda disk 1073741824 Oct 13 04:43 >pisa.lan.lexum.pri._home_projets.0.2 >-rw---1 amanda disk 1073741824 Oct 13 04:45 >pisa.lan.lexum.pri._home_projets.0.3 >-rw---1 amanda disk 1073741824 Oct 13 04:47 >pisa.lan.lexum.pri._home_projets.0.4 >-rw---1 amanda disk 1073741824 Oct 13 04:49 >pisa.lan.lexum.pri._home_projets.0.5 >-rw---1 amanda disk 1073741824 Oct 13 04:51 >pisa.lan.lexum.pri._home_projets.0.6 >-rw---1 amanda disk 1073741824 Oct 13 04:54 >pisa.lan.lexum.pri._home_projets.0.7 >-rw---1 amanda disk 1073741824 Oct 13 04:56 >pisa.lan.lexum.pri._home_projets.0.8 >-rw---1 amanda disk 1073741824 Oct 13 04:58 >pisa.lan.lexum.pri._home_projets.0.9 >-rw---1
Re: amflush problem
ok :) here is the output of amanda/daily : total 24 drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 . drwxr-xr-x7 root root 4096 Aug 23 13:27 .. drwx--2 amanda disk 4096 Aug 25 14:19 20040823 drwx--2 amanda disk 4096 Oct 12 10:30 20040910 drwx--2 amanda disk 4096 Oct 13 16:28 20041012 drwx--2 amanda disk 4096 Oct 15 08:30 20041014 ./20040823: total 11258772 drwx--2 amanda disk 4096 Aug 25 14:19 . drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 .. -rw---1 amanda disk 1073741824 Aug 24 09:18 sassari.lan.lexum.pri._home_workdata_archie_.1 -rw---1 amanda disk 1073741824 Aug 24 09:18 sassari.lan.lexum.pri._home_workdata_archie_.1.1 -rw---1 amanda disk 1073741824 Aug 24 09:18 sassari.lan.lexum.pri._home_workdata_archie_.1.2 -rw---1 amanda disk 1073741824 Aug 24 09:18 sassari.lan.lexum.pri._home_workdata_archie_.1.3 -rw---1 amanda disk 1073741824 Aug 24 09:18 sassari.lan.lexum.pri._home_workdata_archie_.1.4 -rw---1 amanda disk 1073741824 Aug 24 09:18 sassari.lan.lexum.pri._home_workdata_archie_.1.5 -rw---1 amanda disk 1073741824 Aug 24 09:18 sassari.lan.lexum.pri._home_workdata_archie_.1.6 -rw---1 amanda disk 1073741824 Aug 24 09:18 sassari.lan.lexum.pri._home_workdata_archie_.1.7 -rw---1 amanda disk 1073741824 Aug 24 09:29 sassari.lan.lexum.pri._home_workdata_archie_.1.8 -rw---1 amanda disk 530968564 Aug 24 09:32 sassari.lan.lexum.pri._home_workdata_archie_.1.9.tmp -rw---1 amanda disk 1073741824 Aug 24 11:32 urbino.lan.lexum.pri._home_web_canlii_web.1 -rw---1 amanda disk 213549056 Aug 24 11:35 urbino.lan.lexum.pri._home_web_canlii_web.1.1.tmp -rw---1 amanda disk 17739324 Aug 24 01:22 urbino.lan.lexum.pri._var_lib_pgsql.1 -rw---1 amanda disk 17984275 Aug 24 02:37 urbino.lan.lexum.pri._var_spool_mail.0 ./20040910: total 118824 drwx--2 amanda disk 4096 Oct 12 10:30 . drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 .. -rw---1 amanda disk 113950 Sep 11 02:17 modena.dmz.lexum.pri._etc_courier.0 -rw---1 amanda disk33426 Sep 11 02:17 modena.dmz.lexum.pri._etc_httpd.1 -rw---1 amanda disk 48062501 Sep 11 03:11 modena.dmz.lexum.pri._home.2 -rw---1 amanda disk37002 Sep 11 02:17 modena.dmz.lexum.pri._usr_lib_courier.1 -rw---1 amanda disk 67833381 Sep 11 03:04 modena.dmz.lexum.pri._var.0 -rw---1 amanda disk 5428247 Sep 11 03:02 sassari.lan.lexum.pri._home_workdata_archie_.2 ./20041012: total 32444796 drwx--2 amanda disk 4096 Oct 13 16:28 . drwxr-xr-x6 amanda disk 4096 Oct 14 20:00 .. -rw---1 amanda disk 1073741824 Oct 13 04:38 pisa.lan.lexum.pri._home_projets.0 -rw---1 amanda disk 1073741824 Oct 13 04:41 pisa.lan.lexum.pri._home_projets.0.1 -rw---1 amanda disk 1073741824 Oct 13 05:01 pisa.lan.lexum.pri._home_projets.0.10 -rw---1 amanda disk 1073741824 Oct 13 05:03 pisa.lan.lexum.pri._home_projets.0.11 -rw---1 amanda disk 1073741824 Oct 13 05:05 pisa.lan.lexum.pri._home_projets.0.12 -rw---1 amanda disk 1073741824 Oct 13 05:07 pisa.lan.lexum.pri._home_projets.0.13 -rw---1 amanda disk 1073741824 Oct 13 05:09 pisa.lan.lexum.pri._home_projets.0.14 -rw---1 amanda disk 1073741824 Oct 13 05:11 pisa.lan.lexum.pri._home_projets.0.15 -rw---1 amanda disk 1073741824 Oct 13 05:14 pisa.lan.lexum.pri._home_projets.0.16 -rw---1 amanda disk 1073741824 Oct 13 05:16 pisa.lan.lexum.pri._home_projets.0.17 -rw---1 amanda disk 1073741824 Oct 13 05:18 pisa.lan.lexum.pri._home_projets.0.18 -rw---1 amanda disk 141387973 Oct 13 05:18 pisa.lan.lexum.pri._home_projets.0.19 -rw---1 amanda disk 1073741824 Oct 13 04:43 pisa.lan.lexum.pri._home_projets.0.2 -rw---1 amanda disk 1073741824 Oct 13 04:45 pisa.lan.lexum.pri._home_projets.0.3 -rw---1 amanda disk 1073741824 Oct 13 04:47 pisa.lan.lexum.pri._home_projets.0.4 -rw---1 amanda disk 1073741824 Oct 13 04:49 pisa.lan.lexum.pri._home_projets.0.5 -rw---1 amanda disk 1073741824 Oct 13 04:51 pisa.lan.lexum.pri._home_projets.0.6 -rw---1 amanda disk 1073741824 Oct 13 04:54 pisa.lan.lexum.pri._home_projets.0.7 -rw---1 amanda disk 1073741824 Oct 13 04:56 pisa.lan.lexum.pri._home_projets.0.8 -rw---1 amanda disk 1073741824 Oct 13 04:58 pisa.lan.lexum.pri._home_projets.0.9 -rw---1 amanda disk 47940080 Oct 13 10:12 roma.dmz.lexum.pri._home.1 -rw---1 amanda disk 177768448 Oct 13 10:06 salerno.lan.lexum.pri._var.1 -rw---1 amanda disk 145864980 O
Re: amflush problem
On Fri, Oct 15, 2004 at 04:40:06PM +0200, Paul Bijnens wrote: > > Then a "ls -lR" of the contents of the holding directories > you believe contains data would be useful too (and the relevant > disklist entries). Add the "a" option "ls -alR" to that in order to detect any garbage "dot" files. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amflush problem
Frederic Medery wrote: I also did a grep amflush inside the amanda log dir without any result :( First it seems that you believe amanda should flush something, but when instructing amanda doing it, she believes there is nothing to flush. Also, annoying when trying to help, is that you post only part of the information (part of the log, just a statement that there are files to flush, but not a real listing). If you believe the information is too sensitive to post, you may mail to me privately. Flush problems could happen if the entries in the holdingdisk do not correspond to any DLE. Did you rearrange the disklist recently? (e.g. changing uppercase to lowercase, split up a large DLE into smaller ones etc.) First I would have a look for any message in the two files in directory ~amanda/daily log.2004MMDD.N amflush.X (MMDD is month+day, N is the counter that day, X is incremented when amflush runs, and the most recent is 1) Choose the two files that are from the same run. Then a "ls -lR" of the contents of the holding directories you believe contains data would be useful too (and the relevant disklist entries). --On Thursday, October 14, 2004 15:16:31 -0400 Frederic Medery <[EMAIL PROTECTED]> wrote: I can confirm that all my dumps are inside the directory But we can't confirm it... Prove it. Here is my amflush command : Scanning /amanda/daily... 20040823: found Amanda directory. 20040910: found Amanda directory. 20041012: found Amanda directory. Multiple Amanda directories, please pick one by letter: A. 20040823 B. 20040910 C. 20041012 Select directories to flush [A..C]: [ALL] As you can see I saw the dump I can flush, The prob occure with each dump I can't see the dump, I can only see the directories that would contain the dumps. disklist + "ls -lR" would be more convincing. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: amflush problem
here is my amcleanup :
bash-2.05b$ amcleanup daily
amcleanup: no unprocessed logfile to clean up
I also did a grep amflush inside the amanda log dir without any result :(
Frederic Medery
System Administrator
LexUM, University of Montreal
Frank Smith wrote:
--On Thursday, October 14, 2004 15:16:31 -0400 Frederic Medery <[EMAIL PROTECTED]>
wrote:
I can confirm that all my dumps are inside the directory
OK, perhaps amflush thinks amdump is still running. Try
running 'amcleanup config', if it says it did anything then
some previous amdump didn't exit cleanly. If it says there's
nothing to process then that wasn't the problem and you'll
need to keep looking.
Is anything written to Amanda's log directory (or system
logs, for that matter) when you run amflush?
Frank
Frederic Medery
System Administrator
LexUM, University of Montreal
Frank Smith wrote:
--On Thursday, October 14, 2004 13:12:22 -0400 Frederic Medery <[EMAIL PROTECTED]>
wrote:
Here is my amflush command :
Scanning /amanda/daily...
20040823: found Amanda directory.
20040910: found Amanda directory.
20041012: found Amanda directory.
Multiple Amanda directories, please pick one by letter:
A. 20040823
B. 20040910
C. 20041012
Select directories to flush [A..C]: [ALL]
As you can see I saw the dump I can flush, The prob occure with each dump
Just because the directory is there doesn't mean anything is in it. What
does an 'ls -lR' of one of those directories show? Sometimes Amanda doesn't
properly clean up the holdingdisk. The directory only gets removed if its
completely empty and sometimes there are 0 byte chunks left behind if a
client backup fails. Amflush isn't too smart and just looks for the dated
directories to ask you about but then doesn't have anything to actually
write to tape if you pick one.
Frank
Frederic Medery
System Administrator
LexUM, University of Montreal
Frank Smith wrote:
--On Thursday, October 14, 2004 11:10:47 -0400 Frederic Medery <[EMAIL PROTECTED]>
wrote:
Hello,
every time I do a amflush i received this report :
The dumps were flushed to tape daily-05.
The next tape Amanda expects to use is: daily-02.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:01
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- -- Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
Label Time Size %Nb
daily-05 0:00 0.00.0 0
How can i troubleshoot amflush (I run it as amanda user)
First make sure there is something to flush. Are there actually
files in your holdingdisk or are you running it because of a
report that says 'warning, some files may be left on holdingdisk'?
The warning just means there is a possibilty of something to flush,
not that there definately is.
Also, make sure that whatever is in your holdingdisk belongs to
the config you're trying to amflush.
I would guess there's something in your debug directory as well
(I think /tmp/amanda is the default), but I've never had occasion to
look there after an amflush.
Related question for others on the group: why does amanda mark a
tape as being used even when nothing is written to it? Shouldn't
the update to the tapelist be done only after something was written?
Frank
thanks
--
Frederic Medery
System Administrator
LexUM, University of Montreal
Re: amflush problem
--On Thursday, October 14, 2004 15:16:31 -0400 Frederic Medery <[EMAIL PROTECTED]> wrote: > I can confirm that all my dumps are inside the directory OK, perhaps amflush thinks amdump is still running. Try running 'amcleanup config', if it says it did anything then some previous amdump didn't exit cleanly. If it says there's nothing to process then that wasn't the problem and you'll need to keep looking. Is anything written to Amanda's log directory (or system logs, for that matter) when you run amflush? Frank > > Frederic Medery > System Administrator > > LexUM, University of Montreal > > > > Frank Smith wrote: > >> --On Thursday, October 14, 2004 13:12:22 -0400 Frederic Medery <[EMAIL PROTECTED]> >> wrote: >> >> >> >>> Here is my amflush command : >>> Scanning /amanda/daily... >>> 20040823: found Amanda directory. >>> 20040910: found Amanda directory. >>> 20041012: found Amanda directory. >>> >>> Multiple Amanda directories, please pick one by letter: >>> A. 20040823 >>> B. 20040910 >>> C. 20041012 >>> Select directories to flush [A..C]: [ALL] >>> >>> >>> As you can see I saw the dump I can flush, The prob occure with each dump >>> >>> >> >> Just because the directory is there doesn't mean anything is in it. What >> does an 'ls -lR' of one of those directories show? Sometimes Amanda doesn't >> properly clean up the holdingdisk. The directory only gets removed if its >> completely empty and sometimes there are 0 byte chunks left behind if a >> client backup fails. Amflush isn't too smart and just looks for the dated >> directories to ask you about but then doesn't have anything to actually >> write to tape if you pick one. >> >> Frank >> >> >> >> >>> Frederic Medery >>> System Administrator >>> >>> LexUM, University of Montreal >>> >>> >>> >>> Frank Smith wrote: >>> >>> >>> --On Thursday, October 14, 2004 11:10:47 -0400 Frederic Medery <[EMAIL PROTECTED]> wrote: > Hello, > every time I do a amflush i received this report : > > The dumps were flushed to tape daily-05. > The next tape Amanda expects to use is: daily-02. > > > STATISTICS: > Total Full Daily > > Estimate Time (hrs:min)0:00 > Run Time (hrs:min) 0:01 > Dump Time (hrs:min)0:00 0:00 0:00 > Output Size (meg) 0.00.00.0 > Original Size (meg) 0.00.00.0 > Avg Compressed Size (%) -- -- -- Filesystems Dumped > 0 0 0 > Avg Dump Rate (k/s) -- -- -- > Tape Time (hrs:min)0:00 0:00 0:00 > Tape Size (meg) 0.00.00.0 > Tape Used (%) 0.00.00.0 > Filesystems Taped 0 0 0 > Avg Tp Write Rate (k/s) -- -- -- > USAGE BY TAPE: > Label Time Size %Nb > daily-05 0:00 0.00.0 0 > > > How can i troubleshoot amflush (I run it as amanda user) > > > > First make sure there is something to flush. Are there actually files in your holdingdisk or are you running it because of a report that says 'warning, some files may be left on holdingdisk'? The warning just means there is a possibilty of something to flush, not that there definately is. Also, make sure that whatever is in your holdingdisk belongs to the config you're trying to amflush. I would guess there's something in your debug directory as well (I think /tmp/amanda is the default), but I've never had occasion to look there after an amflush. Related question for others on the group: why does amanda mark a tape as being used even when nothing is written to it? Shouldn't the update to the tapelist be done only after something was written? Frank > thanks > > -- > Frederic Medery > System Administrator > > LexUM, University of Montreal > > > > >> >> >> >> >> -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amflush problem
I can confirm that all my dumps are inside the directory
Frederic Medery
System Administrator
LexUM, University of Montreal
Frank Smith wrote:
--On Thursday, October 14, 2004 13:12:22 -0400 Frederic Medery <[EMAIL PROTECTED]>
wrote:
Here is my amflush command :
Scanning /amanda/daily...
20040823: found Amanda directory.
20040910: found Amanda directory.
20041012: found Amanda directory.
Multiple Amanda directories, please pick one by letter:
A. 20040823
B. 20040910
C. 20041012
Select directories to flush [A..C]: [ALL]
As you can see I saw the dump I can flush, The prob occure with each dump
Just because the directory is there doesn't mean anything is in it. What
does an 'ls -lR' of one of those directories show? Sometimes Amanda doesn't
properly clean up the holdingdisk. The directory only gets removed if its
completely empty and sometimes there are 0 byte chunks left behind if a
client backup fails. Amflush isn't too smart and just looks for the dated
directories to ask you about but then doesn't have anything to actually
write to tape if you pick one.
Frank
Frederic Medery
System Administrator
LexUM, University of Montreal
Frank Smith wrote:
--On Thursday, October 14, 2004 11:10:47 -0400 Frederic Medery <[EMAIL PROTECTED]>
wrote:
Hello,
every time I do a amflush i received this report :
The dumps were flushed to tape daily-05.
The next tape Amanda expects to use is: daily-02.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:01
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- -- Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
Label Time Size %Nb
daily-05 0:00 0.00.0 0
How can i troubleshoot amflush (I run it as amanda user)
First make sure there is something to flush. Are there actually
files in your holdingdisk or are you running it because of a
report that says 'warning, some files may be left on holdingdisk'?
The warning just means there is a possibilty of something to flush,
not that there definately is.
Also, make sure that whatever is in your holdingdisk belongs to
the config you're trying to amflush.
I would guess there's something in your debug directory as well
(I think /tmp/amanda is the default), but I've never had occasion to
look there after an amflush.
Related question for others on the group: why does amanda mark a
tape as being used even when nothing is written to it? Shouldn't
the update to the tapelist be done only after something was written?
Frank
thanks
--
Frederic Medery
System Administrator
LexUM, University of Montreal
Re: amflush problem
On Thu, Oct 14, 2004 at 01:45:13PM -0500, Frank Smith wrote: > --On Thursday, October 14, 2004 13:12:22 -0400 Frederic Medery <[EMAIL PROTECTED]> > wrote: > > > Here is my amflush command : > > Scanning /amanda/daily... > > 20040823: found Amanda directory. > > 20040910: found Amanda directory. > > 20041012: found Amanda directory. > > > > Multiple Amanda directories, please pick one by letter: > > A. 20040823 > > B. 20040910 > > C. 20041012 > > Select directories to flush [A..C]: [ALL] > > > > > > As you can see I saw the dump I can flush, The prob occure with each dump > > Just because the directory is there doesn't mean anything is in it. What > does an 'ls -lR' of one of those directories show? Sometimes Amanda doesn't > properly clean up the holdingdisk. The directory only gets removed if its > completely empty and sometimes there are 0 byte chunks left behind if a > client backup fails. Similar to what I was going to write. Minor addition, there could also be "garbage" file and/or directories in the holding disk directories. These would prevent the removal of the dated directories. Check the dated directories for files of size >0 with names of the format: ... The ".chunk number" will not be present for the first and/or only chunk of any DLE. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amflush problem
--On Thursday, October 14, 2004 13:12:22 -0400 Frederic Medery <[EMAIL PROTECTED]> wrote: > Here is my amflush command : > Scanning /amanda/daily... > 20040823: found Amanda directory. > 20040910: found Amanda directory. > 20041012: found Amanda directory. > > Multiple Amanda directories, please pick one by letter: > A. 20040823 > B. 20040910 > C. 20041012 > Select directories to flush [A..C]: [ALL] > > > As you can see I saw the dump I can flush, The prob occure with each dump Just because the directory is there doesn't mean anything is in it. What does an 'ls -lR' of one of those directories show? Sometimes Amanda doesn't properly clean up the holdingdisk. The directory only gets removed if its completely empty and sometimes there are 0 byte chunks left behind if a client backup fails. Amflush isn't too smart and just looks for the dated directories to ask you about but then doesn't have anything to actually write to tape if you pick one. Frank > > Frederic Medery > System Administrator > > LexUM, University of Montreal > > > > Frank Smith wrote: > >> --On Thursday, October 14, 2004 11:10:47 -0400 Frederic Medery <[EMAIL PROTECTED]> >> wrote: >> >> >> >>> Hello, >>> every time I do a amflush i received this report : >>> >>> The dumps were flushed to tape daily-05. >>> The next tape Amanda expects to use is: daily-02. >>> >>> >>> STATISTICS: >>> Total Full Daily >>> >>> Estimate Time (hrs:min)0:00 >>> Run Time (hrs:min) 0:01 >>> Dump Time (hrs:min)0:00 0:00 0:00 >>> Output Size (meg) 0.00.00.0 >>> Original Size (meg) 0.00.00.0 >>> Avg Compressed Size (%) -- -- -- Filesystems Dumped >>> 0 0 0 >>> Avg Dump Rate (k/s) -- -- -- >>> Tape Time (hrs:min)0:00 0:00 0:00 >>> Tape Size (meg) 0.00.00.0 >>> Tape Used (%) 0.00.00.0 >>> Filesystems Taped 0 0 0 >>> Avg Tp Write Rate (k/s) -- -- -- >>> USAGE BY TAPE: >>> Label Time Size %Nb >>> daily-05 0:00 0.00.0 0 >>> >>> >>> How can i troubleshoot amflush (I run it as amanda user) >>> >>> >> >> First make sure there is something to flush. Are there actually >> files in your holdingdisk or are you running it because of a >> report that says 'warning, some files may be left on holdingdisk'? >> The warning just means there is a possibilty of something to flush, >> not that there definately is. >> Also, make sure that whatever is in your holdingdisk belongs to >> the config you're trying to amflush. >> I would guess there's something in your debug directory as well >> (I think /tmp/amanda is the default), but I've never had occasion to >> look there after an amflush. >> >> Related question for others on the group: why does amanda mark a >> tape as being used even when nothing is written to it? Shouldn't >> the update to the tapelist be done only after something was written? >> >> Frank >> >> >> >>> thanks >>> >>> -- >>> Frederic Medery >>> System Administrator >>> >>> LexUM, University of Montreal >>> >>> >> >> >> >> >> -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amflush problem
Here is my amflush command :
Scanning /amanda/daily...
20040823: found Amanda directory.
20040910: found Amanda directory.
20041012: found Amanda directory.
Multiple Amanda directories, please pick one by letter:
A. 20040823
B. 20040910
C. 20041012
Select directories to flush [A..C]: [ALL]
As you can see I saw the dump I can flush, The prob occure with each dump
Frederic Medery
System Administrator
LexUM, University of Montreal
Frank Smith wrote:
--On Thursday, October 14, 2004 11:10:47 -0400 Frederic Medery <[EMAIL PROTECTED]>
wrote:
Hello,
every time I do a amflush i received this report :
The dumps were flushed to tape daily-05.
The next tape Amanda expects to use is: daily-02.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:01
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- -- Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
USAGE BY TAPE:
Label Time Size %Nb
daily-05 0:00 0.00.0 0
How can i troubleshoot amflush (I run it as amanda user)
First make sure there is something to flush. Are there actually
files in your holdingdisk or are you running it because of a
report that says 'warning, some files may be left on holdingdisk'?
The warning just means there is a possibilty of something to flush,
not that there definately is.
Also, make sure that whatever is in your holdingdisk belongs to
the config you're trying to amflush.
I would guess there's something in your debug directory as well
(I think /tmp/amanda is the default), but I've never had occasion to
look there after an amflush.
Related question for others on the group: why does amanda mark a
tape as being used even when nothing is written to it? Shouldn't
the update to the tapelist be done only after something was written?
Frank
thanks
--
Frederic Medery
System Administrator
LexUM, University of Montreal
Re: amflush problem
--On Thursday, October 14, 2004 11:10:47 -0400 Frederic Medery <[EMAIL PROTECTED]> wrote: > Hello, > every time I do a amflush i received this report : > > The dumps were flushed to tape daily-05. > The next tape Amanda expects to use is: daily-02. > > > STATISTICS: > Total Full Daily > > Estimate Time (hrs:min)0:00 > Run Time (hrs:min) 0:01 > Dump Time (hrs:min)0:00 0:00 0:00 > Output Size (meg) 0.00.00.0 > Original Size (meg) 0.00.00.0 > Avg Compressed Size (%) -- -- -- Filesystems Dumped0 > 0 0 > Avg Dump Rate (k/s) -- -- -- > Tape Time (hrs:min)0:00 0:00 0:00 > Tape Size (meg) 0.00.00.0 > Tape Used (%) 0.00.00.0 > Filesystems Taped 0 0 0 > Avg Tp Write Rate (k/s) -- -- -- > USAGE BY TAPE: > Label Time Size %Nb > daily-05 0:00 0.00.0 0 > > > How can i troubleshoot amflush (I run it as amanda user) First make sure there is something to flush. Are there actually files in your holdingdisk or are you running it because of a report that says 'warning, some files may be left on holdingdisk'? The warning just means there is a possibilty of something to flush, not that there definately is. Also, make sure that whatever is in your holdingdisk belongs to the config you're trying to amflush. I would guess there's something in your debug directory as well (I think /tmp/amanda is the default), but I've never had occasion to look there after an amflush. Related question for others on the group: why does amanda mark a tape as being used even when nothing is written to it? Shouldn't the update to the tapelist be done only after something was written? Frank > > thanks > > -- > Frederic Medery > System Administrator > > LexUM, University of Montreal -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amflush problem
On Monday 02 June 2003 15:45, Jon LaBadie wrote: > > Can anyone suggest what's going on here, and how I might flush these > > outstanding dumps ? > > Gosh those straws are hard to grasp :) > > Config changes? switch holding disk location? names? fqdn's? disklist? Fair question Jon, and I know many people often don't give sufficient information. But I gave all the information I had available. I have changed nothing. > Rebuild amanda and do an incomplete installation so part are from different > version? I take it that's a question rather than a suggestion :-) And no, I didn't do that. This my backup box, which has been happily running 2.4.3 for some time now. > Are they really dump files or other cruft? They're really dump files. > Was a dump aborted so they are incomplete? No - just ran out of disk (tape) space, so the dumps stayed in holding. > Are they possibly so old their dumps are not in the logs any longer? No - all quite recent. > Do you really need them? :)) On tape? If not does amcleanup get rid of > them? Well, I would like to have them - they're recent backups. What happens if I delete them ? Are they currently in the indices, or do they only go there when they get flushed from holding ? And anyway, this seems to be a problem now such that future held dumps will be unflushable too - I'd like to avoid that if I can. Niall
Re: amflush problem
On Mon, Jun 02, 2003 at 02:54:46PM +0100, Niall O Broin wrote: > I've been a happy amanda user for quite some time now but now I've a little > problem. I backup to disk and backups occassionally stay in holding because > of a shortage of disk space (I'm using 2.4.3 - want to upgrade soon to 2.4.4 > to be able to use autoflush). This hasn't been a problem as I just ran > amflush but now I've some dumps that I can't flush. This has happened for a > while now and I get mails like this: > > DUMP SUMMARY: > DUMPER STATS TAPER STATS > HOSTNAME DISK L ORIG-KBOUT-KB COMP% MMM:SS KB/s MMM:SS > KB/s > --- -- --- > arda /NO FILE TO FLUSH > arda /bootNO FILE TO FLUSH > bree /NO FILE TO FLUSH > bree /bootNO FILE TO FLUSH > dale /NO FILE TO FLUSH > dale /bootNO FILE TO FLUSH > > > I get this "NO FILE TO FLUSH" message for every disk in my disklist, and there > are dumps for those disks in the holding disk. > > In the last couple of days amdump doesn't seem to complete properly. Although > ps shows me no relevant processes, I have to run amcleanup - then I get the > above mail. I get the message about the unprocessed logfile and when I look > at the logfile I see: > > DISK amflush arda / > DISK amflush arda /boot > DISK amflush bree / > DISK amflush bree /boot > DISK amflush dale / > DISK amflush dale /boot > START amflush date 20030601 > START driver date 20030601 > STATS driver startup time 0.015 > START taper datestamp 20030601 label TIZdaily45 tape 0 > INFO taper tape TIZdaily45 kb 0 fm 0 [OK] > FINISH driver date 20030601 time 1.116 > > This is the entire logfile, except that I have removed a number of the > "DISK amflush" lines to shorten this mail. > > Can anyone suggest what's going on here, and how I might flush these > outstanding dumps ? Gosh those straws are hard to grasp :) Config changes? switch holding disk location? names? fqdn's? disklist? Rebuild amanda and do an incomplete installation so part are from different version? Are they really dump files or other cruft? Was a dump aborted so they are incomplete? Are they possibly so old their dumps are not in the logs any longer? (don't know if that would matter) Do you really need them? :)) On tape? If not does amcleanup get rid of them? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amflush problem
>That is what happens when I try to flush : >... > amflush: FATAL infofile update failed (chailly99,c1t1d0s3) This almost always means you have a permissions problem. Look for the "infofile" keyword in your amanda.conf. That should point to a directory. Inside there will be one directory per client, and within each of those is one directory per disk and within each of those is a file called "info". Make sure each and every directory (in particular, the ones for chailly99 and c1t1d0s3) allow your Amanda user to read, write and execute (search), and make sure the "info" file is able to be read and written. Often times what has happened is you've run an Amanda command as root. The only Amanda command you'll ever run as root is amrecover. Everything else should always be run as the Amanda user. >Nadine OLIVIER John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
