Re: TAKE 884392 - Add a stack trace to _xfs_force

xfs

Re: TAKE 884392 - Add a stack trace to _xfs_force_shutdown.

To:	Derek Glidden <dglidden@xxxxxxxxxxxxxxx>
Subject:	Re: TAKE 884392 - Add a stack trace to _xfs_force_shutdown.
From:	Eric Sandeen <sandeen@xxxxxxx>
Date:	30 Oct 2003 10:28:14 -0600
Cc:	linux-xfs@xxxxxxxxxxx
In-reply-to:	<Pine.LNX.4.44.0310292323230.6171-100000@xxxxxxxxxxxxxxxxxxxxxx>
Organization:
References:	<Pine.LNX.4.44.0310292323230.6171-100000@xxxxxxxxxxxxxxxxxxxxxx>
Sender:	linux-xfs-bounce@xxxxxxxxxxx

I should amend that a little, Glen points out that this only works if
the shutdown is an 'in memory corruption' type.

It would be trivial for you to move it in your code to hit any
shutdown... we may do something similar.

-Eric

On Wed, 2003-10-29 at 23:33, Eric Sandeen wrote:
> In theory... :)
> 
> Set /proc/sys/fs/xfs/error_level to 5 or higher to turn it on.
> 
> -Eric

-- 
Eric Sandeen      [C]XFS for Linux   http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx   SGI, Inc.          651-683-3102

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
TAKE 884392 - Add a stack trace to _xfs_force_shutdown., Eric Sandeen Re: TAKE 884392 - Add a stack trace to _xfs_force_shutdown., Derek Glidden Re: TAKE 884392 - Add a stack trace to _xfs_force_shutdown., Eric Sandeen Re: TAKE 884392 - Add a stack trace to _xfs_force_shutdown., Eric Sandeen <=

Previous by Date:	[Bug 202] XFS data corruption (very old bug!!!), bugzilla-daemon
Next by Date:	Re: Linux 2.4.22 XFS 1.3.1 reservation ran out, Eric Sandeen
Previous by Thread:	Re: TAKE 884392 - Add a stack trace to _xfs_force_shutdown., Eric Sandeen
Next by Thread:	PARTIAL TAKE 893355 - Fix test for large sector_t, Eric Sandeen
Indexes:	[Date] [Thread] [Top] [All Lists]