On Wed, 5 Jun 2002, Brooks Davis wrote:
> 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?
I guess this is another 64-bit daddr_t problem. At least
`daddr_t idblk[MAXNINDIR]' in traverse.c seems to be broken. This seems
to be fixed in the ufs2 patch.
There as another report about this earlier today, in a PR IIRC.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message