Re: REISER4 corruptions errors

Paolo Correnti writes:
 > In my last message "REISER4 strange partition size"
 > I wrote:
 > 
 > "... making intensive writing test on this
 > reiser4 partition (for example: writing 1 million rows
 > on an Oracle table in archivelog mode) on each test I
 > obtain a corrupted redolog file [sometimes is
 > recoverable, sometimes I've to rebuild the entire
 > DB)."
 > 
 > And Nikita answered:
 > 
 > "It is not clear how to diagnose this. What oracle
 > are you using? Is it available freely?"
 > 
 > Really I think this test is not so easy to prepare
 > (you have to download Oracle, install it and bla bla
 > ...) but I think my last test is more "human".
 > 
 > I recomplied Kernel 2.6.0 with
 > CONFIG_REISER4_BADBLOCKS=y
 > 
 > I'm using 2.6.0 + 20031223 snapshot because 
 > 2.6.1 + 20040119_fixed always gives me some file
 > corrupted and I was spending too much time re-creating
 > Oracle DB.
 > 
 > Reiser4 partition is mounted with tmgr.atom_max_age=20
 > option.
 > 
 > I noticed that if you copy a large amount of data (at
 > least 500 Mb) from a partition to a Reiser4 partition,
 > umounting Reiser4 part and using fsck.reiser4
 > you always obtain from 5 to 40 (and more) fixable
 > corruptions detected.
 > 
 > It seems that with 2.6.0 + 20031223 snapshot these
 > corruptions are not so "dangerous" to corrupt files
 > (I mean, also with these corruptions I'm able to work
 > with Oracle). Unfortunately I cannot say the same
 > with 2.6.1 and latest snapshot.

Well, for all I know, this very well may be a bug in the fsck, rather
than corruption of the on-disk data structures. Are you experiencing any
problems when _using_ this partition (error messages in the kernel log,
crashes, deadlocks, etc.)?

 > 
 > Any idea ?
 > 
 > All the best
 > 
 > Paolo
 >

Nikita.