CURRENT: supeblock hash failure - CURRENT wrecking disks
O. Hartmann
ohartmann at walstatt.org
Wed Aug 7 15:53:13 UTC 2019
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Am Wed, 07 Aug 2019 13:02:23 +0000
"Poul-Henning Kamp" <phk at phk.freebsd.dk> schrieb:
> --------
> In message <39FB31E6-A8EC-484C-B297-39C19A787E44 at gmail.com>, Enji Cooper writes
> :
>
> 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.
>
The box in question has been setup 6 weeks ago with FreeBSD 13-CURRENT natively. It is now a
wreck. Other systems running CURRENT (as of the most recent revision as of today) were
partially installed as 12-STABLE/12-CURRENT and "moved on" to what is now 13-CURRENT. They do
not(!) indicate such problems reported.
Either I hit the crap installing a new system whilst there was a problem, or something really
strange happened.
The bad thing is that kernel.old exits/dies with an exception and /boot/kernel/ seems to be
completely corrupted. Tomorrow I try to install a prepared pkg tar arcive FreeBSD-kernel from
aCURRENT pkg base and hope this will fix the issue.
Regards,
oh
- --
O. Hartmann
Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQSy8IBxAPDkqVBaTJ44N1ZZPba5RwUCXUrtzQAKCRA4N1ZZPba5
R4EpAPoC9Bk4l9aJXDsLF1mbZYxEqOxe8MknYx0ErVzaWDtHlQD9EogA6Xk71LEF
cxtLCo/HgEIdPaJtIOPiWh9dAg9t2wg=
=gLEF
-----END PGP SIGNATURE-----
More information about the freebsd-current
mailing list