Date: Mon, 11 Jun 2018 12:52:26 -0700 (PDT) From: "Rodney W. Grimes" <freebsd@pdx.rh.CN85.dnsmgr.net> To: Warner Losh <imp@freebsd.org> Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r334970 - head Message-ID: <201806111952.w5BJqQNU029751@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201806111932.w5BJWfCd045993@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[ Charset UTF-8 unsupported, converting... ] > Author: imp > Date: Mon Jun 11 19:32:40 2018 > New Revision: 334970 > URL: https://svnweb.freebsd.org/changeset/base/334970 > > Log: > Document the dump issue in UPDATING so people understand when they > get a new diagnostic. > > Modified: > head/UPDATING > > Modified: head/UPDATING > ============================================================================== > --- head/UPDATING Mon Jun 11 19:32:36 2018 (r334969) > +++ head/UPDATING Mon Jun 11 19:32:40 2018 (r334970) > @@ -32,6 +32,13 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW: > "ln -s 'abort:false,junk:false' /etc/malloc.conf".) > > > +20180611: > + A bug in dump has been found where it can incorrectly dump filesystems > + with more than 512k inodes and produce corrupted dump images. r334968 > + closes the door by not dumping filesystems with more than 512k inodes. > + While older dumps may 'work' the image they produce may or may not be > + readable depending on many factors. > + Does it make since to put a temporary warning in newfs to warn users of the "may bot be able to dump this fs" issue? Regards, -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201806111952.w5BJqQNU029751>