mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@user.it.uu.se>
To: sct@redhat.com, akpm@osdl.org, adilger@clusterfs.com
Cc: linux-kernel@vger.kernel.org
Subject: ext3 extended attributes refcounting wrong?
Date: Thu, 3 Feb 2005 23:42:27 +0100	[thread overview]
Message-ID: <16898.43219.133783.439910@alkaid.it.uu.se> (raw)

I believe there is some accounting error in the ext3 code
for the case when CONFIG_EXT3_FS_XATTR is not selected.

Whenever any one of my development boxes triggers an fsck
at boot because some file system, usually /, has been mounted
sufficiently many times, an inconsistency error occurs:

Extended attribute block N has reference count M, should be M'.

where M' is much less than M. As I drop into single-user and
run fsck, it finds at lot occurrences of this error, followed by:

Block bitmap differences ...

and then:

Free blocks count wrong

(always too low, i.e. I have more free blocks than the fs records).

This occurs on all my boxes, with different CPUs (x86/x86-64/ppc)
and different chipsets (Intel, Promise, VIA, Apple), and basically
the only commonalities are:
- they dual boot the most recent 2.4 and 2.6 kernels, and I switch often
- all file systems are ext3
- all XATTR stuff is disabled

/Mikael

             reply	other threads:[~2005-02-03 22:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03 22:42 Mikael Pettersson [this message]
2005-02-03 23:36 ` Stephen C. Tweedie
2005-02-04  8:25   ` Mikael Pettersson
2005-02-04 10:40     ` Stephen C. Tweedie
2005-02-04 13:10       ` Mikael Pettersson
2005-02-04 13:56         ` Stephen C. Tweedie
2005-02-04 14:15           ` Mikael Pettersson
2005-02-04 16:19             ` Andreas Gruenbacher
2005-02-05 12:39 Mikael Pettersson
2005-02-05 14:20 ` Andreas Gruenbacher
2005-02-05 19:49 Mikael Pettersson
2005-02-07  9:23 ` Stephen C. Tweedie

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=16898.43219.133783.439910@alkaid.it.uu.se \
    --to=mikpe@user.it.uu.se \
    --cc=adilger@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®