The 02.11.26 at 01:37, Mark Gray wrote:

I just had a random freeze on my main server running 8.1 and I would like to get more information on the barrier=none problem. I just recently joined the list and have tried searching using google.com and manually searching the archive reading every 'crash', 'freeze', 'reiserfs' and 'hang' article that was posted to suse-linux-e, but was unable to find the original thread, or any discussion of the problem at all.

I watched the thread, but I saw no explanation of what "barrier=none" does. The mail in question was an excerpt from some other mail that explained it, but the original I never got. Probably it was posted to some other list. I only know it worked for me. Mmm, from the /usr/src/linux/fs/reiserfs/file I just got the possible options: } else if (!strcmp (this_char, "barrier")) { if (value && *value) { if (!strcmp(value, "flush")) { set_bit (REISERFS_BARRIER_FLUSH, mount_options); printk("reiserfs: enabling write barrier flush code\n") ; } else if (!strcmp(value, "tag")) { set_bit (REISERFS_BARRIER_TAG, mount_options); printk("reiserfs: enabling write barrier tag code\n") ; } else if (!strcmp(value, "none")) { set_bit (REISERFS_BARRIER_NONE, mount_options); printk("reiserfs: turning off barrier code\n") ; } else { printk("reiserfs: invalid barrier option\n"); return 0; } } else { printk("reiserfs: barrier option requires a value\n"); return 0; } } else if (!strcmp (this_char, "test4")) { I also had a look at the reiserfs web page, but no luck, it was not documented nor mentioned :-(

Could someone point me to it. Also, I have several large reiserfs 3.5 partitions left over from 7.3, is there any risk to mixing reiserfs 3.5 and 3.6 filesystems in the same machine?

I have such mixture, I haven't noticed anything. I don't know what to look for in that respect, either :-) -- Cheers, Carlos Robinson