From: Arjan Filius <iafilius@xs4all.nl>
To: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
<mason@suse.com>
Subject: Re: reiserfs: still problems with tail conversion
Date: Sat, 24 Feb 2001 16:45:04 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.30.0102241613140.1185-100000@sjoerd.sjoerdnet> (raw)
In-Reply-To: <20010223221856.A24959@arthur.ubicom.tudelft.nl>
Hello,
I tried Erik's trigger-program.
After some test i thing it's memory related, and it seems to match the
other reports i saw on lkm.
With my 384M ram i was not able te reproduce it.
With "mem=32M" linux hang while starting a test oracle-db.
However i tried (not repeated tests, and after a fresh reboot):
ram=128M ; Triggered
ram=138M ; Triggered
ram=180M ; Triggered
ram=192M ; NOT Triggered
ram=250M ; NOT Triggered
ram=256M ; NOT Triggered
These results say that it memory dependent, and perhaps memory use
dependent.
With the mem=180M i did some additional tests:
reisertest ; triggered
free ; shows only 60M on cached data and 8192 files*8192
bytes=64M
/sbin/swapout 100M ; make sure enough cache to hold 64M data
reisertest ; NOT Triggered !!!!
While leaving the data, and executing reisertest in a new dir i'm
triggring it again!
So i think i can say, it's triggerable when the cache has no space to hold
all the data (64M), but i didn't extensive tests.
Running suse7.0+updates
kernel 2.4.2
Greatings,
On Fri, 23 Feb 2001, Erik Mouw wrote:
> Hi all,
>
> I am running linux-2.4.2-pre4 with Chris Mason's tailconversion bug fix
> applied, but I still have problems with null bytes in files. I wrote a
> little test program that clearly shows the problem:
>
>
> /* reisertest.c: test for tailconversion bug in reiserfs
> *
> * Compile with: gcc -O2 -o reisertest reisertest.c
> */
> #include <stdio.h>
> #include <sys/types.h>
> #include <sys/stat.h>
> #include <fcntl.h>
> #include <unistd.h>
>
> #define MAXBYTES 8192
>
> int main(int argc, char *argv[])
> {
> int fd;
> int i;
> char name[32];
> char buf[MAXBYTES];
> char check[MAXBYTES];
>
> memset(buf, 0x55, MAXBYTES);
>
> fprintf(stderr, "Creating %d files ... ", MAXBYTES);
>
> for(i = 0; i < MAXBYTES; i++) {
> sprintf(name, "reiser-%05d.test", i);
> fd = open(name, O_WRONLY | O_CREAT, 0644);
> write(fd, buf, i);
> close(fd);
> }
>
> fprintf(stderr, "done\n");
> fprintf(stderr, "Appending to the files ... ");
>
> for(i = 0; i < MAXBYTES; i++) {
> sprintf(name, "reiser-%05d.test", i);
> fd = open(name, O_WRONLY | O_APPEND);
> write(fd, buf, MAXBYTES - i);
> close(fd);
> }
>
> fprintf(stderr, "done\n");
> fprintf(stderr, "Checking files for null bytes ...\n");
>
> for(i = 0; i < MAXBYTES; i++) {
> sprintf(name, "reiser-%05d.test", i);
> fd = open(name, O_RDONLY);
> read(fd, check, MAXBYTES);
> if(memcmp(buf, check, MAXBYTES) != 0)
> fprintf(stderr, " %s contains null bytes\n", name);
> }
>
> fprintf(stderr, "Checking done\n");
>
> return 0;
> }
>
>
> When I run this on a reiserfs partition, I get output like this:
>
>
> erik@arthur:~/reisertest/foo> ../reisertest
> Creating 8192 files ... done
> Appending to the files ... done
> Checking files for null bytes ...
> reiser-00193.test contains null bytes
> reiser-00220.test contains null bytes
> reiser-00256.test contains null bytes
> reiser-00289.test contains null bytes
> reiser-00329.test contains null bytes
> reiser-00338.test contains null bytes
> reiser-00374.test contains null bytes
> reiser-00407.test contains null bytes
> reiser-00415.test contains null bytes
> reiser-00430.test contains null bytes
> reiser-00438.test contains null bytes
> reiser-00445.test contains null bytes
> reiser-00459.test contains null bytes
> reiser-00481.test contains null bytes
> reiser-00501.test contains null bytes
> reiser-00508.test contains null bytes
> reiser-00521.test contains null bytes
> reiser-00534.test contains null bytes
> reiser-00558.test contains null bytes
> reiser-00577.test contains null bytes
> reiser-00583.test contains null bytes
> reiser-00600.test contains null bytes
> reiser-00606.test contains null bytes
> reiser-00612.test contains null bytes
> reiser-00623.test contains null bytes
> reiser-00634.test contains null bytes
> reiser-00645.test contains null bytes
> reiser-00665.test contains null bytes
> reiser-00685.test contains null bytes
> reiser-00730.test contains null bytes
> reiser-00735.test contains null bytes
> reiser-00740.test contains null bytes
> reiser-00745.test contains null bytes
> reiser-00750.test contains null bytes
> reiser-00759.test contains null bytes
> reiser-00764.test contains null bytes
> reiser-00773.test contains null bytes
> reiser-00778.test contains null bytes
> reiser-00787.test contains null bytes
> reiser-00796.test contains null bytes
> reiser-00805.test contains null bytes
> reiser-00814.test contains null bytes
> reiser-00866.test contains null bytes
> reiser-00915.test contains null bytes
> reiser-00930.test contains null bytes
> reiser-00934.test contains null bytes
> reiser-00938.test contains null bytes
> reiser-00942.test contains null bytes
> reiser-00946.test contains null bytes
> reiser-00950.test contains null bytes
> reiser-00954.test contains null bytes
> reiser-00958.test contains null bytes
> reiser-00965.test contains null bytes
> reiser-00969.test contains null bytes
> reiser-00973.test contains null bytes
> reiser-00977.test contains null bytes
> reiser-00984.test contains null bytes
> reiser-00988.test contains null bytes
> reiser-00995.test contains null bytes
> reiser-00999.test contains null bytes
> reiser-01006.test contains null bytes
> reiser-01010.test contains null bytes
> reiser-01017.test contains null bytes
> Checking done
>
>
> Running the test a couple of times doesn't really show a pattern,
> sometimes the same files contains null bytes, sometimes others do. The
> files with null bytes seem to be with index < 1024.
>
> I did the same test with an ext2 filesystem, but didn't see any error.
> System is SuSE 7.0, compiler gcc-2.95.2.
>
>
> Erik
>
>
--
Arjan Filius
mailto:iafilius@xs4all.nl
next prev parent reply other threads:[~2001-02-24 15:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 21:18 reiserfs: still problems with tail conversion Erik Mouw
2001-02-23 22:10 ` Chris Mason
2001-02-23 22:19 ` Erik Mouw
2001-02-24 2:52 ` Michal Gornisiewicz
2001-02-24 4:13 ` Meino Christian Cramer
2001-02-24 8:18 ` thunder7
2001-02-24 19:27 ` Ken Moffat
2001-02-24 20:53 ` Alan Cox
2001-02-25 0:41 ` Chris Mason
2001-02-25 4:21 ` Bernd Eckenfels
2001-02-25 5:41 ` Mike Galbraith
2001-02-25 13:53 ` Alan Cox
2001-02-25 16:37 ` Erik Mouw
2001-02-25 17:32 ` Erik Mouw
2001-02-26 2:40 ` [PATCH] " Chris Mason
2001-02-26 11:07 ` Erik Mouw
2001-02-26 15:37 ` Erik Mouw
2001-02-26 22:46 ` Ken Moffat
2001-02-25 20:32 ` Chris Mason
2001-02-24 0:34 ` Oliver Teuber
[not found] ` <01022318321302.01755@flash>
2001-02-24 8:40 ` John E. Adams
2001-02-24 15:45 ` Arjan Filius [this message]
2001-02-24 16:24 ` [lkml]Re: " thunder7
2001-02-24 17:28 ` Chris Mason
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=Pine.LNX.4.30.0102241613140.1185-100000@sjoerd.sjoerdnet \
--to=iafilius@xs4all.nl \
--cc=J.A.K.Mouw@ITS.TUDelft.NL \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
/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).