From: Tomek Kruszona <bloodyscarion@gmail.com>
To: Steffen Knauf <Steffen.Knauf@gmx.net>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_log_force: error 5 returend
Date: Mon, 14 Sep 2009 17:09:31 +0200 [thread overview]
Message-ID: <4AAE5CAB.6090602@gmail.com> (raw)
In-Reply-To: <20090914100548.45440@gmx.net>
Steffen Knauf wrote:
> hello,
>
> sometimes, our server crashed with xfs_log_force: error 5.
> It isn't reproducible and a xfs_check / xfs_repair don't find some errors.
>
> Perhaps it's a bug?
>
> Version: Linux version 2.6.26-bpo.1-amd64 (Debian 2.6.26-9~bpo40+1) (nobse@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21
>
> greets
>
> Steffen
Hello!
Look at http://oss.sgi.com/bugzilla/show_bug.cgi?id=840
Please provide your dmesg output regarding kernel oops message (maybe
there is similar issue in your case as I had)
It seems that in my case it was a problem of HBA configuration (using
LVM2 and caches) as Christoph Hellwig replied. After proper
configuration I had similar issues still, but last Friday I upgraded HBA
firmware because I've found that there was an issue with cache mode
report (software reported that write caches are disabled but they were
still enabled). I hope this will help in my case - for now I had no
crash. We'll see within next week (it occurs about once a week).
In your case without oops message it's really hard to tell what's wrong.
Best regards,
Tomasz Kruszona
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-09-14 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-14 10:05 xfs_log_force: error 5 returend Steffen Knauf
2009-09-14 15:09 ` Tomek Kruszona [this message]
2009-09-14 16:41 ` Christoph Hellwig
2009-09-14 17:46 ` Eric Sandeen
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=4AAE5CAB.6090602@gmail.com \
--to=bloodyscarion@gmail.com \
--cc=Steffen.Knauf@gmx.net \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox