[Top] [All Lists]

Re: help xfs filesystem crash

To: xfs@xxxxxxxxxxx
Subject: Re: help xfs filesystem crash
From: Joe Landman <joe.landman@xxxxxxxxx>
Date: Sat, 05 Jan 2013 10:48:04 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ZpI1PElSTfzWjyj8SbMp15G9DTeDplpFZ9gwn/fgo4s=; b=V2v6z6IxpVwn30j3NYHmLc8sJ6vooyd3YkZhwnJehUCkztvaDz9XRjjd4Pb0GPBcE4 MNZbENDB/A7TQ4zp0OEVqjiH4aV4Ndz7slOF/rM5Pe1p8Wo8b3FH7dlvpCK0Jk84rtUF v6IMU8e5eflldkWuQ3jHYQQb/V2kyh8+QhyQcJgw5yrar4/diTNyheb/DPv+/l7E7xlR NlBkwmg9B29AFq1ReM1xdmV3BMPK1vDR/7UBiYwlQVk2CtEbOhscpXlha+mczBovme+H 2/feu6rZFHqWH3gZfJzWvJrmPMNgyx1HV6ZihmIZlgMfMHK7RGLSB/U9I2is04fmkvmJ 9JEQ==
In-reply-to: <CADFMGuL2GtcXs_BZ-xhoqczs8B=orWqZSOMGLmpRCokdtcY8ww@xxxxxxxxxxxxxx>
References: <CADFMGuL2GtcXs_BZ-xhoqczs8B=orWqZSOMGLmpRCokdtcY8ww@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
On 01/05/2013 08:47 AM, 符永涛 wrote:
> Dear xfs experts,
> We're running glusterfs over top of xfs and recently we have
> encountered xfs filesystem crash two times on two different servers.
> Can you kindly help to give me some insight of how to debug this kind
> of failure?
> Bellow is xfs filesystem crash messages:
> server1:
> Dec 28 16:55:01 localhost kernel: XFS (dm-0): xfs_iunlink_remove:
> xfs_inotobp() returned error 22.
> Dec 28 16:55:01 localhost kernel: XFS (dm-0): xfs_inactive: xfs_ifree
> returned error 22
> Dec 28 16:55:01 localhost kernel: XFS (dm-0):
> xfs_do_force_shutdown(0x1) called from line 1184 of file
> fs/xfs/xfs_vnodeops.c. Return address = 0xffffffffa029f20a
> Dec 28 16:55:01 localhost kernel: XFS (dm-0): I/O Error Detected.
> Shutting down filesystem
> Dec 28 16:55:01 localhost kernel: XFS (dm-0): Please umount the
> filesystem and rectify the problem(s)
> Dec 28 16:55:20 localhost kernel: XFS (dm-0): xfs_log_force: error 5 returned.

xfs sitting atop dm here.  This looks like a dm issue, possibly the dm
LV going away, or going offline.  I'd start with tracing at the device
level upwards to the LV, see if this is still alive and well behaved

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