On Wed, 3 Jul 2019, Frank Filz wrote: > Other than a crash or a code bug, I can't think of any reason. Frank, Me, neither. > e2fsck does the journal replay after a crash, so it's reporting orphaned > inodes may just be part of journal replay. Yes, and this is why I asked the question. Thanks much, Rich