Re: fsck: too many inodes

[Brett Lymn <blymn%internode.on.net@localhost>]

On Wed, Jun 19, 2019 at 07:46:50AM +0200, Emmanuel Dreyfus wrote:
> Hello
> 
> After an unexpected reboot, a FFSv2 filesystem had trouble replaying its
> log. It took infinite time, ddb showed mount stuck in biolobk, and I had
> to interrupt it. 
> 
> After that event the filesystem now mounts read/write without a hitch,
> and fsck thinks it is clean. However, running fsck -f brings this:
> 
> ** /dev/rdk0
> ** File system is already clean
> ** Last Mounted on /home
> ** Phase 1 - Check Blocks and Sizes
> too many inodes 18446744073709551615
> 
> Any advice better than restoring backups?
> 

Try an alternate superblock?  Use scan_ffs -b to find superblocks and
use an alternate with fsck_ffs.

-- 
Brett Lymn
--
Sent from my NetBSD device.

"We are were wolves",
"You mean werewolves?",
"No we were wolves, now we are something else entirely",
"Oh"