> -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of > Dustin J. Mitchell > Sent: Tuesday, May 11, 2010 10:31 AM > To: Dustin C. Hatch > Cc: [email protected] > Subject: Re: taper segfault (BUG: Bad page map in process taper) > > On Tue, May 11, 2010 at 4:08 AM, Dustin C. Hatch > <[email protected]> wrote: > > [2373787.012572] BUG: Bad page map in process taper pte:480810000b > pmd:261970067 > > Well, clearly there's a kernel bug here. But that's coming *after* > the taper says it's out of tapes. >
Okay, interesting. I guess I thought the segfault was what was causing it to think was out of tapes. > Please check the taper debug log to see what it says. Note that the > taper considers any error from the tape drive to indicate end of tape, > since there is no well-defined error code to expect. So if it's > getting EIO due to a kernel bug, bad SCSI connections, bad tape drive, > or bad tape, it will consider that an end-of-tape. > Here is the excerpt from the taper log; it shows exactly what you describe: 1273566451.676648: taper: warning: Got EIO on /dev/nst0, assuming end of tape 1273566451.676701: taper: Device /dev/nst0 error = 'No space left on device' 1273566451.676769: taper: Device /dev/nst0 setting status flag(s): DEVICE_STATUS_VOLUME_ERROR 1273566452.268931: taper: device /dev/nst0 ran out of space 1273566462.562534: taper: putresult: 4 PARTIAL > Can you write a significant quantity of data to the tapes using dd? Yes, I was actually able to take the dumps in the holding directory and put them onto the tape manually with dd without error. I update to Kernel version 2.6.32-r7 last night. I was able to do a full backup to tape earlier today, using tapes that I know failed before. I guess there could have been a driver problem in 2.6.31. I'll try a larger DLE later and see how it goes. Thanks for your tips Dustin C. Hatch Director of Information Systems Supertechs 13153 State Line Rd. Kansas City, MO 64145 (816) 559-3620 http://www.gosupertechs.com/
smime.p7s
Description: S/MIME cryptographic signature
