[DRBD-user] trace out of no where

Lars Ellenberg Lars.Ellenberg at linbit.com
Fri Jun 30 20:52:34 CEST 2006

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

/ 2006-06-30 13:41:01 -0400
\ Vampire D:
> Everything is plugging along fine, then all of a sudden all services are
> unavailable.  I fail over the heartbeat to the other node, and reboot the
> strange acting node.
> I looked in /var/log/messages and noticed this, any ideas what could have
> caused this?

> kernel/drivers+-866879/96] [drbd:__insmod_drbd_O/lib/modules/2.4.27-3-686-smp/
> [drbd:__insmod_drbd_O/lib/modules/2.4.27-3-686-smp/kernel/drivers+-447720/96]
> [clear_inode+260/320] [iput+184/800] [vfs_unlink+385/640]
> kernel:   [sys_unlink+187/288] [system_call+51/56]
> kernel: xfs_force_shutdown(drbd(147,0),0x8) called from line 4049 of file
> xfs_bmap.c.  Return address = 0xf89bb9eb

stack dump does not make much sense.
maybe you got a kernel stack overflow?
that would be expected for xfs on drbd on maybe some other layers.
I don't recall whether you can adjust that in 2.4 kernels at all.

base on unverified assumptions which may be grossly misguided,
I'm not so sure whether xfs with kernel 2.4 is a good idea.

: Lars Ellenberg                                  Tel +43-1-8178292-0  :
: LINBIT Information Technologies GmbH            Fax +43-1-8178292-82 :
: Schoenbrunner Str. 244, A-1120 Vienna/Europe   http://www.linbit.com :
please use the "List-Reply" function of your email client.

More information about the drbd-user mailing list