[Bug 203588] [ufs] fsck_ufs segfaults during journals after powerloss

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203588

amvandemore at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amvandemore at gmail.com

--- Comment #1 from amvandemore at gmail.com ---
Yes this is a bug.  Unfortunately, this type of PR is almost useless since
there is no actionable information included.  I don't know any devs who love
wild goose chases.

If it happens again, better ways to handle this are:

1.  Snapshot the underlying block device so there is always access to the
problematic state.
2.  Run "fsck_ffs -d" and "fsck_ffs -f -d" and ensure the output is saved eg
script(1).

See bug #187221 for an example of an actionable PR.

Also what does this "A full fsck hopefully worked .." mean?  Did a full fsck
work?  If yes then there is no need to mention it and if no it needs to be in
the PR.

-- 
You are receiving this mail because:
You are the assignee for the bug.