From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay2.corp.sgi.com [137.38.102.29]) by oss.sgi.com (Postfix) with ESMTP id 2FDF97CEB for ; Wed, 6 Jul 2016 23:57:25 -0500 (CDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay2.corp.sgi.com (Postfix) with ESMTP id E835530407B for ; Wed, 6 Jul 2016 21:57:21 -0700 (PDT) Received: from mail-it0-f46.google.com (mail-it0-f46.google.com [209.85.214.46]) by cuda.sgi.com with ESMTP id rDDER4iNwF9BffRs (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 06 Jul 2016 21:57:18 -0700 (PDT) Received: by mail-it0-f46.google.com with SMTP id g4so83089939ith.1 for ; Wed, 06 Jul 2016 21:57:18 -0700 (PDT) From: Kirubakaran Kaliannan References: <20160706113534.GA24552@bfoster.bfoster> In-Reply-To: <20160706113534.GA24552@bfoster.bfoster> MIME-Version: 1.0 Date: Thu, 7 Jul 2016 10:27:11 +0530 Message-ID: <2f90f396734caeed89cc599acb0aa42d@mail.gmail.com> Subject: RE: xfs mount hung on a corrupted filesystem List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Brian Foster Cc: xfs@oss.sgi.com Thanks Brain, I will check whether we can move up to v4.3. In the mean time, I want to automate this situation. Run xfsrepair -L before trying to mount, By checking whether the file system is corrupted without mounting it. Not sure whether we can differentiate a mount which is going to hang and which is not. ? Thanks, -kiru -----Original Message----- From: Brian Foster [mailto:bfoster@redhat.com] Sent: Wednesday, July 06, 2016 5:06 PM To: Kirubakaran Kaliannan Cc: xfs@oss.sgi.com Subject: Re: xfs mount hung on a corrupted filesystem On Wed, Jul 06, 2016 at 04:04:54PM +0530, Kirubakaran Kaliannan wrote: > Hi All, > > > > Sending it once again, in case we all missed this earlier mail, > > > > Any help is much appreciated. > > This bug hangs the mount with the following stack. Similar to ( > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382801) > It's hard to say for sure, but this could be due to historical EFI/EFD reference counting brokenness. This was known to lead to unmount hangs on mount failure, shutdown situations, etc. This code was totally reworked in v4.3.0 and I don't think includes any fixes that are easily backportable to such an old kernel. You should be able to avoid this by repairing the fs such that it mounts, fwiw. Brian > > > root@zios-vsa-00000253-vc-0:~# cat /proc/26511/task/26511/stack > > [] xfs_ail_push_all_sync+0xa9/0xe0 [xfs] > > [] xfs_log_quiesce+0x37/0x70 [xfs] > > [] xfs_log_unmount+0x1a/0x70 [xfs] > > [] xfs_mountfs+0x5e5/0x7b0 [xfs] > > [] xfs_fs_fill_super+0x2ca/0x360 [xfs] > > [] mount_bdev+0x1b0/0x1f0 > > [] xfs_fs_mount+0x15/0x20 [xfs] > > [] mount_fs+0x39/0x1b0 > > [] vfs_kern_mount+0x6b/0x120 > > [] do_mount+0x222/0xca0 > > [] SyS_mount+0x8b/0xe0 > > [] system_call_fastpath+0x16/0x1b > > [] 0xffffffffffffffff > > > > > > Is this a known issue ? otherwise how to avoid the hang, a mount > failure will help to force-repair the filesystem and remount. > > > > Thanks > > -kiru > > > > *From:* Kirubakaran Kaliannan [mailto:kirubak@zadarastorage.com] > *Sent:* Wednesday, June 29, 2016 11:25 AM > *To:* 'xfs@oss.sgi.com' > *Subject:* xfs mount hung on a corrupted filesystem > > > > > > Hi XFS-developers, > > > > We are running XFS on ubuntu kernel-3.18.19 > > > > On a drive failure connected to my server, the file-system experienced > the corruption. Attached the corruption.out file which contains the > information regarding the corruption. > > > > Later when the file-system is unmounted and mounted back, the mount > hung with the following stack (attached the dmesg when mount is run) > > > > ------------------ > > [ 3611.093909] [] dump_stack+0x4e/0x71 > > [ 3611.093943] [] xfs_error_report+0x3e/0x40 [xfs] > > [ 3611.093964] [] ? xfs_free_extent+0x10c/0x170 > [xfs] > > [ 3611.093984] [] > xfs_free_ag_extent.constprop.13+0x20f/0x980 [xfs] > > [ 3611.094012] [] ? > xfs_alloc_fix_freelist+0x4af/0x510 > [xfs] > > [ 3611.094070] [] xfs_free_extent+0x10c/0x170 [xfs] > > [ 3611.094120] [] > xlog_recover_process_efi+0x175/0x1b0 > [xfs] > > [ 3611.094180] [] > xlog_recover_process_efis.isra.27+0x64/0xb0 [xfs] > > [ 3611.094227] [] xlog_recover_finish+0x21/0xb0 > [xfs] > > [ 3611.094271] [] xfs_log_mount_finish+0x34/0x50 > [xfs] > > [ 3611.094317] [] xfs_mountfs+0x509/0x7b0 [xfs] > > [ 3611.094359] [] xfs_fs_fill_super+0x2ca/0x360 > [xfs] > > [ 3611.094369] [] mount_bdev+0x1b0/0x1f0 > > [ 3611.094406] [] ? xfs_parseargs+0xbe0/0xbe0 [xfs] > > [ 3611.094443] [] xfs_fs_mount+0x15/0x20 [xfs] > > [ 3611.094452] [] mount_fs+0x39/0x1b0 > > [ 3611.094460] [] ? __alloc_percpu+0x15/0x20 > > [ 3611.094472] [] vfs_kern_mount+0x6b/0x120 > > [ 3611.094479] [] do_mount+0x222/0xca0 > > [ 3611.094486] [] SyS_mount+0x8b/0xe0 > > [ 3611.094495] [] system_call_fastpath+0x16/0x1b > > [ 3611.094512] XFS (dm-56): Failed to recover EFIs > > [ 3611.095813] XFS (dm-56): log mount finish failed > > ----------- > > > > My initial analysis shows, exactly the issue is same as in (but > expired) > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382801 > > > > filesystem getting corrupted is the first problem. But the mount hang > instead of failing is making it difficult to repair the filesystem. > > > > Can you please help progress on this issue ? > > I have the metadump of the filesystem, and can provide any details required. > > > > Thanks > > -kiru > _______________________________________________ > xfs mailing list > xfs@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs