From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030226AbWGaQZt (ORCPT ); Mon, 31 Jul 2006 12:25:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030228AbWGaQZt (ORCPT ); Mon, 31 Jul 2006 12:25:49 -0400 Received: from tirith.ics.muni.cz ([147.251.4.36]:10409 "EHLO tirith.ics.muni.cz") by vger.kernel.org with ESMTP id S1030226AbWGaQZs (ORCPT ); Mon, 31 Jul 2006 12:25:48 -0400 Date: Mon, 31 Jul 2006 18:25:35 +0200 From: Jan Kasprzak To: Nathan Scott Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com Subject: Re: FAQ updated (was Re: XFS breakage...) Message-ID: <20060731162535.GA15555@fi.muni.cz> References: <20060718222941.GA3801@stargate.galaxy> <20060719085731.C1935136@wobbly.melbourne.sgi.com> <1153304468.3706.4.camel@localhost> <20060720171310.B1970528@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060720171310.B1970528@wobbly.melbourne.sgi.com> User-Agent: Mutt/1.4.1i X-Muni-Spam-TestIP: 147.251.48.3 X-Muni-Envelope-From: kas@fi.muni.cz X-Muni-Virus-Test: Clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Nathan Scott wrote: : I've captured the state of this issue here, with options and ways : to correct the problem: : http://oss.sgi.com/projects/xfs/faq.html#dir2 : : Hope this helps. I have been hit with this bug as well - I tried to clear the two corrupted directory inodes with xfs_db (as the FAQ entry says), then ran xfs_repair (lots of files ended up in lost+found), but apparently the volume is still not OK - when I tried to use it (this volume is a public FTP archive), I got the following traces: Jul 30 16:04:49 odysseus kernel: Filesystem "md5": XFS internal error xfs_da_do_buf(2) at line 2212 of file fs/xfs/xfs_da_btree.c. Caller 0xffffffff80324221 Jul 30 16:04:49 odysseus kernel: Jul 30 16:04:49 odysseus kernel: Call Trace: {xfs_corruption_error+228} Jul 30 16:04:49 odysseus kernel: {kmem_zone_alloc+86} {xfs_da_do_buf+1359} Jul 30 16:04:49 odysseus kernel: {xfs_da_read_buf+22} {xfs_da_buf_make+31} Jul 30 16:04:49 odysseus kernel: {xfs_da_read_buf+22} {xfs_da_node_lookup_int+112} Jul 30 16:04:49 odysseus kernel: {xfs_da_node_lookup_int+112} {xfs_dir2_node_lookup+70} Jul 30 16:04:50 odysseus kernel: {xfs_dir2_isleaf+25} {xfs_dir2_lookup+256} Jul 30 16:04:51 odysseus kernel: {xfs_dir_lookup_int+55} {xfs_lookup+79} Jul 30 16:04:51 odysseus kernel: {xfs_vn_lo7b35>{xfs_dir2_isleaf+25} {xfs_dir2_lookup+256} Jul 30 16:04:52 odysseus kernel: {xfs_dir_lookup_int+55} {xfs_lookup+79} Jul 30 16:04:53 odysseus kernel: {xfs_vn_lookup+48} {do_lookup+196} Jul 30 16:04:53 odysseus rpc.statd[3145]: Caught signal 15, un-registering and exiting. Jul 30 16:04:53 odysseus kernel: {__link_path_walk+2435} {link_path_walk+89} Jul 30 16:04:53 odysseus kernel: {__sched_text_start+290} {do_path_lookup+614} Jul 30 16:04:53 odysseus kernel: {getname+347} {__user_walk_fd+55} Jul 30 16:04:53 odysseus kernel: {vfs_lstat_fd+21} {__sched_text_start+290} Jul 30 16:04:53 odysseus kernel: {sys_newlstat+25} {vfs_write+283} Jul 30 16:04:53 odysseus kernel: {sys_write+69} {system_call+126} Jul 30 16:04:53 odysseus kernel: 0x0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 This is 2.6.17.7 dual x86_64 (Fedora Core 5). It has been unfortunately running 2.6.17.1 for some time. I will probably have to recreate the volume and restore its contents from backups. Or is there any better solution? Thanks, -Yenya -- | Jan "Yenya" Kasprzak | | GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E | | http://www.fi.muni.cz/~kas/ Journal: http://www.fi.muni.cz/~kas/blog/ | > I will never go to meetings again because I think face to face meetings < > are the biggest waste of time you can ever have. --Linus Torvalds <