what's the next step I'd make if any ?
- If this was a "preen" (-p) filesystem recovery, performed by rc(8) on boot, only a limited set of inconsistencies are recovered -- see fsck_ffs(8).
- If this is after a standard filesystem check (without -p) performed manually, you'll have to read the output to find out why the error is not recoverable. Note that answering "n" to any question will prevent recovery of an inconsistency, and answering "y" to any prompt during fsck could cause data loss.
Assuming #2, above, you will need to understand the particular inconsistencies reported that require a yes/no decision, and
whether or not possible data loss is acceptable for the affected file, or if the effected entity is a directory, for the directory and all of the files in its hierarchy.
If data loss is acceptable, you may use "y"; if unacceptable, you should determine if you can manually retrieve the data when the filesystem is mounted read-only, or if recovery from backup is acceptable, prior to answering "y".
administrator might be able to effect a repair or recovery using fsdb(8); however, best practice recommends doing so only after making a filesystem backup of the damaged filesystem with dd(1) prior to using that tool.