mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Andreas Dilger <adilger@clusterfs.com>,
	Andrew Morton <akpm@osdl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Stephen C. Tweedie" <sct@redhat.com>
Subject: Re: ext3 extended attributes refcounting wrong?
Date: Sat, 05 Feb 2005 15:20:00 +0100	[thread overview]
Message-ID: <1107613200.27797.5.camel@winden.suse.de> (raw)
In-Reply-To: <200502051239.j15CdJc8020766@harpo.it.uu.se>

On Sat, 2005-02-05 at 13:39, Mikael Pettersson wrote:
> [...] It does not explain why 2.6 allocated
> the xattr blocks in the first place; as I wrote initially, I
> have disabled the xattrs stuff:
> 
> CONFIG_EXT3_FS=y
> # CONFIG_EXT3_FS_XATTR is not set

The filesystem in question must have been used with a kernel that was
xattr aware once. You could also have been using ext2. Maybe you ran
selinux at some point, or similar. Can you boot into a kernel with
CONFIG_EXT3_FS_XATTR enabled, and ``getfattr -m- -d -R .'' on the
filesystem in question? This gives you a full xattr dump.

Regards,
-- 
Andreas Gruenbacher <agruen@suse.de>
SUSE Labs, SUSE LINUX GMBH


  reply	other threads:[~2005-02-05 14:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-05 12:39 Mikael Pettersson
2005-02-05 14:20 ` Andreas Gruenbacher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-05 19:49 Mikael Pettersson
2005-02-07  9:23 ` Stephen C. Tweedie
2005-02-03 22:42 Mikael Pettersson
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

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=1107613200.27797.5.camel@winden.suse.de \
    --to=agruen@suse.de \
    --cc=adilger@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --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

Powered by JetHome