On Thu, Jun 06, 2002 at 10:37:12AM +1000, Bruce Evans wrote:
> On Wed, 5 Jun 2002, Brooks Davis wrote:
> > For the last week or so I've had my laptop panic every time amanda did
> > a dump of it.  This happens with a kernel as of yesterday so it probably
> > wasn't just a bad update.
> This is caused by:
> (1) amanda attempting to read from a bad offset on the device.  Almost
>     any offset that causes a block number of >= 2GB or 4GB will trigger
>     the kernel bug.
> (2) the bounds checking in dscheck() being 64-bit daddr_t casualty
>     (*blush*).

This fixes the panic.  It appears there's also another bug in dump
though.  When I run dump I get this:

[10:15pm] brooks@minya (~): sudo dump -a -f /dev/null /var
  DUMP: Date of this level 0 dump: Wed Jun  5 22:16:09 2002
  DUMP: Date of last level 0 dump: the epoch
  DUMP: Dumping /dev/ad0s2e (/var) to /dev/null
  DUMP: mapping (Pass I) [regular files]
  DUMP: mapping (Pass II) [directories]
  DUMP: estimated 580085 tape blocks.
  DUMP: dumping (Pass III) [directories]
  DUMP: dumping (Pass IV) [regular files]
  DUMP: master/slave protocol botched.
  DUMP: The ENTIRE dump is aborted.

Any idea what this problem is?

-- Brooks

Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

Attachment: msg39238/pgp00000.pgp
Description: PGP signature

Reply via email to