reiserfs: still problems with tail conversion

reiserfs: still problems with tail conversion

Post by Erik Mou » Sun, 25 Feb 2001 06:30:03



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;

Quote:}

When I run this on a reiserfs partition, I get output like this:


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

--
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031,  2600 GA Delft, The Netherlands

WWW: http://www-ict.its.tudelft.nl/~erik/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Chris Maso » Sun, 25 Feb 2001 07:20:04


On Friday, February 23, 2001 10:18:56 PM +0100 Erik Mouw


> 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:

Many thanks for sending along a test program for reproducing.  But, it
doesn't seem to reproduce the problem here, how many times did you have to
run it to see the null bytes?  Do you remove the files between runs?

-chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Erik Mou » Sun, 25 Feb 2001 07:30:05



> Many thanks for sending along a test program for reproducing.  But, it
> doesn't seem to reproduce the problem here, how many times did you have to
> run it to see the null bytes?  Do you remove the files between runs?

I got them immediately at the first run, which more or less was what I
expected because reiserfs ate one of my mailfolders that way (only a
CVS log folder, so nothing special was lost). You have to remove the
files between runs, otherwise the same blocks seem to be allocated to
the files.

I'll upgrade to linux-2.4.2 to see if it solves the problem. (was
running 2.4.2-pre4 + your patch)

Erik

--
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Department
of Electrical Engineering, Faculty of Information Technology and Systems,
Delft University of Technology, PO BOX 5031,  2600 GA Delft, The Netherlands

WWW: http://www-ict.its.tudelft.nl/~erik/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Oliver Teube » Sun, 25 Feb 2001 09:40:05



> On Friday, February 23, 2001 10:18:56 PM +0100 Erik Mouw

> > 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:
> Many thanks for sending along a test program for reproducing.  But, it
> doesn't seem to reproduce the problem here, how many times did you have to
> run it to see the null bytes?  Do you remove the files between runs?

i cant reproduce the problem on my system runnig 2.4.2, too.

no problem so far ;)

reiserfs on an 46gb ibm ide hdd, 750mhz p3, 256mb ram

yours, oliver teuber

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Michal Gornisiewic » Sun, 25 Feb 2001 12:00:05



Quote:> I'll upgrade to linux-2.4.2 to see if it solves the problem. (was
> running 2.4.2-pre4 + your patch)

> Erik

I'm running 2.4.2 and I get similar results using your test program.
This is on an IBM 390 Laptop. P2-233, 96mb RAM, 3.2gb HDD.

See program results below. I can supply more info
(.config etc, & do testing) if needed.

MG

Creating 8192 files ... done
Appending to the files ... done
Checking files for null bytes ...
  reiser-00107.test contains null bytes
  reiser-00127.test contains null bytes
  reiser-00208.test contains null bytes
  reiser-00234.test contains null bytes
  reiser-00259.test contains null bytes
  reiser-00303.test contains null bytes
  reiser-00324.test contains null bytes
  reiser-00343.test contains null bytes
  reiser-00371.test contains null bytes
  reiser-00388.test contains null bytes
  reiser-00444.test contains null bytes
  reiser-00452.test contains null bytes
  reiser-00459.test contains null bytes
  reiser-00466.test contains null bytes
  reiser-00495.test contains null bytes
  reiser-00502.test contains null bytes
  reiser-00515.test contains null bytes
  reiser-00522.test contains null bytes
  reiser-00535.test contains null bytes
  reiser-00548.test contains null bytes
  reiser-00608.test contains null bytes
  reiser-00614.test contains null bytes
  reiser-00620.test contains null bytes
  reiser-00626.test contains null bytes
  reiser-00637.test contains null bytes
  reiser-00648.test contains null bytes
  reiser-00659.test contains null bytes
  reiser-00669.test contains null bytes
  reiser-00674.test contains null bytes
  reiser-00704.test contains null bytes
  reiser-00744.test contains null bytes
  reiser-00749.test contains null bytes
  reiser-00754.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-00792.test contains null bytes
  reiser-00801.test contains null bytes
  reiser-00810.test contains null bytes
  reiser-00819.test contains null bytes
  reiser-00847.test contains null bytes
  reiser-00855.test contains null bytes
  reiser-00899.test contains null bytes
  reiser-00947.test contains null bytes
  reiser-00951.test contains null bytes
  reiser-00955.test contains null bytes
  reiser-00959.test contains null bytes
  reiser-00963.test contains null bytes
  reiser-00967.test contains null bytes
  reiser-00971.test contains null bytes
  reiser-00978.test contains null bytes
  reiser-00982.test contains null bytes
  reiser-00986.test contains null bytes
  reiser-00990.test contains null bytes
  reiser-00997.test contains null bytes
  reiser-01001.test contains null bytes
  reiser-01005.test contains null bytes
  reiser-01012.test contains null bytes
  reiser-01016.test contains null bytes
Checking done
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Meino Christian Crame » Sun, 25 Feb 2001 15:20:04



Subject: Re: reiserfs: still problems with tail conversion
Date: Sat, 24 Feb 2001 10:52:07 +0800

I'm running 2.4.2ac3 and tried also the reisertest program.
No problems here...

The created files are all of 8192 bytes. Partition size was 1Gig.

  keep hacking the right site of life ! :-)
  Meino  

Quote:> I'm running 2.4.2 and I get similar results using your test program.
> This is on an IBM 390 Laptop. P2-233, 96mb RAM, 3.2gb HDD.

> See program results below. I can supply more info
> (.config etc, & do testing) if needed.

> MG

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
 
 
 

reiserfs: still problems with tail conversion

Post by thund.. » Sun, 25 Feb 2001 17:40:03



> I got them immediately at the first run, which more or less was what I
> expected because reiserfs ate one of my mailfolders that way (only a
> CVS log folder, so nothing special was lost). You have to remove the
> files between runs, otherwise the same blocks seem to be allocated to
> the files.

> I'll upgrade to linux-2.4.2 to see if it solves the problem. (was
> running 2.4.2-pre4 + your patch)

kernel 2.4.2-ac3, gcc-2.95.2, libc-2.1.3, SuSE-7.0 base system.
Using ReiserFS 3.5.x disk format, binutils-2.10, x86(P3/866)-SMP system.
The program from Erik did the following:

Creating 8192 files ... done
Appending to the files ... done
Checking files for null bytes ...
  reiser-00000.test contains null bytes
  reiser-00001.test contains null bytes
  reiser-00002.test contains null bytes
  reiser-00003.test contains null bytes
  reiser-00004.test contains null bytes
<snip a lot of lines>
  reiser-08189.test contains null bytes
  reiser-08190.test contains null bytes
  reiser-08191.test contains null bytes
Checking done

Good luck,
Jurriaan
--
Backup Not Found (A)ssasinate Bill Gates (R)etry (K)eep trying until 6 am?
GNU/Linux 2.4.2-ac3 SMP/ReiserFS 2x1730 bogomips load av: 0.08 0.02 0.01
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by John E. Adam » Sun, 25 Feb 2001 17:50:03



Quote:> 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:

I tried the test pgm.
First run didn't even hit the disk, so I added O_SYNC to the opens.
No errors were detected.  Then i split out the checking code from the
building code after noticing the checks were run against the buffer cache.
Still no errors.

This is a SuSE 7.0 machine w/512M memory, plenty of disk space and no swap,
running 2.4.2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Arjan Filiu » Mon, 26 Feb 2001 01:00:04


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,


> 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:


> 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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Chris Maso » Mon, 26 Feb 2001 02:40:05


On Saturday, February 24, 2001 04:45:04 PM +0100 Arjan Filius


> 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

Ah, I did not get it at 128M, but did get the messages at 32MB.  The read
stage of the test program does not close the fd by the way, so some of the
errors were from that (but not all).

So, there must be somewhere else that we are screwing up the tail
conversion, I'll see what I can find.

-chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by thund.. » Mon, 26 Feb 2001 04:00:06



> 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.

I can't confirm that. This machine has 512 Mb memory:

free
             total       used       free     shared    buffers     cached
Mem:        512940     144916     368024          0      12052     106552
-/+ buffers/cache:      26312     486628
Swap:      1992052          0    1992052

<after the failing test>
             total       used       free     shared    buffers     cached
Mem:        512940     144924     368016          0      12052     106552
-/+ buffers/cache:      26320     486620
Swap:      1992052          0    1992052

Jurriaan
--
BOFH excuse #167:

excessive collisions & not enough packet ambulances
GNU/Linux 2.4.2-ac3 SMP/ReiserFS 2x1730 bogomips load av: 0.26 0.06 0.02
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Ken Moffa » Mon, 26 Feb 2001 05:40:06


(reisertest)

I get the same problems with straight 2.4.2, machine is a k5 with
32Mb. The test results vary depending on what else is on the partition,
but in each case the last file affected is 01017 and there are sequences
of previous_number+4, for up to 8 files (but next file after this might be
previous+7 or previous +15, or sporadic). From other problems I've seen on
the list, maybe I need more memory to run reiserfs ?

This happens whether I compile the kernel (and/or the test program) with
Red Hat's revised gcc-2.96 or with egcs. First testing was with a
partition created from the rpm version of mkreiserfs, while running a
2.96-built-kernel. I've now recreated the partition while running a kernel
compiled with egcs ('kgcc'), the only difference is some of the numbers
for the affected files differ.

Partition approx 1.7Gb, built with defaults, block size is 4096.

More details of config or whatever available if required.

Ken

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Alan Co » Mon, 26 Feb 2001 06:00:06


Quote:> 32Mb. The test results vary depending on what else is on the partition,
> but in each case the last file affected is 01017 and there are sequences
> of previous_number+4, for up to 8 files (but next file after this might be
> previous+7 or previous +15, or sporadic). From other problems I've seen on
> the list, maybe I need more memory to run reiserfs ?

No. Reiserfs cannot go around corrupting files regardless of the amount of
memory you have. What is however quite possible is that there is a race
condition on reiserfs (or in the VFS) that is triggered when you are paging
and programs are thus sleeping on buffer and memory allocations

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Chris Maso » Mon, 26 Feb 2001 09:50:04


On Saturday, February 24, 2001 08:53:15 PM +0000 Alan Cox


>> 32Mb. The test results vary depending on what else is on the partition,
>> but in each case the last file affected is 01017 and there are sequences
>> of previous_number+4, for up to 8 files (but next file after this might
>> be previous+7 or previous +15, or sporadic). From other problems I've
>> seen on the list, maybe I need more memory to run reiserfs ?

> No. Reiserfs cannot go around corrupting files regardless of the amount of
> memory you have. What is however quite possible is that there is a race
> condition on reiserfs (or in the VFS) that is triggered when you are
> paging and programs are thus sleeping on buffer and memory allocations

Exactly.  The tail conversion code depends heavily on the page up to date
bit being set right.  It is more than possible that I've screwed up
something there, and the code thinks a page is valid when it really isn't.

-chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

reiserfs: still problems with tail conversion

Post by Bernd Eckenfel » Mon, 26 Feb 2001 13:30:03



> Exactly.  The tail conversion code depends heavily on the page up to date
> bit being set right.  It is more than possible that I've screwed up
> something there, and the code thinks a page is valid when it really isn't.

I have seen null byte corruptions in syslog files with ext2 in various
kernels. So perhaps it is a general VFS problem?

Greetings
Bernd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/