Unless I'm mistaken, EXT3 and 4 will always report orphaned inodes after a crash (if they occur). It's just part of the logging like frank mentioned.
However, I do remember instances back when I was using EXT3 that the journal would be replayed after normal cold boots. It was also much slower than EXT4 which made it look scarier than it really is. On Wed, Jul 3, 2019 at 8:28 AM Rich Shepard <rshep...@appl-ecosys.com> wrote: > > 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 > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
