amflush fails with 'taper: FATAL Can't locate auto/Amanda/Device/Device/swig_volume.al'
Greetings: My system is ALL 3.3.0 (brand new) and has been working for the past few weeks. I keep adding additional clients, etc, but am now pretty well ready to go live. Yesterday, I ran another test backup, but received errors indicating the tape drive wasn't ready (strange enough), but that the backups were still held in the holding disks (I have two). ~ *** A TAPE ERROR OCCURRED: [while waiting for 'tape:/dev/nst0' to become ready: Can't open tape device /dev/nst0: Device or resource busy]. There are 378G of dumps left in the holding disk. They will be flushed on the next run. ~ Okay, so I think the tape drive is ready, it indicates 'Online' and 'Ready', tape '06L4' is in the drive (LTO4). I execute 'amflush WEEKLY', and receive the below message in my eMail: ~ The next 2 tapes Amanda expects to use are: 06L4, 07L4. FAILURE DUMP SUMMARY: taper: FATAL Can't locate auto/Amanda/Device/Device/swig_volume.al in @INC (@INC contains: @amperldir@ /usr/lib/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Device.pm line 34 ~ In the 'dump summary' section of the report, it indicates for each client NO FILE TO FLUSH. Yet, there are almost 400GB of files in my holding disks waiting to be flushed to tape. I haven't, so far, been able to find anything that looks like this error. Any suggestions? Thanks! Neil
Re: amflush fails with 'taper: FATAL Can't locate auto/Amanda/Device/Device/swig_volume.al'
Neil, I'd had a variety of tape errors, one of the linux boxes will occasionally drop the driver for the robot on the floor. My most recent problem was timeouts to the LTO5 in my G2 juke attached to a Solaris x86 box. The answers very and you have to run the checklist, the linux box, you unload and reload the driver # modprobe -r aic79xx; sleep 120; modprobe -a aic79xx For the G2, we updated FW, rebooted the host, rebooted the juke and will marginal success. Interestingly we haven't seen any problems since I reseated the ESAS cable that connects it to its host. I hate to say it, but there is no one fix works for all here. Let us know how you make out, if your proding shows anything else strange it may trip a memory for me, or finding something novel, I'll add it to my (mental) checklist. On Thu, Jan 19, 2012 at 10:24:23AM -0600, Neil Carter wrote: Greetings: My system is ALL 3.3.0 (brand new) and has been working for the past few weeks. I keep adding additional clients, etc, but am now pretty well ready to go live. Yesterday, I ran another test backup, but received errors indicating the tape drive wasn't ready (strange enough), but that the backups were still held in the holding disks (I have two). ~ *** A TAPE ERROR OCCURRED: [while waiting for 'tape:/dev/nst0' to become ready: Can't open tape device /dev/nst0: Device or resource busy]. There are 378G of dumps left in the holding disk. They will be flushed on the next run. ~ Okay, so I think the tape drive is ready, it indicates 'Online' and 'Ready', tape '06L4' is in the drive (LTO4). I execute 'amflush WEEKLY', and receive the below message in my eMail: ~ The next 2 tapes Amanda expects to use are: 06L4, 07L4. FAILURE DUMP SUMMARY: taper: FATAL Can't locate auto/Amanda/Device/Device/swig_volume.al in @INC (@INC contains: @amperldir@ /usr/lib/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Device.pm line 34 ~ In the 'dump summary' section of the report, it indicates for each client NO FILE TO FLUSH. Yet, there are almost 400GB of files in my holding disks waiting to be flushed to tape. I haven't, so far, been able to find anything that looks like this error. Any suggestions? Thanks! Neil --- Brian R Cuttler brian.cutt...@wadsworth.org Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 IMPORTANT NOTICE: This e-mail and any attachments may contain confidential or sensitive information which is, or may be, legally privileged or otherwise protected by law from further disclosure. It is intended only for the addressee. If you received this in error or from someone who was not authorized to send it to you, please do not distribute, copy or use it or any attachments. Please notify the sender immediately by reply e-mail and delete this from your system. Thank you for your cooperation.
Re: amflush fails with 'taper: FATAL Can't locate auto/Amanda/Device/Device/swig_volume.al'
neil, Can you post the changer state file. Run the following command and post the result: amtape CONFIG inventory amtape CONFIG update Try a new amflush or amdump. Jean-Louis On 01/19/2012 11:24 AM, Neil Carter wrote: Greetings: My system is ALL 3.3.0 (brand new) and has been working for the past few weeks. I keep adding additional clients, etc, but am now pretty well ready to go live. Yesterday, I ran another test backup, but received errors indicating the tape drive wasn't ready (strange enough), but that the backups were still held in the holding disks (I have two). ~ *** A TAPE ERROR OCCURRED: [while waiting for 'tape:/dev/nst0' to become ready: Can't open tape device /dev/nst0: Device or resource busy]. There are 378G of dumps left in the holding disk. They will be flushed on the next run. ~ Okay, so I think the tape drive is ready, it indicates 'Online' and 'Ready', tape '06L4' is in the drive (LTO4). I execute 'amflush WEEKLY', and receive the below message in my eMail: ~ The next 2 tapes Amanda expects to use are: 06L4, 07L4. FAILURE DUMP SUMMARY: taper: FATAL Can't locate auto/Amanda/Device/Device/swig_volume.al in @INC (@INC contains: @amperldir@ /usr/lib/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Device.pm line 34 ~ In the 'dump summary' section of the report, it indicates for each client NO FILE TO FLUSH. Yet, there are almost 400GB of files in my holding disks waiting to be flushed to tape. I haven't, so far, been able to find anything that looks like this error. Any suggestions? Thanks! Neil
Re: amflush fails with 'taper: FATAL Can't locate auto/Amanda/Device/Device/swig_volume.al'
Greetings: Attached are the changer.conf file, the results of the two commands you requested, and the eMailed result from another attempted amflush. Thanks! Neil On 2012.01.19 10:51 AM, Jean-Louis Martineau wrote: neil, Can you post the changer state file. Run the following command and post the result: amtape CONFIG inventory amtape CONFIG update Try a new amflush or amdump. Jean-Louis On 01/19/2012 11:24 AM, Neil Carter wrote: Greetings: My system is ALL 3.3.0 (brand new) and has been working for the past few weeks. I keep adding additional clients, etc, but am now pretty well ready to go live. Yesterday, I ran another test backup, but received errors indicating the tape drive wasn't ready (strange enough), but that the backups were still held in the holding disks (I have two). ~ *** A TAPE ERROR OCCURRED: [while waiting for 'tape:/dev/nst0' to become ready: Can't open tape device /dev/nst0: Device or resource busy]. There are 378G of dumps left in the holding disk. They will be flushed on the next run. ~ Okay, so I think the tape drive is ready, it indicates 'Online' and 'Ready', tape '06L4' is in the drive (LTO4). I execute 'amflush WEEKLY', and receive the below message in my eMail: ~ The next 2 tapes Amanda expects to use are: 06L4, 07L4. FAILURE DUMP SUMMARY: taper: FATAL Can't locate auto/Amanda/Device/Device/swig_volume.al in @INC (@INC contains: @amperldir@ /usr/lib/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Device.pm line 34 ~ In the 'dump summary' section of the report, it indicates for each client NO FILE TO FLUSH. Yet, there are almost 400GB of files in my holding disks waiting to be flushed to tape. I haven't, so far, been able to find anything that looks like this error. Any suggestions? Thanks! Neil changer.conf Description: Binary data eMailed_amflush_report.rtf Description: MS-Word document amtape_commands_results.rtf Description: MS-Word document
Re: amflush fails with 'taper: FATAL Can't locate auto/Amanda/Device/Device/swig_volume.al'
Greetings: GOT IT!! I found the following in the taper.20120119111247.debug file: Thu Jan 19 11:12:48 2012: taper: SL24: polling 'tape:/dev/nst0' to see if it's ready *_Thu Jan 19 11:12:50 2012: taper: Empty amanda header: buflen=32768 lsize=32768 buf='' Thu Jan 19 11:12:50 2012: taper: strange amanda header: Thu Jan 19 11:12:50 2012: taper: Expected: Non-empty line Actual: null Thu Jan 19 11:12:50 2012: taper: Device tape:/dev/nst0 error = 'No tapestart header -- unlabeled device?' Thu Jan 19 11:12:50 2012: taper: Device tape:/dev/nst0 setting status flag(s): DEVICE_STATUS_VOLUME_UNLABELED Thu Jan 19 11:12:50 2012: taper: SL24: Expected label '06L4', but got an unlabeled tape_* Thu Jan 19 11:12:50 2012: taper: critical (fatal): Can't locate auto/Amanda/Device/Device/swig_volume.al in @INC (@INC contains: @amperldir@ /usr/lib/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl /5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/ vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Device.pm line 34 It turns out that, somehow, the tape in question, '06L4' didn't get labeled. This is strange, as I went back in my .bash_history file and found where I'd used amlabel to label all of the first 12 tapes. Oh well... I ran it again and now the flush is running properly. Once again, log files are your friend! (If you can find all of them...) Thanks, everyone! Neil On 2012.01.19 10:51 AM, Jean-Louis Martineau wrote: neil, Can you post the changer state file. Run the following command and post the result: amtape CONFIG inventory amtape CONFIG update Try a new amflush or amdump. Jean-Louis On 01/19/2012 11:24 AM, Neil Carter wrote: Greetings: My system is ALL 3.3.0 (brand new) and has been working for the past few weeks. I keep adding additional clients, etc, but am now pretty well ready to go live. Yesterday, I ran another test backup, but received errors indicating the tape drive wasn't ready (strange enough), but that the backups were still held in the holding disks (I have two). ~ *** A TAPE ERROR OCCURRED: [while waiting for 'tape:/dev/nst0' to become ready: Can't open tape device /dev/nst0: Device or resource busy]. There are 378G of dumps left in the holding disk. They will be flushed on the next run. ~ Okay, so I think the tape drive is ready, it indicates 'Online' and 'Ready', tape '06L4' is in the drive (LTO4). I execute 'amflush WEEKLY', and receive the below message in my eMail: ~ The next 2 tapes Amanda expects to use are: 06L4, 07L4. FAILURE DUMP SUMMARY: taper: FATAL Can't locate auto/Amanda/Device/Device/swig_volume.al in @INC (@INC contains: @amperldir@ /usr/lib/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at /usr/lib/perl5/site_perl/5.8.8/Amanda/Device.pm line 34 ~ In the 'dump summary' section of the report, it indicates for each client NO FILE TO FLUSH. Yet, there are almost 400GB of files in my holding disks waiting to be flushed to tape. I haven't, so far, been able to find anything that looks like this error. Any suggestions? Thanks! Neil
amflush fails
Hi all,
last day's dump of Amanda (version 2.5.1b1) failed and files were
left over in the holding disk. So I tried to do an amflush which
also fails, nearly immediately. Below is some more info:
logfile amflush.1:
amflush: start at Thu Aug 24 13:02:54 CEST 2006
amflush: datestamp 20060824130248
amflush: Can't fdopen: Illegal seek
driver: pid 29589 executable driver version 2.5.1b1
driver: Did not get DATE line from planner
logfile log.20060824130248.0:
DISK amflush corrente.localnet /boot
DISK amflush corrente.localnet /
DISK amflush corrente.localnet /home
DISK amflush corrente.localnet /home/charles/pictures
DISK amflush corrente.localnet /home/charles/vmware-4
DISK amflush corrente.localnet /local
DISK amflush corrente.localnet /opt
DISK amflush corrente.localnet /usr
DISK amflush corrente.localnet /usr/local
DISK amflush corrente.localnet /var
START amflush date 20060824130248
FATAL amflush Can't fdopen: Illegal seek
FATAL driver Did not get DATE line from planner
and the mailed report is
From: [EMAIL PROTECTED] (Amanda)
*** THE DUMPS DID NOT FINISH PROPERLY!
The next tape Amanda expects to use is: daily-05.
FAILURE AND STRANGE DUMP SUMMARY:
amflush: FATAL Can't fdopen: Illegal seek
driver: FATAL Did not get DATE line from planner
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
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
Chunks Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- - -
corrente.loc / NO FILE TO FLUSH --
corrente.loc /boot NO FILE TO FLUSH --
corrente.loc /home NO FILE TO FLUSH --
corrente.loc -s/pictures NO FILE TO FLUSH --
corrente.loc -s/vmware-4 NO FILE TO FLUSH --
corrente.loc /localNO FILE TO FLUSH --
corrente.loc /opt NO FILE TO FLUSH --
corrente.loc /usr NO FILE TO FLUSH --
corrente.loc /usr/localNO FILE TO FLUSH --
corrente.loc /var NO FILE TO FLUSH --
(brought to you by Amanda version 2.5.1b1)
I have tried to use amflush before and it never succeeded, I always
got the same problem, but than I ignored the problem as the dumps
started to run smoothly. I am rather new to Amanda.
Can anybody shed some light? This is an RPM installation of Amanda
version 2.5.1b1 on SuSE 10.0, currently a single PC as client-server.
Regards,
Charles Stroom
email: charles at stremen dot xs4all dot nl
Re: amflush fails
On Thu, Aug 24, 2006 at 01:17:14PM +0200, Charles Stroom wrote:
Hi all,
last day's dump of Amanda (version 2.5.1b1) failed and files were
left over in the holding disk. So I tried to do an amflush which
also fails, nearly immediately. Below is some more info:
logfile amflush.1:
amflush: start at Thu Aug 24 13:02:54 CEST 2006
amflush: datestamp 20060824130248
amflush: Can't fdopen: Illegal seek
driver: pid 29589 executable driver version 2.5.1b1
driver: Did not get DATE line from planner
logfile log.20060824130248.0:
DISK amflush corrente.localnet /boot
DISK amflush corrente.localnet /
DISK amflush corrente.localnet /home
DISK amflush corrente.localnet /home/charles/pictures
DISK amflush corrente.localnet /home/charles/vmware-4
DISK amflush corrente.localnet /local
DISK amflush corrente.localnet /opt
DISK amflush corrente.localnet /usr
DISK amflush corrente.localnet /usr/local
DISK amflush corrente.localnet /var
START amflush date 20060824130248
FATAL amflush Can't fdopen: Illegal seek
FATAL driver Did not get DATE line from planner
and the mailed report is
From: [EMAIL PROTECTED] (Amanda)
*** THE DUMPS DID NOT FINISH PROPERLY!
The next tape Amanda expects to use is: daily-05.
FAILURE AND STRANGE DUMP SUMMARY:
amflush: FATAL Can't fdopen: Illegal seek
driver: FATAL Did not get DATE line from planner
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
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
Chunks Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- - -
corrente.loc / NO FILE TO FLUSH --
corrente.loc /boot NO FILE TO FLUSH --
corrente.loc /home NO FILE TO FLUSH --
corrente.loc -s/pictures NO FILE TO FLUSH --
corrente.loc -s/vmware-4 NO FILE TO FLUSH --
corrente.loc /localNO FILE TO FLUSH --
corrente.loc /opt NO FILE TO FLUSH --
corrente.loc /usr NO FILE TO FLUSH --
corrente.loc /usr/localNO FILE TO FLUSH --
corrente.loc /var NO FILE TO FLUSH --
(brought to you by Amanda version 2.5.1b1)
I have tried to use amflush before and it never succeeded, I always
got the same problem, but than I ignored the problem as the dumps
started to run smoothly. I am rather new to Amanda.
Can anybody shed some light? This is an RPM installation of Amanda
version 2.5.1b1 on SuSE 10.0, currently a single PC as client-server.
I guess my first question would be,
are there any amanda dumps on your holding disk?
Try an ls -lR on the hold 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 fails
Charles,
It's a bug 2.5.1b1.
Upgrade to 2.5.1b2, latest cvs or latest snapshot
from http://www.iro.umontreal.ca/~martinea/amanda
We are close of a stable 2.5.1 release.
Jean-Louis
Charles Stroom wrote:
Hi all,
last day's dump of Amanda (version 2.5.1b1) failed and files were
left over in the holding disk. So I tried to do an amflush which
also fails, nearly immediately. Below is some more info:
logfile amflush.1:
amflush: start at Thu Aug 24 13:02:54 CEST 2006
amflush: datestamp 20060824130248
amflush: Can't fdopen: Illegal seek
driver: pid 29589 executable driver version 2.5.1b1
driver: Did not get DATE line from planner
logfile log.20060824130248.0:
DISK amflush corrente.localnet /boot
DISK amflush corrente.localnet /
DISK amflush corrente.localnet /home
DISK amflush corrente.localnet /home/charles/pictures
DISK amflush corrente.localnet /home/charles/vmware-4
DISK amflush corrente.localnet /local
DISK amflush corrente.localnet /opt
DISK amflush corrente.localnet /usr
DISK amflush corrente.localnet /usr/local
DISK amflush corrente.localnet /var
START amflush date 20060824130248
FATAL amflush Can't fdopen: Illegal seek
FATAL driver Did not get DATE line from planner
and the mailed report is
From: [EMAIL PROTECTED] (Amanda)
*** THE DUMPS DID NOT FINISH PROPERLY!
The next tape Amanda expects to use is: daily-05.
FAILURE AND STRANGE DUMP SUMMARY:
amflush: FATAL Can't fdopen: Illegal seek
driver: FATAL Did not get DATE line from planner
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
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
Chunks Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- - -
corrente.loc / NO FILE TO FLUSH --
corrente.loc /boot NO FILE TO FLUSH --
corrente.loc /home NO FILE TO FLUSH --
corrente.loc -s/pictures NO FILE TO FLUSH --
corrente.loc -s/vmware-4 NO FILE TO FLUSH --
corrente.loc /localNO FILE TO FLUSH --
corrente.loc /opt NO FILE TO FLUSH --
corrente.loc /usr NO FILE TO FLUSH --
corrente.loc /usr/localNO FILE TO FLUSH --
corrente.loc /var NO FILE TO FLUSH --
(brought to you by Amanda version 2.5.1b1)
I have tried to use amflush before and it never succeeded, I always
got the same problem, but than I ignored the problem as the dumps
started to run smoothly. I am rather new to Amanda.
Can anybody shed some light? This is an RPM installation of Amanda
version 2.5.1b1 on SuSE 10.0, currently a single PC as client-server.
Regards,
Charles Stroom
email: charles at stremen dot xs4all dot nl
Re: amflush fails
On Thursday 24 August 2006 10:29, Jean-Louis Martineau wrote:
Charles,
It's a bug 2.5.1b1.
Upgrade to 2.5.1b2, latest cvs or latest snapshot
from http://www.iro.umontreal.ca/~martinea/amanda
We are close of a stable 2.5.1 release.
Jean-Louis
Jean-Louis: Is it safe to try last nights snapshot?
I have it and have built it, but didn't install it yet. I had sent in a
bunch of logs to the hackers-list that I could duplicate while running
anything newer than 2.5.0-20060424 at about the time you went on vacation,
and which in some respects resembled the problems being reported here
recently. I went back to 2.5.0-20060424 in the meantime. I was in
upstate MI from 1 May to 15 July, working out of an HP lappy, so I wasn't
able to play my usual canary in the coal mine early alert till I got back
ran smack dab into all kinds of troubles with anything labeled
2.5.1anything, usually on the second run after an install.
Charles Stroom wrote:
Hi all,
last day's dump of Amanda (version 2.5.1b1) failed and files were
left over in the holding disk. So I tried to do an amflush which
also fails, nearly immediately. Below is some more info:
logfile amflush.1:
amflush: start at Thu Aug 24 13:02:54 CEST 2006
amflush: datestamp 20060824130248
amflush: Can't fdopen: Illegal seek
driver: pid 29589 executable driver version 2.5.1b1
driver: Did not get DATE line from planner
logfile log.20060824130248.0:
DISK amflush corrente.localnet /boot
DISK amflush corrente.localnet /
DISK amflush corrente.localnet /home
DISK amflush corrente.localnet /home/charles/pictures
DISK amflush corrente.localnet /home/charles/vmware-4
DISK amflush corrente.localnet /local
DISK amflush corrente.localnet /opt
DISK amflush corrente.localnet /usr
DISK amflush corrente.localnet /usr/local
DISK amflush corrente.localnet /var
START amflush date 20060824130248
FATAL amflush Can't fdopen: Illegal seek
FATAL driver Did not get DATE line from planner
and the mailed report is
From: [EMAIL PROTECTED] (Amanda)
*** THE DUMPS DID NOT FINISH PROPERLY!
The next tape Amanda expects to use is: daily-05.
FAILURE AND STRANGE DUMP SUMMARY:
amflush: FATAL Can't fdopen: Illegal seek
driver: FATAL Did not get DATE line from planner
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
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
Chunks Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
DUMP SUMMARY:
DUMPER STATS TAPER
STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s
MMM:SS KB/s --
- - corrente.loc /
NO FILE TO FLUSH -- corrente.loc
/boot NO FILE TO FLUSH --
corrente.loc /home NO FILE TO FLUSH
-- corrente.loc -s/pictures NO FILE
TO FLUSH -- corrente.loc -s/vmware-4
NO FILE TO FLUSH -- corrente.loc /local
NO FILE TO FLUSH -- corrente.loc
/opt NO FILE TO FLUSH --
corrente.loc /usr NO FILE TO FLUSH
-- corrente.loc /usr/localNO FILE
TO FLUSH -- corrente.loc /var
NO FILE TO FLUSH --
(brought to you by Amanda version 2.5.1b1)
I have tried to use amflush before and it never succeeded, I always
got the same problem, but than I ignored the problem as the dumps
started to run smoothly. I am rather new to Amanda.
Can anybody shed some light? This is an RPM installation of Amanda
version 2.5.1b1 on SuSE 10.0, currently a single PC as client-server.
Regards,
Charles Stroom
email: charles at stremen dot xs4all dot nl
--
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)
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 fails
Thanks. As I have a Suse specific RPM installation, I might prefer to wait until 2.5.1 is made available in RPM. To John LaBadie: yes, there were dumps! ls /work-2/amanda/dumps/20060824110501 . corrente.localnet._usr.0 .. corrente.localnet._usr.0.1 corrente.localnet._.1 corrente.localnet._usr.0.2 corrente.localnet._home.1 corrente.localnet._usr.0.3 corrente.localnet._home_charles_pictures.1 corrente.localnet._usr.0.4 corrente.localnet._home_charles_vmware-4.1 corrente.localnet._usr_local.1 corrente.localnet._local.1 corrente.localnet._var.1 corrente.localnet._opt.1 Regards, Charles Stroom email: charles at stremen dot xs4all dot nl --- Original Message on Thu, 24 Aug 2006 10:29:57 EDT Jean-Louis Martineau [EMAIL PROTECTED] wrote: Charles, It's a bug 2.5.1b1. Upgrade to 2.5.1b2, latest cvs or latest snapshot from http://www.iro.umontreal.ca/~martinea/amanda We are close of a stable 2.5.1 release. Jean-Louis Charles Stroom wrote: Hi all, last day's dump of Amanda (version 2.5.1b1) failed and files were left over in the holding disk. So I tried to do an amflush which also fails, nearly immediately. Below is some more info: logfile amflush.1: amflush: start at Thu Aug 24 13:02:54 CEST 2006 amflush: datestamp 20060824130248 amflush: Can't fdopen: Illegal seek driver: pid 29589 executable driver version 2.5.1b1 driver: Did not get DATE line from planner logfile log.20060824130248.0: DISK amflush corrente.localnet /boot DISK amflush corrente.localnet / DISK amflush corrente.localnet /home DISK amflush corrente.localnet /home/charles/pictures DISK amflush corrente.localnet /home/charles/vmware-4 DISK amflush corrente.localnet /local DISK amflush corrente.localnet /opt DISK amflush corrente.localnet /usr DISK amflush corrente.localnet /usr/local DISK amflush corrente.localnet /var START amflush date 20060824130248 FATAL amflush Can't fdopen: Illegal seek FATAL driver Did not get DATE line from planner etc.
Re: amflush fails
On Thu, Aug 24, 2006 at 06:16:03PM +0200, Charles Stroom wrote: Thanks. As I have a Suse specific RPM installation, I might prefer to wait until 2.5.1 is made available in RPM. To John LaBadie: yes, there were dumps! My question was moot once JLM noted it was a know and fixed defect. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
