xfs
[Top] [All Lists]

ADD 802017 - ASSERT fail in xlog_get_bp on small mem machine

To: dxm@xxxxxxxxxxxx
Subject: ADD 802017 - ASSERT fail in xlog_get_bp on small mem machine
From: pv@xxxxxxxxxxxxx (lord@xxxxxxx)
Date: Tue, 19 Sep 2000 07:08:24 -0700 (PDT)
Cc: linux-xfs@xxxxxxxxxxx
Reply-to: sgi.bugs.xfs@xxxxxxxxxxxxxxxxx
Sender: owner-linux-xfs@xxxxxxxxxxx
Webexec: webpvupdate,pvincident
Webpv: jen.americas.sgi.com
View Incident: 
http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=802017

 Status : open                         Priority : 3                         
 Assigned Engineer : dxm               Submitter : dxm                      
*Modified User : lord                 *Modified User Domain : sgi.com       
*Description :
I haven't seen this problem for ages on my 64Mb crash box,
but the problem is still there.

I installed XFS on my home machine last night and was very
happy with its performance (P100, 32Mb RAM, 32Gb disk) until 
I tried to cleanly remount my XFS partition and tripped an 
ASSERT in xlog_get_bp.

My home machine is very tight on memory, but I don't think
it's an unreasonable machine to try to run XFS on. Unfortunately,

.....


==========================
ADDITIONAL INFORMATION (ADD)
From: lord@xxxxxxx (BugWorks)
Date: Sep 19 2000 07:08:24AM
==========================

I would apply this - without the warning message which replaced
the ASSERT, just return the NULL. The caller will report an
ENOMEM error back to user space and the mount will fail. The
other message is just extra noise.

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