On Thu, 25 Jul 2002, Gene Heskett wrote: > On Thursday 25 July 2002 15:40, Keith Nasman wrote: > >[root@presto DailySet1]# su amanda -c "amlabel DailySet1 > > DailySet113" rewinding, reading label, reading label: Cannot > > allocate memory rewinding, writing label DailySet113, checking > > label, done. > > > >I assume that the tape got labeled correctly. Can anyone enlighten > > me on the memory error? > > Hummm, not brand new tapes? Maybe a tape that was used with another > backup util, probably proprietary? > These are not brand new tapes. Leftovers from ArcServe for NT.
> What it sounds like is that when amanda tried to read the initial > header from the tape, its encountering a totally humungous value > the tapes block size and can't allocate that much memory. > > My best guess... > > Anyway, dd can retrieve the tape label with this pair of commands: > #>mt -f /dev/tape_device rewind > #>dd if = /dev/tape_device count = 1 > which should disgorge the first block of 512 bytes to the screen, > showing you the label as written. > > Hmmm, this is what I get. [root@presto amanda]# mt -f /dev/nst0 rewind [root@presto amanda]# dd if=/dev/nst0 count=1 dd: reading `/dev/nst0': Cannot allocate memory 0+0 records in 0+0 records out yet, I get this output from amcheck [root@presto amanda]# su amanda -c "amcheck DailySet1" Amanda Tape Server Host Check ----------------------------- Holding disk /var/tmp: 127389 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape DailySet114 label ok so it looks like the tape label is fine. <shrug> Keith
