reiser3: data=journal causes panic in 2.6.29.4

reiser3: data=journal causes panic in 2.6.29.4

[Carlos Carvalho]

Putting data=journal in the options in fstab makes the kernel stop at
boot complaining it couldn't get a lock. What's the status of data
journaling in reiser3?

Re: reiser3: data=journal causes panic in 2.6.29.4

[Christian Kujau]

On Fri, 19 Jun 2009, Carlos Carvalho wrote:
> Putting data=journal in the options in fstab makes the kernel stop at
> boot complaining it couldn't get a lock.

AFAIK there is no data= mount option for reiserfs. Where did you see this 
documented?

> What's the status of data journaling in reiser3?

In which regard?

-- 
BOFH excuse #408:

Computers under water due to SYN flooding.

Re: reiser3: data=journal causes panic in 2.6.29.4

[Carlos Carvalho]

Christian Kujau (lists@nerdbynature.de) wrote on 20 June 2009 23:07:
 >On Fri, 19 Jun 2009, Carlos Carvalho wrote:
 >> Putting data=journal in the options in fstab makes the kernel stop at
 >> boot complaining it couldn't get a lock.
 >
 >AFAIK there is no data= mount option for reiserfs. Where did you see this 
 >documented?

It's not in the man page; it's mentioned in some posts. Clearly, it's
recognized by mount and passed to the kernel, otherwise there'd be no
panic. Also, after it's mounted we can use
mount -o remount,data=journal. In a freshly mounted partition it seems
to work; there are no hangs, and creating/removing/changing files
works. On a busy fs it hangs.

 >> What's the status of data journaling in reiser3?
 >
 >In which regard?

Does it work? Should it work? Is there any relation to the recent
changes with locking?

Re: reiser3: data=journal causes panic in 2.6.29.4

[Christian Kujau]

On Sun, 21 Jun 2009, Carlos Carvalho wrote:
> It's not in the man page; it's mentioned in some posts.

And it's been in fs/reiserfs/super.c for quite some time; commit bd4c625c 
is from 07/2005 where the mount options merely got formatted - I wonder 
why this hasn't been documented yet. Then again, the latest manpages 
tarball still lists the mount(8) manpage as updated on 2004-12-16...

-- 
BOFH excuse #210:

We didn't pay the Internet bill and it's been cut off.

Re: reiser3: data=journal causes panic in 2.6.29.4

[Edward Shishkin]

Carlos Carvalho wrote:
> Christian Kujau (lists@nerdbynature.de) wrote on 20 June 2009 23:07:
>  >On Fri, 19 Jun 2009, Carlos Carvalho wrote:
>  >> Putting data=journal in the options in fstab makes the kernel stop at
>  >> boot complaining it couldn't get a lock.
>  >
>  >AFAIK there is no data= mount option for reiserfs. Where did you see this 
>  >documented?
>
>   

Reiserfs has mount options "data=journal", "data=ordered", data=writeback,
which have the same meaning as in the case of ext3.
Description of all reiserfs mount options can be found here:
http://web.archive.org/web/20061113154827/www.namesys.com/mount-options.html

> It's not in the man page; it's mentioned in some posts. Clearly, it's
> recognized by mount and passed to the kernel, otherwise there'd be no
> panic. Also, after it's mounted we can use
> mount -o remount,data=journal. In a freshly mounted partition it seems
> to work; there are no hangs, and creating/removing/changing files
> works. On a busy fs it hangs.
>
>  >> What's the status of data journaling in reiser3?
>   

It should work.

Are you sure that your system hangs on reiserfs?
If yes, then please, let's start with checking your
partition with reiserfsck.

Thanks,
Edward.

>  >
>  >In which regard?
>
> Does it work? Should it work? Is there any relation to the recent
> changes with locking?
> --
> To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>