From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Sean Plaice <splaice@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiserfs errors in dmesg output
Date: Sat, 03 Jul 2004 16:53:11 +0400 [thread overview]
Message-ID: <40E6AC37.1090609@namesys.com> (raw)
In-Reply-To: <ae9bd76a040703052222e0065f@mail.gmail.com>
Hello
Sean Plaice wrote:
> Hello,
> My system is running linux 2.4.33
Please double check linux version.
with reiserfs for all of it's files
> systems, The system has a PERC-3DC Raid card (uses the aacraid
> driver).
>
> The server is a very io intensive mail server.
>
> I have recently noticed some "troubleing" output in the dmesg output.
> The server does not appear to be having any operational problems but
> the errors are leading me to be quite worried of potential future
> problems.
>
> Could someone please help me diagnose what these error messages mean,
> and what I should do about them.
>
> Thank you in advance for your answers, take care.
>
> <snip>
>
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 28)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 28)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 28)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 28)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 28)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 28)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 28)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 50)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 50)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 50)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
> sd(8,6):vs-13060: reiserfs_update_sd: stat data of object [1131
> 1466199 0x0 SD] (nlink == 1) not found (pos 3)
>
These is not too bad in this. But,
would you run find -inum 1466199?
What do you get?
> and
>
> sd(8,6):journal-1777: buffer 109798 bad state !PREPARED !LOCKED !DIRTY
> JDIRTY_WAIT
> sd(8,6):journal-1777: buffer 185659 bad state !PREPARED !LOCKED !DIRTY
> JDIRTY_WAIT
> sd(8,6):journal-1777: buffer 208840 bad state !PREPARED !LOCKED !DIRTY
> JDIRTY_WAIT
> sd(8,6):journal-1777: buffer 300870 bad state !PREPARED !LOCKED !DIRTY
> JDIRTY_WAIT
>
IIRC, sometime ago, there were some fixes for race conditions which
might cause this. Chris, would you please confirm that?
> </snip>
>
next prev parent reply other threads:[~2004-07-03 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 12:22 reiserfs errors in dmesg output Sean Plaice
2004-07-03 12:53 ` Vladimir V. Saveliev [this message]
2004-07-03 23:10 ` Sean Plaice
2004-07-04 8:41 ` Vladimir V. Saveliev
2004-07-14 10:45 ` Sean Plaice
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=40E6AC37.1090609@namesys.com \
--to=vs@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=splaice@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.