Re: TAPE-ERROR 00-00001 [writing file: File too large]
On Thu, 26 Apr 2007, Jon LaBadie wrote: On Thu, Apr 26, 2007 at 08:52:24PM +0400, Igor V. Ruzanov wrote: Hello! I run Amanda under FreeBSD-4.11, so when Amanda trying to make file of dump with size of more than 4GB (exactly, 2**32-1), i can see in log/amdump.* the following messages: taper: writing end marker. [Sunday2 ERR kb 4194272 fm 1] driver: state time 2560.825 free kps: 3 space: 81451306 taper: writing idle-dumpers: 1 qlen tapeq: 0 runq: 0 roomq: 0 wakeup: 0 driver-idle: not-idle driver: interface-state time 2560.825 if default: free 1 if local: free 1 if lnc0: free 1 driver: hdisk-state time 2560.825 hdisk 0: free 81451306 dumpers 0 driver: result time 2560.825 from taper: TAPE-ERROR 00-1 [writing file: File too large] That is due to filesystems constraints in FreeBSD-4.x where a size of file is given in 32-bit representation and declared in sys/stat.h with int32_t integer type. Is there passible to change some code of Amanda to do the dumps into more than 4GB files under FreeBSD-4.x? (for example, with deal of stdout) Where in the Amanda code the conditions are checking for the maximum length of writing file? Are you taping to virtual tapes on hard disk? If so, and your version of amanda is recent, us the tape splitting feature that writes in chunks than can, but don't have to, span several tapes. If using a holding disk, use the chunk size feature to limit the maximum size of a file on holding disk. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax) Yes, i'm taping to hard disk (tapedev=file:/). Actually the problem arises when the dump itself is finished and all chunks (in my config chunksize = 256MB) are beginning to be sent from holding disk to file in storage directory. And when this file reaches 4GB Amanda dropping errors such as [writing file: File too large] into log. Mayby there are some ways to solve the problem of under FreeBSD-4.x system? I have Amanda of version 2.5.1p3. +---+ ! CANMOS ISP Network! +---+ ! Best regards ! ! Igor V. Ruzanov, network operational staff! ! e-Mail: [EMAIL PROTECTED] ! +---+
Re: TAPE-ERROR 00-00001 [writing file: File too large]
On Fri, Apr 27, 2007 at 11:33:59AM +0400, Igor V. Ruzanov wrote: On Thu, 26 Apr 2007, Jon LaBadie wrote: On Thu, Apr 26, 2007 at 08:52:24PM +0400, Igor V. Ruzanov wrote: Hello! I run Amanda under FreeBSD-4.11, so when Amanda trying to make file of dump with size of more than 4GB (exactly, 2**32-1), i can see in log/amdump.* the following messages: ... That is due to filesystems constraints in FreeBSD-4.x where a size of file is given in 32-bit representation and declared in sys/stat.h with int32_t integer type. Is there passible to change some code of Amanda to do the dumps into more than 4GB files under FreeBSD-4.x? (for example, with deal of stdout) Where in the Amanda code the conditions are checking for the maximum length of writing file? Are you taping to virtual tapes on hard disk? If so, and your version of amanda is recent, us the tape splitting feature that writes in chunks than can, but don't have to, span several tapes. Yes, i'm taping to hard disk (tapedev=file:/). Actually the problem arises when the dump itself is finished and all chunks (in my config chunksize = 256MB) are beginning to be sent from holding disk to file in storage directory. And when this file reaches 4GB Amanda dropping errors such as [writing file: File too large] into log. Mayby there are some ways to solve the problem of under FreeBSD-4.x system? I have Amanda of version 2.5.1p3. As I suggested, look into the tape splitting/spanning features of amanda.conf. These can be used to limit the size of the on tape files. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
amrestore help
I am trying to restore a folder from a tape in a previous cycle (last night had a level 0 of the disk, but the folder was deleted prior). I have a tape changer and read that amrestore doesnt work with tape changers. My dumptypes are gnutar, so I probably can't use amrecover. Is this correct? When I tried to run it, it said amrecover: Unexpected end of file, check amindexd*debug on server localhost. I've looked all over and can't seem to find what I need (possibly because I've never recovered before and don't know what to look for). Steve
Re: amrestore help
actually, i found how to put the desired tape into the active slot of the changer. But when i do amrestore /dev/nst0 lollipop /files1 I get this: amrestore: missing file header block amrestore: 2: skipping zoo._.20070419.1.1 amrestore: missing file header block amrestore: 6: skipping marlin._var.20070419.1.1 amrestore: 10: reached end of information What now? Steven Settlemyre wrote: I am trying to restore a folder from a tape in a previous cycle (last night had a level 0 of the disk, but the folder was deleted prior). I have a tape changer and read that amrestore doesnt work with tape changers. My dumptypes are gnutar, so I probably can't use amrecover. Is this correct? When I tried to run it, it said amrecover: Unexpected end of file, check amindexd*debug on server localhost. I've looked all over and can't seem to find what I need (possibly because I've never recovered before and don't know what to look for). Steve
