xfs
[Top] [All Lists]

Re: Need to up reservation ...

To: Gaspar Bakos <gbakos@xxxxxxxxxxxxxxx>
Subject: Re: Need to up reservation ...
From: Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 28 Jan 2006 11:42:30 +0100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <Pine.SOL.4.58.0601272049280.16779@titan.cfa.harvard.edu>
References: <Pine.SOL.4.58.0601272049280.16779@titan.cfa.harvard.edu>
Reply-to: christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, Jan 27, 2006 at 08:54:12PM -0500, Gaspar Bakos wrote:
> Dear all,
> 
> After the following messages, my (remote) system hang:
> 
> Jan 27 02:15:38 hat10 kernel: Filesystem "md(9,3)": xfs_log_write: 
> reservation ran out. Need to up reservation
> Jan 27 02:15:38 hat10 kernel: xfs_force_shutdown(md(9,3),0x8) called from 
> line 1739 of file xfs_log.c.  Return address = 0xc01e2a9b
> Jan 27 02:15:38 hat10 kernel: Filesystem "md(9,3)": Corruption of in-memory 
> data detected.  Shutting down filesystem: md(9,3)
> Jan 27 02:15:38 hat10 kernel: Please umount the filesystem, and rectify the 
> problem(s)
> Jan 27 02:15:38 hat10 kernel: xfs_force_shutdown(md(9,3),0x2) called from 
> line 1321 of file xfs_log.c.  Return address = 0xc01e2a9b
> 
> This is a PIV PC with 0.5Gb RAM, RH9.0 Linux with 2.4.22 kernel patched
> for XFS support (2.4.22-xfs-031010). The previous uptime was something
> like half a year.
> 
This is probably Bug #284 (and #313) - 
http://oss.sgi.com/bugzilla/show_bug.cgi?id=284, which started to
happen in 2.4.22 CVS days. It has been fixed by Glen Overby sometime in
March 2004. I guess, uprading your kernel to 2.4.32 should solve this problem.

cheers.
 - Christian
 


<Prev in Thread] Current Thread [Next in Thread>