All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Chris Hunter <chris.hunter@yale.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: e2fsck discrepancy with debugfs stat ?
Date: Fri, 11 Sep 2015 22:09:12 -0400	[thread overview]
Message-ID: <20150912020912.GA3917@thunk.org> (raw)
In-Reply-To: <55F332B6.3010107@yale.edu>

On Fri, Sep 11, 2015 at 03:59:50PM -0400, Chris Hunter wrote:
> Hi Theodore, Thanks for the reply.
> 
> Most of the e2fsck errors appear to have been uncommitted journal
> transactions. After stopping filesystem activity (hopefully to clear
> journal) a second dry-run e2fsck produced a much shorter list of errors.

Oh, if you trying to run e2fsck on a mounted file system ---- don't do
that.  The results will be very confusing.

> FYI, There was an entry "Links: 1  Blockcount: 8" reported by debugfs "stat"
> command is that same as i_links_count field ?

Yes.

						- Ted

      reply	other threads:[~2015-09-12  2:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-11  3:03 e2fsck discrepancy with debugfs stat ? Chris Hunter
2015-09-11 12:39 ` Chris Hunter
2015-09-11 17:55 ` Theodore Ts'o
2015-09-11 19:59   ` Chris Hunter
2015-09-12  2:09     ` Theodore Ts'o [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150912020912.GA3917@thunk.org \
    --to=tytso@mit.edu \
    --cc=chris.hunter@yale.edu \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.