Sorry Jon, when I see backups failing especially after I put this to
production, I tend to get little overexcited and forget to give
enough information that might be usefull for others to help.
Sorry again for my limited edition posts :)
Elaborating on my earlier post:
Here is the amreport email which I got (I did write few DLEs to the
tape)
These dumps were to tape TLS-Set-1-10.
*** A TAPE ERROR OCCURRED: [[writing file: No space left on device]].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: TLS-Set-2-01.
FAILURE AND STRANGE DUMP SUMMARY:
localhost /h lev 0 FAILED [dumps too big, but cannot incremental dump new
disk]
machine2 /h3 lev 0 FAILED [dumps too big, but cannot incremental dump
new disk]
machine2 /h lev 0 FAILED [dumps too big, but cannot incremental dump
new disk]
machine2 /h2 lev 0 FAILED [dumps too big, but cannot incremental dump
new disk]
machine2 //windows/UsersG3 lev 0 STRANGE
machine2 //windows/UsersG2 lev 1 STRANGE
machine2 //windows/users lev 0 STRANGE
machine2 //windows/users lev 0 FAILED [out of tape]
STATISTICS:
Total Full Daily
-------- -------- --------
Estimate Time (hrs:min) 0:26
Run Time (hrs:min) 9:34
Dump Time (hrs:min) 8:02 5:40 2:22
Output Size (meg) 12275.1 8396.3 3878.8
Original Size (meg) 23046.4 15172.3 7874.1
Avg Compressed Size (%) 53.3 55.3 49.3 (level:#disks ...)
Filesystems Dumped 12 2 10 (1:8 2:2)
Avg Dump Rate (k/s) 434.7 420.9 467.8
Tape Time (hrs:min) 2:10 1:03 1:07
Tape Size (meg) 7577.8 3698.5 3879.3
Tape Used (%) 64.2 31.4 32.9 (level:#disks ...)
Filesystems Taped 11 1 10 (1:8 2:2)
Avg Tp Write Rate (k/s) 993.4 995.2 991.8
FAILED AND STRANGE DUMP DETAILS:
/-- machine2 //windows/UsersG3 lev 0 STRANGE
sendbackup: start [machine2://windows/UsersG3 level 0]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
--> some NT_STATUS_OBJECT_NAME_NOT_FOUND errors <--
| tar: dumped 55299 files and directories
| Total bytes written: 6503511552
sendbackup: size 6351086
sendbackup: end
\--------
/-- machine2 //windows/UsersG2 lev 1 STRANGE
sendbackup: start [machine2://windows/UsersG2 level 1]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
--> some NT_STATUS_OBJECT_NAME_NOT_FOUND errors <--
| tar: dumped 44048 files and directories
| Total bytes written: 6387213824
sendbackup: size 6237514
sendbackup: end
\--------
/-- machine2 //windows/users lev 0 STRANGE
sendbackup: start [machine2://windows/users level 0]
sendbackup: info BACKUP=/usr/bin/smbclient
sendbackup: info RECOVER_CMD=/usr/bin/smbclient -f... -
sendbackup: info end
--> some NT_STATUS_OBJECT_NAME_NOT_FOUND errors <--
| tar: dumped 119083 files and directories
| Total bytes written: 9405756416
sendbackup: size 9185309
sendbackup: end
\--------
NOTES:
planner: Adding new disk localhost:/h.
planner: Adding new disk machine2:/h.
planner: Adding new disk machine2:/h2.
planner: Adding new disk machine2:/h3.
planner: Adding new disk machine2://windows/users.
planner: Incremental of machine2:/vl bumped to level 2.
taper: tape TLS-Set-1-10 kb 11981568 fm 12 writing file: No space left on
device
driver: going into degraded mode because of tape error.
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-------------------------- --------------------------------- ------------
machine1 /h 2 64160 58912 91.8 1:16 778.4 0:581019.8
machine1 /vl 1 1449150 103744 7.2 5:12 332.0 1:421016.6
machine1 /vm 1 44820 11360 25.3 0:15 780.1 0:12 911.2
machine1 /vw 1 1280 448 35.0 0:01 452.9 0:22 20.8
machine2 -is/UsersG2 1 62375143682880 59.0 131:26 467.0 61:32 997.4
machine2 -is/UsersG3 0 63510863787296 59.6 135:14 466.7 63:26 995.2
machine2 -osis/users 0 91853094810515 52.4 205:11 390.8 FAILED ----
machine2 /h 0 FAILED ---------------------------------------
machine2 /h2 0 FAILED ---------------------------------------
machine2 /h3 0 FAILED ---------------------------------------
machine2 /vl 2 61570 5472 8.9 0:18 301.9 0:07 775.6
machine2 /vw 1 178790 106368 59.5 2:56 605.1 1:451017.6
localhost /h 0 FAILED ---------------------------------------
localhost /rp 1 21770 2752 12.6 0:021267.3 0:04 694.1
localhost /vl 1 1790 160 8.9 0:01 172.7 0:02 77.9
localhost /vw 1 2280 320 14.0 0:05 52.9 0:02 186.0
(brought to you by Amanda version 2.4.3)
----- Original Message -----
From: "Jon LaBadie" <jon AT jgcomp DOT com>
To: <amanda-users AT amanda DOT org>
Sent: Saturday, October 18, 2003 10:14 PM
Subject: Re: tape type for HP DDS3 C5708A
> On Sat, Oct 18, 2003 at 01:22:49PM +0530, Rohit wrote:
> > This was the output of the tapetype program after running for
> > several hours (maybe close to 8 hours or so). I then included
> > this in my tapetype defination in amanda.conf. But when amanda
> > ran yesterday night, it complained about "No space left on
> > the device" and left one share in the holding space.
> >
> > How come this error? Did tapetype estimate more then what my
> > tape can hold?
> >
> > Thanks!
> >
> >
> > ----- Original Message -----
> > From: "Rohit" <rohit AT genetechindia DOT com>
> > To: <amanda-users AT amanda DOT org>
> > Sent: Friday, October 17, 2003 9:33 PM
> > Subject: tape type for HP DDS3 C5708A
> >
> >
> > > tape type for HP DDS3 C5708A:
> > >
> > > define tapetype HP-DDS3 {
> > > comment "just produced by tapetype program"
> > > length 11796 mbytes
> > > filemark 0 kbytes
> > > speed 975 kps
> > > }
> >
>
> Based on the substantial number of other DDS3 tapetypes
> that have been posted (including my own) these are fine
> and appropriate values.
>
>
> But please Rohit, don't give us a little tidbit of information
> and expect a comprehensive, accurate response.
>
> "no space left on device"
>
> Gee, when did that happen? Did that message pop up in isolation?
> Or was it part of a more larger report? Did the report show
> that anything worked? Were any DLE's taped? How many, how much?
> Did you try to write 4000Gb on to that tiny 12Gb tape?
>
> Right now I'd guess that latter happened. Only a guess.
>
> But 2 days ago I made a wrong guess that you did not have
> a configuration problem. That guess, like this one, was
> based on limited information. When you provided more data
> Paul B pointed out it was clear you did have a config problem.
>
> You see a lot more information about your installation that
> we do. Help us see that same things so the list is better
> able to help you.
>
> --
> Jon H. LaBadie jon AT jgcomp DOT com
> JG Computing
> 4455 Province Line Road (609) 252-0159
> Princeton, NJ 08540-4322 (609) 683-7220 (fax)
|
