Date: Wed, 5 Dec 2018 10:45:35 -0800 (PST) From: Don Lewis <truckman@FreeBSD.org> To: Kirk McKusick <mckusick@mckusick.com> Cc: freebsd-fs@FreeBSD.org Subject: Re: stuck with ufs CHECK-HASH errors Message-ID: <tkrat.e3d9bb21ca501329@FreeBSD.org> In-Reply-To: <201812050644.wB56iYQQ020650@chez.mckusick.com> References: <tkrat.2f594d1b2546d371@FreeBSD.org> <201812050644.wB56iYQQ020650@chez.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 Dec, Kirk McKusick wrote: >> Date: Mon, 3 Dec 2018 23:08:50 -0800 (PST) >> From: Don Lewis <truckman@FreeBSD.org> >> Subject: Re: stuck with ufs CHECK-HASH errors >> To: Kirk McKusick <mckusick@mckusick.com> >> cc: freebsd-fs@FreeBSD.org >> >> On 3 Dec, Kirk McKusick wrote: >>> I am working on a fix. Hopefully have it in no more than a day. >> >> I figured out that ufs_disk_fillout() and therefore sbread() in libufs >> is never getting called. Therefore the superblock used by cgput() is >> all zeros. If I change the call to ufs_disk_fillout_blank() in setup() >> to ufs_disk_fillout() then things appear to work much better. > > Your above workaround was quite helpful in tracking down the > problem and coming up with an appropriate fix that did not > conflict with the superblock check-hashes. I have checked > in a fix (-r341510). Please confirm that it resolves your > problem. Thanks! It worked on my broken VM.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?tkrat.e3d9bb21ca501329>