From: Jeff Mahoney <jeffm@suse.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Marco Gatti <marco.gatti@gmail.com>, reiserfs-devel@vger.kernel.org
Subject: Re: reiserfs + acl corruption
Date: Mon, 05 Apr 2010 11:34:43 -0400 [thread overview]
Message-ID: <4BBA0313.4020405@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.01.1004042240500.29272@bogon.housecafe.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 04/05/2010 01:44 AM, Christian Kujau wrote:
> On Sun, 4 Apr 2010 at 18:11, Christian Kujau wrote:
>> Got it. After a few more iterations of the testscript[0] I was hitting it
>> at 25601 files, 25600 file were fine. Again, setting and removing *one*
>> ACL is fine, but removing *all* ACLs lead to I/O error.
>
> The 25601 files don't need to be in one single directory. With 25000 files in
> one and 25000 files in another (sub-)directory, the same happens. Enabling
> REISERFS_CHECK hasn't revealed any more information yet.
Ok. I'm able to reproduce this with your script. I _can't_ reproduce it
with 8 GB of memory, but I can reproduce it with mem=256m. That's a good
data point.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAku6AxMACgkQLPWxlyuTD7K5HwCfQrKlzFoLu93sfVPAolDVPsvI
gsoAmwdMU9sT4fWIlrWw+RMnFuHJDk8U
=pJCj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-04-05 15:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-28 15:29 reiserfs + acl corruption 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 [this message]
2010-04-06 8:40 ` Christian Kujau
2010-04-06 9:40 ` Marco Gatti
2010-04-06 13:31 ` Marco Gatti
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=4BBA0313.4020405@suse.com \
--to=jeffm@suse.com \
--cc=lists@nerdbynature.de \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).