Date: Wed, 07 Aug 2019 13:02:23 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Enji Cooper <yaneurabeya@gmail.com> Cc: "O. Hartmann" <ohartmann@walstatt.org>, freebsd-current <freebsd-current@freebsd.org>, mckusick@mckusick.com Subject: Re: CURRENT: supeblock hash failure - CURRENT wrecking disks Message-ID: <42457.1565182943@critter.freebsd.dk> In-Reply-To: <39FB31E6-A8EC-484C-B297-39C19A787E44@gmail.com> References: <20190807103725.3d06ceca@freyja> <39FB31E6-A8EC-484C-B297-39C19A787E44@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <39FB31E6-A8EC-484C-B297-39C19A787E44@gmail.com>, Enji Cooper w= rites : There is an "interesting" failure-mechanism when you move a disk between 13/current and older systems which do not support ufs-hashes. It will be prudent to make 11 and 12 clear the "use hashes" flags in the superblocks of all filesystems they mount R/W, to limit the amount havoc this will cause when people start playing with 13. -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42457.1565182943>