fsck errors on a running system that disappear in single-user mode

[Dan Nelson]

In the last episode (Mar 11), Anthony Atkielski said:
> I ran fsck on a running system (check only, no changes), and it turned
> up some inconsistencies.  So I rebooted into single-user mode and ran it
> again, but then everything checked out fine.  I presume this is because
> fsck is looking at filesystems that are changing right in front of its
> eyes on a running system, which leads to inconsistencies that really
> don't mean anything ... right?

Correct.

-- 
	Dan Nelson
	dnelson at allantgroup.com