Date: Sat, 8 Jul 2017 11:13:27 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net> To: Michael Butler <imb@protected-networks.net> Cc: Peter Jeremy <peter@rulingia.com>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: dump trying to access incorrect block numbers? Message-ID: <201707081813.v68IDR7Y068636@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <db504937-a091-f01e-5b8e-19ceebd3eab9@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 07/08/17 12:28, Rodney W. Grimes wrote: > > > Since it has been speculated that this is occuring during the > > creation of the snapshot, could you try just creating a snapshot > > using mksnap_ffs and see if any errors occur? > > After a short pause with disk activity, the same sorts of errors are > logged when using "mksnap_ffs /.snap2" where .snap2 did not previously > exist, Ok, so this simplifies what needs to be looked at, this is no longer a dump(8) issue, but now a snapshot ufs issue. This should be much easier for more people to try out. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201707081813.v68IDR7Y068636>