Re: changer wont unload drive
On Wed, Dec 08, 2004 at 12:46:36PM -0800, Ping Wing wrote: > Hi. > > I have TSL-11000 drive with only 1 dds4 tape. Only ONE tape. Amanda was designed with the expectation of a substantial number of tapes used in a rotation. > > When drive is unloaded, like this: > > # mtx -f /dev/sg1 status > Storage Changer /dev/sg1:1 Drives, 8 Slots ( 0 Import/Export ) > Data Transfer Element 0:Empty > Storage Element 1:Empty > Storage Element 2:Empty > Storage Element 3:Empty > Storage Element 4:Empty > Storage Element 5:Empty > Storage Element 6:Empty > Storage Element 7:Empty > Storage Element 8:Full > > > and I do amdump everthing runs fine. > Now I do amdump again and it complains that new tape was not found in rack. The minimum number of tapes you will rotate is listed in the "tapecycle" parameter of amanda.conf. If that number is more than one, then amanda is looking for the next "new", i.e. not previously used by amanda, tape -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Sloooow IBM drive...
Daniel Bentley wrote: Just recently purchased an IBM 200/400G LTO-2 (internal) drive. And the sucker is -SLOW-. Amtapetype ran for over 24 hours and didn't finish. Did you give the "-e 200g" option? If not, that's normal. Read the man page again. Amtapetype also gives an approximation of the total expected run time after a few minutes already, what does it indicate? -- 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: Question using amflush
Just to update this. I tried it again (choosing a different directory and in the foreground). This is the current ps -ef |grep amanda: amanda 30890 30809 76 17:13 pts/000:02:23 amflush -f normal amanda 30891 30890 0 17:13 pts/000:00:00 driver normal nodump amanda 30892 30891 0 17:13 pts/000:00:00 taper normal amanda 30893 30892 0 17:13 pts/000:00:00 taper normal In addition this is the current output from the job: Flushing dumps in 20041207 to tape drive "/dev/nst0". Expecting tape Normal20 or a new tape. (The last dumps were to tape Normal19) Are you sure you want to do this [yN]? y amflush: datestamp 20041208 driver: pid 30891 executable driver version 2.4.3 taper: pid 30892 executable taper version 2.4.3 driver: send-cmd time 5.087 to taper: START-TAPER 20041208 driver: adding holding disk 0 dir /var/holding size 296960 reserving 296960 out of 296960 for degraded-mode dumps taper: page size is 4096 taper: buffer size is 32768 taper: buffer[00] at 0x400df000 taper: buffer[01] at 0x400e7000 taper: buffer[02] at 0x400ef000 taper: buffer[03] at 0x400f7000 taper: buffer[04] at 0x400ff000 taper: buffer[05] at 0x40107000 taper: buffer[06] at 0x4010f000 taper: buffer[07] at 0x40117000 taper: buffer[08] at 0x4011f000 taper: buffer[09] at 0x40127000 taper: buffer[10] at 0x4012f000 taper: buffer[11] at 0x40137000 taper: buffer[12] at 0x4013f000 taper: buffer[13] at 0x40147000 taper: buffer[14] at 0x4014f000 taper: buffer[15] at 0x40157000 taper: buffer[16] at 0x4015f000 taper: buffer[17] at 0x40167000 taper: buffer[18] at 0x4016f000 taper: buffer[19] at 0x40177000 taper: buffer structures at 0x4017f000 for 240 bytes taper: read label `Normal20' date `X' I hope this sheds some lite on the matter. I did notice date `X' comment that confuses me somewhat... Paul Bijnens <[EMAIL PROTECTED]> wrote: > James Marcinek wrote: > > > > I've recently deployed amanda. The client forgot tapes on several occasions and > > I've got 4 backups in my holding area. I initiated the amflush command and > > followed the instructions. The job kicked off in the background and I've been > > using: > > > > ps -ef |grep amanda > > > > to see if the process is still running, which it is. When I do a top command > > it's using lots of CPU time. > > Which process is taking CPU time? planner? driver? taper? > > > > > It's been runninng for several hours now and my logs haven't been populating > > since it started. Here's the last few entries: > > > > START amflush date 20041207 > > START driver date 20041207 > > START taper datestamp 20041207 label Normal18 tape 0 > > > > I'm a bit confused because I now see a folder 20041207 in my /var/holding. It's > > empty, which is good if it's working properly. > > For flush, that's normal. > > > > > Why isn't anything being populated too(amflush and log file)? Is there any way > > to tell if it's running properly? > > On linux:strace -p The-PID > on Solaris: truss -p The-PID > > "lsof -o the-PID" tells you which files are opened, and sometimes can > give a hint what it is doing (e.g. which file it is reading/writing). > > (hit Ctrl-C to stop it). > > PS. have also a look at "autoflush on": when forgetting a tape once, > the next time, amanda flushes automatically. > > -- > 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 * > *** > -- James Marcinek Systems Engineer JEMConsult.biz, Inc 813.416.1324
changer wont unload drive
Hi. I have TSL-11000 drive with only 1 dds4 tape. When drive is unloaded, like this: # mtx -f /dev/sg1 status Storage Changer /dev/sg1:1 Drives, 8 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Empty Storage Element 2:Empty Storage Element 3:Empty Storage Element 4:Empty Storage Element 5:Empty Storage Element 6:Empty Storage Element 7:Empty Storage Element 8:Full and I do amdump everthing runs fine. Now I do amdump again and it complains that new tape was not found in rack. # mtx -f /dev/sg1 status Storage Changer /dev/sg1:1 Drives, 8 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element 1:Empty Storage Element 2:Empty Storage Element 3:Empty Storage Element 4:Empty Storage Element 5:Empty Storage Element 6:Empty Storage Element 7:Empty Storage Element 8:Empty Questin is that why doesnt changer (chg-zd-mtx doesnt unload it ?). in /etc/amanda/Conf1/chg-scsi-linux.conf I have : firstslot=8 lastslot=8 cleanslot=-1 #autoclean=1 #autocleancount=99 offline_before_unload=0 unloadpause=0 #cleancycle=120 __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo
Sloooow IBM drive...
Just recently purchased an IBM 200/400G LTO-2 (internal) drive. And the sucker is -SLOW-. Amtapetype ran for over 24 hours and didn't finish. I'm running the Bacula tape test util right now for a full tape write, and in the past... 21 hours, it's progressed to 14G, and reporting a rate of around 200 KB/s. Now, for a drive that reads 'up to 35MB/sec native data transfer rate (70 MB/sec with 2:1 compression)' for sustained data transfer rate on the product datasheet (I know, I know, 'marketing speak' and all... But one has to admit, there's a -huge- discrepency between 35 MB/s and 200 KB/s. -.- ), that's a -slow- drive we have. So, I was wondering. Has anyone else had experience with this particular drive model before? Are they all this slow, or did we just get 'lucky' here...? (Before it's asked, no, the SCSI controller is not throttled. While it's tweaked down on the secondary SCSI chain (external DDS-3 changer), the primary has not had any limiting done on it.)
Re: Question using amflush
That's what I did to make me believe something was a miss and post to the list. Thanks, James Christoph Scheeder <[EMAIL PROTECTED]> wrote: > Hi, > there is a verry easy way to tell what amflush is doing: > > amstatus > > it shows you which dump is actualy getting flushed, which are waiting to > be flushed, which are already flushed and lots of other info's. > Christoph > > James Marcinek schrieb: > > I initially just straced the parent process (22802 amflush normal) which didn't > > output anything: > > > > Here's the ps -ef again with the trace commands for each PID involved: > > > > ps -ef |grep amanda > > amanda 22803 22802 0 14:01 ?00:00:00 driver normal nodump > > amanda 22804 22803 0 14:01 ?00:00:00 taper normal > > amanda 22805 22804 0 14:01 ?00:00:00 taper normal > > root 27581 27541 0 17:29 pts/000:00:00 su - amanda > > amanda 27582 27581 0 17:29 pts/000:00:00 -bash > > amanda 22802 1 98 14:01 ?05:04:39 amflush normal > > amanda 27972 27582 0 19:10 pts/000:00:00 ps -ef > > amanda 27973 27582 0 19:10 pts/000:00:00 grep amanda > > -bash-2.05b$ strace -p 22803 > > read(0, > > > > strace -p 22804 > > read(0, > > > > -bash-2.05b$ strace -p 22805 > > read(3, > > > > -bash-2.05b$ strace -p 22802 > > > > No output for this... > > > > I'm not sure what to expect for my results to be honest. If this isn't normal > > then I guess I should kill it. Then I need to know what the Root Cause is so I > > can fix it. > > > > On another matter, could of I just deleted these directories if I didn't want to > > flush them or would that cause problems? > > > > Thanks, > > > > James > > > > Paul Bijnens <[EMAIL PROTECTED]> wrote: > > > >>James Marcinek wrote: > >> > >>>I've recently deployed amanda. The client forgot tapes on several occasions > > > > and > > > >>>I've got 4 backups in my holding area. I initiated the amflush command and > >>>followed the instructions. The job kicked off in the background and I've > > > > been > > > >>>using: > >>> > >>>ps -ef |grep amanda > >>> > >>>to see if the process is still running, which it is. When I do a top command > >>>it's using lots of CPU time. > >> > >>Which process is taking CPU time? planner? driver? taper? > >> > >> > >>>It's been runninng for several hours now and my logs haven't been populating > >>>since it started. Here's the last few entries: > >>> > >>>START amflush date 20041207 > >>>START driver date 20041207 > >>>START taper datestamp 20041207 label Normal18 tape 0 > >>> > >>>I'm a bit confused because I now see a folder 20041207 in my /var/holding. > > > > It's > > > >>>empty, which is good if it's working properly. > >> > >>For flush, that's normal. > >> > >> > >>>Why isn't anything being populated too(amflush and log file)? Is there any > > > > way > > > >>>to tell if it's running properly? > >> > >>On linux:strace -p The-PID > >>on Solaris: truss -p The-PID > >> > >>"lsof -o the-PID" tells you which files are opened, and sometimes can > >>give a hint what it is doing (e.g. which file it is reading/writing). > >> > >>(hit Ctrl-C to stop it). > >> > >>PS. have also a look at "autoflush on": when forgetting a tape once, > >> the next time, amanda flushes automatically. > >> > > > > > >
