> On 15. Sep 2020, at 18.54, Jose Soares <josefdsrsoa...@gmail.com> wrote:
> 
> Thank you, Stuart.
> 
> I am facing this when issuing the dump command of a "large" file system
> (2.7TB).
> dump command has finished successfully for the other smaller file systems.
> 
> # df -h
> Filesystem     Size    Used   Avail Capacity  Mounted on
> /dev/wd0a      2.0G    237M    1.6G    12%    /
> /dev/sd0d     10.8T    2.7T    7.6T    26%    /home
> /dev/wd0d      3.9G    146K    3.7G     0%    /tmp
> /dev/wd0f      3.9G    956M    2.8G    25%    /usr
> /dev/wd0g      2.0G    253M    1.6G    13%    /usr/X11R6
> /dev/wd0h      5.9G   15.6M    5.6G     0%    /usr/local
> /dev/wd0j      3.1G    2.0K    3.0G     0%    /usr/obj
> /dev/wd0i      2.0G    2.0K    1.9G     0%    /usr/src
> /dev/wd0e      5.9G    106M    5.5G     2%    /var
> 
> The only contribution I was able to find via Google was
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244470 where a similar
> problem was being reported also regarding a dump of a large file system,
> but for FreeBSD.
> 
> Any suggestion to get the dump working or to better understand what is
> happening?

Segfault on dump, tape.c line 335 spcl.c_addr[I], it overflows.

A workaround is to raise TP_BSIZE from 1024 to
something bigger (maybe 8192?) in /usr/include/protocols/dumprestore.h
and recompile dump. Not a proper fix!

(Also happened to me maybe a week ago, recent -current,
indeed the filesystem was big (2 terabytes)).

Reply via email to