The AMANDA Patches Page

This page contains a list of important patches to some of the older releases of AMANDA.

Please be aware of the fact that the current release of AMANDA is 2.6.1p2 or higher, so think twice about applying some old patch. We, the AMANDA Core Team, strongly recommend to update to the latest stable release !!!

The links below contain pointers to messages posted to the AMANDA mailing lists. Please read the messages for additional information on the problems they fix and any additional action you must take for the patch to work.

You may use GNU patch in order to apply these patches. It is available at the GNU anonymous FTP site or at any of its mirrors, in a file named patch-release-number.tar.gz.

Most patches are application/x-patch MIME attachments of messages posted to AMANDA mailing lists, and this is the recommended form of posting patches, because such patches can be downloaded directly from the archives (not as of May 23, but eGroups is working to fix the problem). Some have been included in the mail text, so you have to click on the Source button and save the page. With a bit of luck, you'll be able to use the .html file as input for patch, but it may require some tweaking. If you cut and paste a patch file from the browser window, make sure to run patch -l so that the patch program does not get confused because of differences of tabs and spaces.

A -p0 or -p1 switch has become almost mandatory in latest releases of GNU patch; if you don't issue a -p switch, patch may guess incorrectly the file to patch, and you'll get rejected junks for files such as INSTALL and

For applying a patch that contain Index: lines, setting the environment variable POSIXLY_CORRECT before running the patch command may help getting the patch applied without human intervention. Thanks to Evan Champion for pointing this out. A detailed explanation of why this helps can be found in the GNU patch man-page.

Patches for older releases are no longer listed here.

Patches for AMANDA 2.4.5

Patches for AMANDA 2.4.2p2

  • advfs.patch: This corrects a problem with detecting the advfs file system type (e.g. on Irix and Tru64) and picking the right dump program to use. It also cleans up some problems with linux device name determinations. (Posted on Apr 12, 2001)
  • stream_client.patch: This corrects a problem with amrecover reporting "did not get a reserved port" when --with-portrange had been used with ./configure. (Posted on Apr 2, 2002)

Patches for packages used by AMANDA:

  • samba2-largefs.patch: an update of the patch samba-largefs.patch, distributed with AMANDA 2.4.1p1, for Samba up to release 2.0.3. This patch is already installed in the Samba CVS tree, so it will no longer be needed in newer releases of Samba.
  • restore.diff: Samba 2.0.2, and probably 2.0.0 too, have trouble when restoring files whose sizes are exact multiples of 512 bytes, and may have trouble reading from pipes. This patch by Bob Boehmer fixes these problems. Note that tar-files produced before this patch are still usable, as the problems addressed by this patch are in the restore code only. The problem is already fixed in Samba 2.0.3.
  • sambatar.diff: Samba 1.9.18p5 up to 1.9.18p10 will print messages to stdout, even when asked to create a tar-file and write to stdout. Since AMANDA asks SAMBA to create tar-files to stdout, if you do not apply this patch in SAMBA, your backups will be useless. Problem reported by Ronny Blomme. According to Todd Pfaff, this problem is fixed in Samba 2.0.0.
  • samba-gtar.diff: Samba 1.9.18p4 (and probably previous 1.9.18 versions) won't read tar-files with gnutar-style long filenames, even ones produced by itself. Patch by Rob Riggs. Fixed in Samba 1.9.18p5. (Apr 12, 1998)
  • Samba 1.9.17 and higher will print incorrect size information for large (> 2GB) filesystems on hosts whose ints are 32bits. If your C compiler supports `unsigned long long's and printf() supports "%llu" for printing them, you should apply samba-largefs.patch, available in AMANDA distributions since release 2.4.0b5. Anyway, beware large SMB filesystems: some MS-Windows hosts were reported (in Samba mailing lists) to randomly corrupt such filesystems, but then, this has nothing to do with Samba or AMANDA.
  • GNU tar 1.12: there are two known problems (described below) that can be fixed by applying tar-1.12.patch, available in AMANDA distributions since release 2.4.0b5.
    • On SunOS 4.1.3, HP/UX and possibly other systems, GNU tar 1.12 will report incorrect output sizes, because printf does not understand "%llu".
    • GNU tar 1.12 would report Bad file number error messages at estimate-time for sparse files.
  • GNU tar 1.13: even though the second problem in release 1.12 is already fixed in 1.13, the other is only partially fixed. Besides, there are a couple of other problems in release 1.13, related with exclude patterns and restoring, so its use is not recommended. Hopefully, all of these problems will be fixed in GNU tar 1.14. If you want to use something past 1.12, 1.13.25 appears to be stable.
  • GNU tar 1.13.18: This patch fixes two problems in tar-1.13.18:
    • A workaround for a bug in fnmatch from glibc.
    • A bug that can cause a core dump.

This page is maintained by the AMANDA Core Development Team.

Please report changes and/or additions to the AMANDA-hackers mailing list.

Last updated: $Date: 2014/12/12 18:44:43 $