Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 29 Jan 2020 16:32:29 +0100
From:   Herbert Poetzl <herbert@13thfloor.at>
To:     linux-ext4@vger.kernel.org
Subject: comm setfattr: corrupted xattr entries on 'clean' filesystem
Message-ID: <20200129153229.GB29184@MAIL.13thfloor.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
Sender: linux-ext4-owner@vger.kernel.org
Precedence: bulk


Not sure this is the best place for this, but it was
suggest on #linuxfs to report the problem here ...

I have an (older) ext3 filesystem where 'some' files
are unable to accept any extended attributes (xattrs).

 # setfattr -n user.x -v y some-file

... results in ...

 setfattr: some-file: Structure needs cleaning

... and the kernel reports ...

kernel: EXT4-fs error (device md2): ext4_xattr_set_entry:1607: inode #2084096: comm setfattr: corrupted xattr entries

... kernel is not the latest (4.19.84), but e2fsck is ...

e2fsck 1.45.5 (07-Jan-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/md2: 6594874/9538640 files (2.7% non-contiguous), 3887814750/3907018432 blocks

Any suggestions how to 'clean my structures' would
be appreciated!

Thanks in advance,
Herbert