journal-2018 trouble?

journal-2018 trouble?

[Gustavo Zacarias]

Hi.
I'm getting loads of journal-2018 kernel messages when mounting a reiser 
filesystem from a lvm block device.

---snip---
Mar 24 22:22:30 anubis kernel: reiserfs: checking transaction log (device 
3a:00) ...
Mar 24 22:22:30 anubis kernel: journal-2018: Bad transaction length 7 
encountered, ignoring transaction
---

Of course they vary in transaction length.

---reiserfsck 3.6.5 snip---
reiserfs_open_journal: journal parameters from super block does not match to
journal parameters from journal.

Either make journal partition available or use --no-journal-available
If you have the standard journal or if your partition is available
and you specified it correctly, you must run rebuild-sb.
---

This is a 2.4.20 kernel with 2.4.20-pending patches, namely
01-iput-deadlock-fix
02-directio-fix
03-journal-overflow-fix
04-trivial1
05-more-mount-checks

Information is just fine, everything works, i'm just a little worried about 
the warnings. The machine has been (obviously) shut down uncleanly some 
times.
Would a rebuild-sb be safe?
Thanks in advance.

Re: journal-2018 trouble?

[Oleg Drokin]

Hello!

On Mon, Mar 24, 2003 at 10:55:48PM -0300, Gustavo Zacarias wrote:

> I'm getting loads of journal-2018 kernel messages when mounting a reiser 
> filesystem from a lvm block device.
> ---snip---
> Mar 24 22:22:30 anubis kernel: reiserfs: checking transaction log (device 
> 3a:00) ...
> Mar 24 22:22:30 anubis kernel: journal-2018: Bad transaction length 7 
> encountered, ignoring transaction
> ---

Argh, you have formatted your filesystem with some old fsck version that does not put
correct journal information into superblock.
So it thinks journal size is zero and rejects to replay any transactions.
Hm, I wonder how that problem escaped our tests.

> ---reiserfsck 3.6.5 snip---
> reiserfs_open_journal: journal parameters from super block does not match to
> journal parameters from journal.
> Either make journal partition available or use --no-journal-available
> If you have the standard journal or if your partition is available
> and you specified it correctly, you must run rebuild-sb.
> ---
> 05-more-mount-checks

Please either do not apply this patch or follow the rebuild-sb advance (it will ask you
if you want to update journal paremreters and you should agree).

I will come up with the fix shortly.
Also this have nothing to do with LVM

Bye,
    Oleg

Re: journal-2018 trouble?

[Oleg Drokin]

Hello!

On Tue, Mar 25, 2003 at 09:32:30AM +0300, Oleg Drokin wrote:

> Please either do not apply this patch or follow the rebuild-sb advance (it will ask you
> if you want to update journal paremreters and you should agree).
> I will come up with the fix shortly.

Ok, here's supposed fix.
If you have not did rebuild-sb, you might want to try it.

(for those using data-logging patches, you do not need this patch as it does correct thing already).

Bye,
    Oleg

===== fs/reiserfs/journal.c 1.26 vs edited =====
--- 1.26/fs/reiserfs/journal.c	Thu Mar 13 14:52:15 2003
+++ edited/fs/reiserfs/journal.c	Tue Mar 25 16:38:55 2003
@@ -1401,7 +1401,7 @@
 		     *newest_mount_id) ;
       return -1 ;
     }
-    if ( le32_to_cpu(desc->j_len) > sb_journal_trans_max(SB_DISK_SUPER_BLOCK(p_s_sb)) ) {
+    if ( le32_to_cpu(desc->j_len) > JOURNAL_TRANS_MAX ) {
       reiserfs_warning("journal-2018: Bad transaction length %d encountered, ignoring transaction\n", le32_to_cpu(desc->j_len));
       return -1 ;
     }

Re: journal-2018 trouble?

[Gustavo Zacarias]

Oleg Drokin wrote:

> Ok, here's supposed fix.
> If you have not did rebuild-sb, you might want to try it.
> 
> (for those using data-logging patches, you do not need this patch as it does correct thing already).

Hi.
Yes, i haven't rebuilt it yet, i was hopeful a patch would arrive soon.
Life is beautiful, no more journal-2018's, it works :-)
I guess i should rebuild the journal anyway right?
BTW, it's reiserfsutils shipped with redhat 7.3 which was used to build 
the filesystem (3.x.0j).
Thanks, bye.