From owner-freebsd-hackers  Wed Jun 21 13:50:55 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA25259
          for hackers-outgoing; Wed, 21 Jun 1995 13:50:55 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA25113
          ; Wed, 21 Jun 1995 13:50:40 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA00811; Thu, 22 Jun 1995 06:06:46 +1000
Date: Thu, 22 Jun 1995 06:06:46 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199506212006.GAA00811@godzilla.zeta.org.au>
To: bde@freefall.cdrom.com, hsu@freefall.cdrom.com
Subject: Re: dump errors
Cc: hackers@freefall.cdrom.com
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>Could this be a slice compatibility problem?  These are old 1.1 filesystems
>that are giving me trouble, and, I just dumped it successfully w/o errors
>from FreeBSD 1.1.5.1.

If the partitions are partly outside the slice, then chopping them would
cause read errors.  Any chopping of partitions is reported when the slice
is first-opened.

PR 461 reports and fixes bogus checking of lseek() for offsets >= 2G
but I don't see how this problem can affect read().

Bruce