All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>,
	linux-kernel@vger.kernel.org, npiggin@suse.de
Subject: Re: xfs problems (possibly after upgrading from linux kernel	2.6.27.10 to .14)
Date: Thu, 19 Feb 2009 11:13:05 +0100	[thread overview]
Message-ID: <499D30B1.30802@aei.mpg.de> (raw)
In-Reply-To: <20090219061925.GE8830@disturbed>

Hi again,

Dave Chinner schrieb:
>> I can try doing that on a few machines, would a metadump help on a
>> machine where this corruption occurred some time ago and is still in
>> this state?
> 
> If you unmount the filesystem, mount it again and then touch a new
> file and it reports the error again, then yes, a metadump woul dbe
> great.
> 
> If the error doesn't show up after a unmount/mount, then I
> can't use a metadump image to reproduce the problem.
> 

I've done it on two nodes so far and the result is not good (metadump wise):
[1344887.778232] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344887.778432] xfs_force_shutdown(sda6,0x1) called from line 420 of
file fs/xfs/xfs_rw.c.  Return address = 0xffffffff8031dd7e
[1344889.579836] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344889.580044] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344889.580257] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344889.580450] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344889.624774] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344915.783844] XFS mounting filesystem sda6
[1344915.872333] Starting XFS recovery on filesystem: sda6 (logdev:
internal)
[1344917.399834] Ending XFS recovery on filesystem: sda6 (logdev: internal)

After that I can touch/create all files I want on the fs again.

> I suspect so. We've already had XFS trigger one bug in the new
> lockless pagecache code, and the fix for that went in 2.6.27.11 -
> between the good version and the version that you've been seeing
> these memory corruptions on. I'm wondering if that fix exposed or
> introduced another bug that you've hit....
> 
> Nick?

If it was triggered by a user job, it might have been in the kernel for
longer and the user just did not run it for a few weeks.

I'll try to gather more information.

Cheers

Carsten

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>,
	linux-kernel@vger.kernel.org, npiggin@suse.de
Subject: Re: xfs problems (possibly after upgrading from linux kernel	2.6.27.10 to .14)
Date: Thu, 19 Feb 2009 11:13:05 +0100	[thread overview]
Message-ID: <499D30B1.30802@aei.mpg.de> (raw)
In-Reply-To: <20090219061925.GE8830@disturbed>

Hi again,

Dave Chinner schrieb:
>> I can try doing that on a few machines, would a metadump help on a
>> machine where this corruption occurred some time ago and is still in
>> this state?
> 
> If you unmount the filesystem, mount it again and then touch a new
> file and it reports the error again, then yes, a metadump woul dbe
> great.
> 
> If the error doesn't show up after a unmount/mount, then I
> can't use a metadump image to reproduce the problem.
> 

I've done it on two nodes so far and the result is not good (metadump wise):
[1344887.778232] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344887.778432] xfs_force_shutdown(sda6,0x1) called from line 420 of
file fs/xfs/xfs_rw.c.  Return address = 0xffffffff8031dd7e
[1344889.579836] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344889.580044] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344889.580257] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344889.580450] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344889.624774] Filesystem "sda6": xfs_log_force: error 5 returned.
[1344915.783844] XFS mounting filesystem sda6
[1344915.872333] Starting XFS recovery on filesystem: sda6 (logdev:
internal)
[1344917.399834] Ending XFS recovery on filesystem: sda6 (logdev: internal)

After that I can touch/create all files I want on the fs again.

> I suspect so. We've already had XFS trigger one bug in the new
> lockless pagecache code, and the fix for that went in 2.6.27.11 -
> between the good version and the version that you've been seeing
> these memory corruptions on. I'm wondering if that fix exposed or
> introduced another bug that you've hit....
> 
> Nick?

If it was triggered by a user job, it might have been in the kernel for
longer and the user just did not run it for a few weeks.

I'll try to gather more information.

Cheers

Carsten

  reply	other threads:[~2009-02-19 10:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 14:49 xfs problems (possibly after upgrading from linux kernel 2.6.27.10 to .14) Carsten Aulbert
2009-02-17 14:49 ` Carsten Aulbert
2009-02-17 15:19 ` Michael Monnerie
2009-02-17 15:56   ` Carsten Aulbert
2009-02-17 17:24 ` Eric Sandeen
2009-02-17 17:24   ` Eric Sandeen
2009-02-18  9:19 ` Dave Chinner
2009-02-18  9:19   ` Dave Chinner
2009-02-18  9:36   ` Carsten Aulbert
2009-02-18  9:36     ` Carsten Aulbert
2009-02-19  6:19     ` Dave Chinner
2009-02-19  6:19       ` Dave Chinner
2009-02-19 10:13       ` Carsten Aulbert [this message]
2009-02-19 10:13         ` Carsten Aulbert
2009-02-19 12:01       ` Nick Piggin
2009-02-19 12:01         ` Nick Piggin
2009-02-19 13:12         ` Carsten Aulbert
2009-02-19 13:12           ` Carsten Aulbert

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=499D30B1.30802@aei.mpg.de \
    --to=carsten.aulbert@aei.mpg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --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 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.