From: Marco Gatti <marco.gatti@gmail.com>
To: reiserfs-devel@vger.kernel.org
Subject: Re: reiserfs + acl corruption
Date: Tue, 6 Apr 2010 15:31:56 +0200 [thread overview]
Message-ID: <y2s54cce25c1004060631l918b128bi32c2739bc68aa271@mail.gmail.com> (raw)
In-Reply-To: <r2r54cce25c1004060240o8f8baf09y5ccb5d7c6791ef53@mail.gmail.com>
Ok, i made some tests and i think i found something really relevant.
I tested in 2 different machines various kernel versions, this is my report:
2.6.26 debian flavoured - no bug
2.6.29.6 - no bug
2.6.30.9 - acl bug present
2.6.31.12 - acl bug present
2.6.32.8, 2.6.32.9, 2.6.32.10 - acl bug present
Then the really interesting thing. If you try my test
mkfsreiserfs /dev/sdc1
mount -o acl /dev/sdc1 /mnt
cd /mnt
mkdir dir_with_many_files
touch dir_with_many_files/{1..100000}
setfacl -R -m u:username:rw dir_with_many_files
setfacl -R -x u:username dir_with_many_files
setfacl -R -b dir_with_many_files
when using the setfacl command keep an eye on the space occupation on
the partition/disc you are testing.
With kernels with bug present when issuing "setfacl -R -x ..." the
used space get reduced like there is no acl at all (or a kind of).
Let's make it clear:
- after creating 300000 empty files in a directory i have 60MB of space used;
- after "setfacl -R -m ..." i have 1.3GB of space used;
- after "setfacl -R -x ..." with bugged kernels i have 153MB of space used;
- after "setfacl -R -x ..." with NO bugged kernels i still have 1.3GB
of space used;
- after "setfacl -R -b ..." with NO bugged kernels i have 119MB of space used.
It seems to me that the changes introduced in kernel version 2.6.30
have modified heavily the behaviour in handling extended attributes,
but i'm not a kernel hacker then i'll leave you looking through the
code!
Hope this helps and if you have some patch (i hope against 2.6.32)
i'll be glad to test it.
Cheers
Marco
prev parent reply other threads:[~2010-04-06 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 15:29 reiserfs + acl corruption Marco Gatti
2010-03-30 8:02 ` Marco Gatti
2010-03-30 18:16 ` Jeff Mahoney
2010-03-31 14:39 ` dimas
2010-04-04 20:38 ` Christian Kujau
2010-04-05 1:11 ` Christian Kujau
2010-04-05 5:44 ` Christian Kujau
2010-04-05 15:34 ` Jeff Mahoney
2010-04-06 8:40 ` Christian Kujau
2010-04-06 9:40 ` Marco Gatti
2010-04-06 13:31 ` Marco Gatti [this message]
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=y2s54cce25c1004060631l918b128bi32c2739bc68aa271@mail.gmail.com \
--to=marco.gatti@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.