It would be really good to have more info on this.
When xfs_log_write says "reservation ran out" it probably means
that we didn't reserve enough in the xfs_trans_reserve call.
Can you figure out what transaction type this is?
If you are running with kdb, you could print the stack after setting
a break point at xfs_cmn_err() or icmn_err().
If you load the xfsidbg module, you can then print out some
of the structures including the xfs_trans structure. You should see
xfs_trans_commit() on the stack. The first parameter (tp) is a
pointer to the trans structure. This structure will contain the
t_type
and the amount of space reserved and ...
This can then help us determine if we need to bump the reservation amount
or if there is some other problem.
The tp also points at all the "log items", t_items.
If you could get this info, it would be great.
Thanks,
Jim
>
>> FYI
>>
>>
>> cmn_err level 1 Filesystem "ide0(3,1)": xfs_log_write: reservation ran out.
>> Need to up reservation
>> Corruption of in-memory data detected. Shutting down filesystem: ide0(3,1)
>> Please umount the filesystem, and rectify the problem(s)
>>
>> Haven't looked into it yet.
>> Will tomorrow...
>
>Hi guys. Look at this:
>
>
>[cut]
>Received: from oss.sgi.com (oss.sgi.com [216.32.174.118])
> by alladin.dds.nl (8.9.1/8.9.1) with ESMTP id BAA23151
> for <ookhoi@xxxxxx>; Tue, 9 May 2000 01:08:04 +0200 (MET DST)
>Received: by oss.sgi.com with SMTP id <S305162AbQEHXHv>;
> Mon, 8 May 2000 23:07:51 +0000
>Received: by oss.sgi.com (bulk_mailer v1.12); Mon, 8 May 2000 23:07:51 +0000
>Received: by oss.sgi.com id <S305174AbQDSXt0>;
> Wed, 19 Apr 2000 16:49:26 -0700
>Received: from deliverator.sgi.com ([204.94.214.10]:30575 "EHLO
> deliverator.sgi.com") by oss.sgi.com with ESMTP id <S305163AbQDSXtQ>;
> Wed, 19 Apr 2000 16:49:16 -0700
>
>==========
>20 days, how is dat possible? And I think I've seen this message before?
>
> Ookhoi
>
>
>Received: from ledzep.cray.com (ledzep.cray.com [137.38.226.97]) by
>deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id
>QAA28127
> for <linux-xfs@xxxxxxxxxxx>; Wed, 19 Apr 2000 16:44:30 -0700 (PDT)
> mail_from (cattelan@xxxxxxxxxxx)
>From: cattelan@xxxxxxxxxxx
>Received: from ironwood-e185.americas.sgi.com (ironwood.cray.com
>[128.162.185.212]) by ledzep.cray.com (SGI-SGI-8.9.3/craymail-smart-nospam1.0)
>with ESMTP id SAA89980 for <linux-xfs@xxxxxxxxxxx>; Wed, 19 Apr 2000 18:46:44
>-0500 (CDT)
>Received: from gibble.americas.sgi.com (root@xxxxxxxxxxxxxxxxxxxxxxx
>[128.162.195.80]) by ironwood-e185.americas.sgi.com (8.8.4/SGI-ironwood-e1.4)
>with ESMTP id SAA20286; Wed, 19 Apr 2000 18:46:34 -0500 (CDT)
>Received: from gibble.americas.sgi.com by gibble.americas.sgi.com
>(8.9.3/SGI-client.1.6) via ESMTP id SAA30673; Wed, 19 Apr 2000 18:46:41 -0500
>Date: Wed, 19 Apr 2000 18:46:39 -0500
>Message-ID: <14590.17759.41450.64144V@xxxxxxxxxxxxxxxxxxxxxxx>
>To: lord@xxxxxxx
>cc: linux-xfs@xxxxxxxxxxx
>Subject: Hmmm out of memory error
>User-Agent: Wanderlust/1.0.3 (Notorious) tm/7.108 XEmacs/21.1 (Bryce Canyon)
>Sender: owner-linux-xfs@xxxxxxxxxxx
>X-Orcpt: rfc822;linux-xfs-outgoing
>Status: RO
>Content-Length: 284
>Lines: 9
>
>FYI
>
>
>cmn_err level 1 Filesystem "ide0(3,1)": xfs_log_write: reservation ran out.
>Need to up reservation
>Corruption of in-memory data detected. Shutting down filesystem: ide0(3,1)
>Please umount the filesystem, and rectify the problem(s)
>
>Haven't looked into it yet.
>Will tomorrow...
>
|