Re: [reiserfs-list] ReiserFS 3.5.32 stability ?

2001-05-27 Thread Ragnar Kjørstad
On Mon, May 28, 2001 at 06:41:42AM +0400, Vladimir V. Saveliev wrote: > > * there is no easy way to tell if a particular stat-data is in v1 or v2 > > format in link. > > Yes, there is. They have different length. But this information is not easily available where it's actually used, in mkdir a

Re: [reiserfs-list] File corruption in journal replay

2001-05-27 Thread Matthew Hawkins
On Mon, 28 May 2001, Jonathan Hseu wrote: > Shouldn't journal replays replay what is being written so that it is actually > the correct data instead of random incorrect data? Only on a filesystem supporting full data journaling. I'm not aware of one for Linux right now. JFS, XFS, ext3, reiserfs

Re: [reiserfs-list] File corruption in journal replay

2001-05-27 Thread Henrik Nordstrom
Jonathan Hseu wrote: > > I run kernel 2.4.5, SMP + reiserfs, and I was copying a file, when I crashed and > rebooted. After reboot, I compared the file that was copying, and found that > they differed. What should happen is that the two files should be equivalent > up until the position of the

[reiserfs-list] File corruption in journal replay

2001-05-27 Thread Jonathan Hseu
I run kernel 2.4.5, SMP + reiserfs, and I was copying a file, when I crashed and rebooted. After reboot, I compared the file that was copying, and found that they differed. What should happen is that the two files should be equivalent up until the position of the end of the file that it was copy

Re: [reiserfs-list] ReiserFS 3.5.32 stability ?

2001-05-27 Thread Henrik Nordstrom
Vladimir V. Saveliev wrote: > It is doable, but afaics now it looks almost useless as far as st_nlink is 16 bit > even in stat64. glibc uses int for link count (all modes). typedef __u_int __nlink_t; /* Type of file link counts. */ kernel stat uses short struct stat { [...

Re: [reiserfs-list] ReiserFS 3.5.32 stability ?

2001-05-27 Thread Vladimir V. Saveliev
Hi Ragnar Kjørstad wrote: > On Sun, May 27, 2001 at 11:47:51PM +0400, Vladimir V. Saveliev wrote: > > > > On a filesystem of 3.6 format you can have files longer than 2 gb and have > > > > more that 64k links to a file. > > > If you're refering to my patch, it doesn't allow more than 64k links,

Re: [reiserfs-list] ReiserFS 3.5.32 stability ?

2001-05-27 Thread Ragnar Kjørstad
On Sun, May 27, 2001 at 11:47:51PM +0400, Vladimir V. Saveliev wrote: > > > On a filesystem of 3.6 format you can have files longer than 2 gb and have > > > more that 64k links to a file. > > If you're refering to my patch, it doesn't allow more than 64k links, > > only more than 64k subdirectorie

Re: [reiserfs-list] ReiserFS 3.5.32 stability ?

2001-05-27 Thread Vladimir V. Saveliev
Hi Ragnar Kjørstad wrote: > On Sun, May 27, 2001 at 06:12:22AM +0400, Vladimir V. Saveliev wrote: > > > 2. What are the differences between ReiserFS for 2.2.x kernels and 2.4.x > > > kernels as for now ? Except the target kernel version, of course... > > > > > > > There are 2 formats of reiserfs

Re: [reiserfs-list] ReiserFS 3.5.32 stability ?

2001-05-27 Thread Ragnar Kjørstad
On Sun, May 27, 2001 at 06:12:22AM +0400, Vladimir V. Saveliev wrote: > > 2. What are the differences between ReiserFS for 2.2.x kernels and 2.4.x > > kernels as for now ? Except the target kernel version, of course... > > > > There are 2 formats of reiserfs. They are referred to as 3.5 and 3.6.

Re: [reiserfs-list] segfault: journal_begin called without kernellock held

2001-05-27 Thread Gergely Tamas
Hi! > It seems, the next patch can fix umount reiserfs bug in linux-2.4.5 : This worked. Thanks. BTW, Alexander Viro posted a patch to the LKML which fixes this problem by inserting a lock & unlock into fs/super.c . Gergely -- Date: Sun, 27 May 2001 00:24:46 -0400 (EDT) From: Alexander Viro <