From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 8DC4C7CD7 for ; Wed, 6 Jul 2016 05:35:09 -0500 (CDT) Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by relay1.corp.sgi.com (Postfix) with ESMTP id 610208F8039 for ; Wed, 6 Jul 2016 03:35:06 -0700 (PDT) Received: from mail-io0-f181.google.com (mail-io0-f181.google.com [209.85.223.181]) by cuda.sgi.com with ESMTP id 3TwYIxxOcacqByXe (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Wed, 06 Jul 2016 03:35:00 -0700 (PDT) Received: by mail-io0-f181.google.com with SMTP id t74so196479757ioi.0 for ; Wed, 06 Jul 2016 03:35:00 -0700 (PDT) From: Kirubakaran Kaliannan References: 662a938320f87297adda5d0b81565c78@mail.gmail.com In-Reply-To: 662a938320f87297adda5d0b81565c78@mail.gmail.com MIME-Version: 1.0 Date: Wed, 6 Jul 2016 16:04:54 +0530 Message-ID: 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: multipart/mixed; boundary="===============9055548993424003117==" Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: xfs@oss.sgi.com --===============9055548993424003117== Content-Type: multipart/alternative; boundary=001a114c9d4c1a12a50536f51f89 --001a114c9d4c1a12a50536f51f89 Content-Type: text/plain; charset=UTF-8 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) 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 --001a114c9d4c1a12a50536f51f89 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

=C2=A0

Hi A= ll,

=C2=A0

Sending it on= ce again, in case we all missed this earlier mail,

=C2=A0

Any help is much appreciated.

<= p class=3D"MsoNormal">This bug hangs the moun= t with the following stack. Similar to (https://bugs.launchpad.net/ubuntu/+source/linux/= +bug/1382801)

=C2=A0

root@zios-vsa-00000253-vc-0:~#= cat /proc/26511/task/26511/stack

[<ffffffffc0776c69>] xfs_ail_push_all_sync+0xa9= /0xe0 [xfs]

= [<ffffffffc076c2e7>] xfs_log_quiesce+0x37/0x70 [xfs]

[<ffffffffc076c33a>] x= fs_log_unmount+0x1a/0x70 [xfs]

[<ffffffffc0760845>] xfs_mountfs+0x5e5/0x7b0 [xfs]=

[<ffffff= ffc0763fca>] xfs_fs_fill_super+0x2ca/0x360 [xfs]

[<ffffffff811eb220>] mount_bd= ev+0x1b0/0x1f0

[<ffffffffc0761c95>] xfs_fs_mount+0x15/0x20 [xfs]

[<ffffffff811ebb79>] m= ount_fs+0x39/0x1b0

[<ffffffff812070db>] vfs_kern_mount+0x6b/0x120

[<ffffffff8120a032>] = do_mount+0x222/0xca0

[<ffffffff8120adab>] SyS_mount+0x8b/0xe0

[<ffffffff817179cd>] sys= tem_call_fastpath+0x16/0x1b

[<ffffffffffffffff>] 0xffffffffffffffff

=C2=A0

=C2=A0

Is this a known issue ? otherwise h= ow to avoid the hang, a mount failure will help to force-repair the filesys= tem and remount.

=C2=A0

= Thanks

-kiru=

=C2=A0

From:<= span style=3D"font-size:10.0pt;font-family:"Tahoma","sans-se= rif""> Kirubakaran Kaliannan [mailto:kirubak@zadarastorage.com]
Sent: Wednesday, June= 29, 2016 11:25 AM
To: 'xf= s@oss.sgi.com'
Subject: xfs mount hung on a corrupted fil= esystem

=C2=A0

=C2=A0

Hi XFS-developers,

=C2=A0

We are running XFS on ubuntu kernel-3.18.19

=C2=A0

On a drive failure = connected to my server, the file-system experienced the corruption. Attache= d the corruption.out file which contains the information regarding the corr= uption.

=C2=A0

<= span style=3D"font-size:10.0pt;font-family:"Comic Sans MS";color:= black">Later when the file-system is unmounted and mounted back, the mount = hung with the following stack (attached the dmesg when mount is run)=

=C2=A0

-------= -----------

= [ 3611.093909]=C2=A0 [<ffffffff81710c85>] dump_stack+0x4e/0x7= 1

[ = 3611.093943]=C2=A0 [<ffffffffc07ff68e>] xfs_error_report+0x3e/0x40 [x= fs]

= [ 3611.093964]=C2=A0 [<ffffffffc07beccc>] ? xfs_free_extent+0x10c/0x1= 70 [xfs]

[ 3611.093984]=C2=A0 [<ffffffffc07bd45f>] xfs_free_ag_extent.con= stprop.13+0x20f/0x980 [xfs]

[ 3611.094012]=C2=A0 [<ffffffffc07be4cf>] ? x= fs_alloc_fix_freelist+0x4af/0x510 [xfs]

[ 3611.094070]=C2=A0 [<ffffffffc07be= ccc>] xfs_free_extent+0x10c/0x170 [xfs]

[ 3611.094120]=C2=A0 [<ffffffffc0= 827da5>] xlog_recover_process_efi+0x175/0x1b0 [xfs]

[ 3611.094180]=C2=A0 [= <ffffffffc0829ed4>] xlog_recover_process_efis.isra.27+0x64/0xb0 [xfs]=

[ 3= 611.094227]=C2=A0 [<ffffffffc082d181>] xlog_recover_finish+0x21/0xb0 = [xfs]

= [ 3611.094317]=C2=A0 [<ffffffffc0817769>] xfs_mountfs+0x509/0= x7b0 [xfs]

<= span style=3D"font-size:10.0pt;font-family:"Comic Sans MS";color:= black">[ 3611.094359]=C2=A0 [<ffffffffc081afca>] xfs_fs_fill_super+0x= 2ca/0x360 [xfs]

[ 3611.094369]=C2=A0 [<ffffffff811eb220>] mount_bdev+0x1b= 0/0x1f0

[ 3611.094406]=C2=A0 [<ffffffffc081ad00>] ? xfs_parseargs+0xbe0/0= xbe0 [xfs]

<= span style=3D"font-size:10.0pt;font-family:"Comic Sans MS";color:= black">[ 3611.094443]=C2=A0 [<ffffffffc0818c95>] xfs_fs_mount+0x15/0x= 20 [xfs]

[ 3611.094452]=C2=A0 [<ffffffff811ebb79>] mount_fs+0x39/0x1b0

[ 3611= .094460]=C2=A0 [<ffffffff81192fc5>] ? __alloc_percpu+0x15/0x20=

[ 3611.094= 472]=C2=A0 [<ffffffff812070db>] vfs_kern_mount+0x6b/0x120

<= p class=3D"MsoNormal" style=3D"text-autospace:none">[ 3611.094479]= =C2=A0 [<ffffffff8120a032>] do_mount+0x222/0xca0

[ 3611.094486]=C2=A0 [= <ffffffff8120adab>] SyS_mount+0x8b/0xe0

[ 3611.094495]=C2=A0 [<fffffff= f817179cd>] system_call_fastpath+0x16/0x1b

[ 3611.094512] XFS (dm-56): Faile= d to recover EFIs

[ 3611.095813] XFS (dm-56): log mount finish failed

-----------

=C2= =A0

= My initial analysis shows, exactly the issue is same as in (but expired)

https://bugs.launchpad.net/ubuntu/= +source/linux/+bug/1382801

=C2=A0

filesystem getting corrupted is the f= irst problem. But the mount hang instead of failing is making it difficult = to repair the filesystem.

=C2=A0

Can you please help progress on this issue ?

I have th= e metadump of the filesystem, and can provide any details required.<= /p>

=C2=A0

Thanks

-kiru

--001a114c9d4c1a12a50536f51f89-- --===============9055548993424003117== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs --===============9055548993424003117==--