From: Edward Shishkin <edward.shishkin@gmail.com>
To: ReiserFS development mailing list <reiserfs-devel@vger.kernel.org>
Subject: Re: reiser4 for 3.12
Date: Sat, 07 Dec 2013 20:38:17 +0100 [thread overview]
Message-ID: <52A37929.8020304@gmail.com> (raw)
07.12.2013 17:59, Mathieu Belanger пишет:
> I have updated my git tree for kernel 3.12.
Thanks!
>
> No change for reiser4 since 3.12-rc2.
>
> Change since 3.11 :
> - Shrinker API change
> - Patch from Edward for enerasable directory (I think)
The problem still exists. It is not always reproducible though..
Sometimes when deleting a file the process can not find the
record about this file in the directory item. As the result, the
size of directory is not updated and it becomes undeletable.
I don't have any ideas, if this is an old bug, or some implicit
regression. People started to complain from 3.10, however
I didn't change reiser4 code when porting to 3.10.
After running fsck --fix the directory becomes removable again.
Also you can rename undeletable directories, so that they won't
annoy you (to not run fsck every time).
Edward.
>
> Note, I did not test it with 3.12 final yet. I still have a busy day
so have fun!
>
> Shrinker API change can be viewed here :
https://github.com/DestroyFX/reiser4/commits/reiser4-for-3.12-rc2
> Current kernel 3.12 git :
https://github.com/DestroyFX/reiser4/commits/reiser4-for-3.12
> Patch Here : http://mirror.nxtoo.org/reiser4-for-3.12.patch.bz2
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2013-12-07 19:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-07 19:38 Edward Shishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-07 16:59 reiser4 for 3.12 Mathieu Belanger
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=52A37929.8020304@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=reiserfs-devel@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.