From: Subodh Nijsure <snijsure@grid-net.com>
To: <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubifs_jnl_update and extended attribute inode removal
Date: Thu, 10 May 2012 16:22:49 -0700 [thread overview]
Message-ID: <4FAC4DC9.2050901@grid-net.com> (raw)
In-Reply-To: <1336624262.1936.27.camel@brekeke>
On 05/09/2012 09:31 PM, Artem Bityutskiy wrote:
> On Wed, 2012-05-09 at 20:19 -0700, Subodh Nijsure wrote:
>> Easy way to describe this is: I create 100 files, assign then extended
>> attribute, and remember what the xattr was, it always stays the same.
>> However now if I delete some of these files randomly some of the files
>> end up having wrong xattr.
> I guess this happens only when you do a power cut? I need to look
> closer, but quick feed-back is that there is probably a bug in the
> journal reply - when we see a deleted inode in the journal - we remove
> it from TNC, and we probably forget to look-up for all its xattrs?
> Really need to look closer.
>
> Would you prepare a description how I could reproduce this?
I re-submitted patches for integck and as well as v3 of extended
attribute patch set that I have been holding on to.
You can just run integck -p -n 2 <dir-name> and that should reproduce
the issue i.e. integck will fail.
If email thread gets too long I could get on the OFTC #mtd irc chat at
time that works best, to get some guidance.
/Subodh
next prev parent reply other threads:[~2012-05-10 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 3:19 ubifs_jnl_update and extended attribute inode removal Subodh Nijsure
2012-05-10 4:31 ` Artem Bityutskiy
2012-05-10 23:22 ` Subodh Nijsure [this message]
2012-06-05 12:07 ` Artem Bityutskiy
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=4FAC4DC9.2050901@grid-net.com \
--to=snijsure@grid-net.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.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.