mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Madden <weez@freelists.org>
To: linux-kernel@vger.kernel.org
Subject: ReiserFS: clm-2201: last flush, clm-2200: last commit
Date: Sat, 12 Nov 2005 22:52:21 -0500	[thread overview]
Message-ID: <200511122252.21366.weez@freelists.org> (raw)

Following a crash last night (suspect buggy Dell BIOS, since upgraded), I'm 
now seeing thousands of: 

ReiserFS: dm-5: warning: clm-2200: last commit 2158066944, current 2158066945
ReiserFS: dm-5: warning: clm-2201: last flush 2158065946, current 2158065947

This is on both 2.6.12.5 (last night) and 2.4.14.1 as of tonight.  fsck 
reports no corruption and I have no reason other than these warnings to 
believe there is any, but this is (obviously) troubling nonetheless.  The 
relevant code is in fs/reiserfs/journal.c.  

For the flush case: 
        if (journal->j_last_flush_id != 0 &&
            (jl->j_trans_id - journal->j_last_flush_id) != 1) {
                reiserfs_warning(s, "clm-2201: last flush %lu, current %lu",
                                 journal->j_last_flush_id, jl->j_trans_id);
        }

And for the commit case:
        if (journal->j_last_commit_id != 0 &&
            (jl->j_trans_id - journal->j_last_commit_id) != 1) {
                reiserfs_warning(s, "clm-2200: last commit %lu, current %lu",
                                 journal->j_last_commit_id, jl->j_trans_id);
        }

The filesystem is mounted notail, no options with the journal.   Any hints as 
to what's up?  Should I expect corruption here?

John




-- 
# John Madden  weez@freelists.org: http://www.nerdarium.com
# FreeLists: Free mailing lists for all: http://www.freelists.org
# Linux, Apache, Perl and C: All the best things in life are free!

             reply	other threads:[~2005-11-13  3:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-13  3:52 John Madden [this message]
2005-11-20  1:23 ` John Madden

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200511122252.21366.weez@freelists.org \
    --to=weez@freelists.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®