xfs
[Top] [All Lists]

Need to up reservation ...

To: linux-xfs@xxxxxxxxxxx
Subject: Need to up reservation ...
From: Gaspar Bakos <gbakos@xxxxxxxxxxxxxxx>
Date: Fri, 27 Jan 2006 20:54:12 -0500 (EST)
Reply-to: gbakos@xxxxxxxxxxxxxxx
Sender: linux-xfs-bounce@xxxxxxxxxxx
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.

The questions are the usual:
1. What could be the problem? I suspect faulty memory.

2. What could be done from __remotely__? Someone hard-reset the PC, and it
booted up fine, but with a mounted / I can not run xfs_check or repair.

Ideas welcome ...

Best wishes
Gaspar


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