From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.12.11.20060308/8.12.11/SuSE Linux 0.7) with ESMTP id mBVETKeb006882 for ; Wed, 31 Dec 2008 08:29:21 -0600 Received: from isp.becroft.co.nz (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 3DAFD55723 for ; Wed, 31 Dec 2008 06:29:19 -0800 (PST) Received: from isp.becroft.co.nz (isp.becroft.co.nz [202.89.33.33]) by cuda.sgi.com with ESMTP id OAGpnPrF6ZgV70Co for ; Wed, 31 Dec 2008 06:29:19 -0800 (PST) Received: from server.ak.quickcircuit.co.nz (gateway.quickcircuit.co.nz [210.55.214.217]) by isp.becroft.co.nz (8.12.11.20060308/8.12.9) with ESMTP id mBVE987w009973 for ; Thu, 1 Jan 2009 03:09:09 +1300 Subject: XFS internal error when NFS client accesses nonexistent inode From: Mario Becroft Date: Thu, 01 Jan 2009 03:09:08 +1300 Message-ID: <87zlicfncr.fsf@server.ak.quickcircuit.co.nz> MIME-Version: 1.0 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 Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: xfs@oss.sgi.com I hit a seemingly strange problem today when I xfsdump/restored some filesystems from one volume onto another. When I exported the new volumes, errors like the following started to occur: Dec 31 09:12:46 nfs1 kernel: nfsd: non-standard errno: -117 Bumping up the XFS debug level revealed the following (full details at the end): Dec 31 09:12:46 nfs1 kernel: Filesystem "dm-17": XFS internal error xfs_imap_to_bp at line 186 of file fs/xfs/xfs_inode.c. Caller 0xffffffff80374c48 xfs_check reported no error in the filesystem. After wasting quite a lot of time, I finally realised that this was probably caused by NFS clients accessing nonexistent file handles that they had open from when the filesystem was previously exported, prior to the dump/restore. Is my analysis correct? Is an internal error the expected behaviour in this case? And can this cause any harm? While I am writing, two things I wish XFS could do, and two more that would be jolly nice to have: 1. shrink filesystems 2. dump/restore preserving inode numbers 3. high-performance dump with multi-threaded reading to fully utilise disk throughput 4. on-line xfs_check/repair I wonder if anyone is working on those? Full log output follows: --8<---------------cut here---------------start------------->8--- Dec 31 09:12:46 nfs1 kernel: 00000000: f5 83 23 77 26 c5 70 43 bb bd 3d 44 c9 63 e2 b1 ..#w&.pC..=D.c.. Dec 31 09:12:46 nfs1 kernel: Filesystem "dm-17": XFS internal error xfs_imap_to_bp at line 186 of file fs/xfs/xfs_inode.c. Caller 0xffffffff80374c48 Dec 31 09:12:46 nfs1 kernel: Pid: 4969, comm: nfsd Not tainted 2.6.27.4 #3 Dec 31 09:12:46 nfs1 kernel: Dec 31 09:12:46 nfs1 kernel: Call Trace: Dec 31 09:12:46 nfs1 kernel: [] xfs_itobp+0xa0/0xe7 Dec 31 09:12:46 nfs1 kernel: [] xfs_imap_to_bp+0xd6/0xfc Dec 31 09:12:46 nfs1 kernel: [] xfs_itobp+0xa0/0xe7 Dec 31 09:12:46 nfs1 kernel: [] xfs_imap+0x6a/0x135 Dec 31 09:12:46 nfs1 kernel: [] xfs_itobp+0xa0/0xe7 Dec 31 09:12:46 nfs1 kernel: [] xfs_iread+0x79/0x1ed Dec 31 09:12:46 nfs1 kernel: [] xfs_iget_core+0x2ea/0x54d Dec 31 09:12:46 nfs1 kernel: [] xfs_iget+0xe2/0x18a Dec 31 09:12:46 nfs1 kernel: [] xfs_nfs_get_inode+0x39/0x88 Dec 31 09:12:46 nfs1 kernel: [] xfs_fs_fh_to_dentry+0x64/0x97 Dec 31 09:12:46 nfs1 kernel: [] exportfs_decode_fh+0x30/0x1dc [exportfs] Dec 31 09:12:46 nfs1 kernel: [] nfsd_acceptable+0x0/0xc7 [nfsd] Dec 31 09:12:46 nfs1 kernel: [] exp_find_key+0x96/0xa9 [nfsd] Dec 31 09:12:46 nfs1 kernel: [] place_entity+0x9e/0xc7 Dec 31 09:12:46 nfs1 kernel: [] enqueue_task_fair+0x17e/0x1a7 Dec 31 09:12:46 nfs1 kernel: [] exp_find+0x63/0x6f [nfsd] Dec 31 09:12:46 nfs1 kernel: [] fh_verify+0x278/0x546 [nfsd] Dec 31 09:12:46 nfs1 kernel: [] __wake_up_common+0x41/0x74 Dec 31 09:12:46 nfs1 kernel: [] nfsd_access+0x29/0xff [nfsd] Dec 31 09:12:46 nfs1 kernel: [] nfsd3_proc_access+0x99/0xa6 [nfsd] Dec 31 09:12:46 nfs1 kernel: [] nfsd_dispatch+0xde/0x1c2 [nfsd] Dec 31 09:12:46 nfs1 kernel: [] svc_process+0x408/0x6eb [sunrpc] Dec 31 09:12:46 nfs1 kernel: [] __down_read+0x12/0x8b Dec 31 09:12:46 nfs1 kernel: [] nfsd+0x1ae/0x27a [nfsd] Dec 31 09:12:46 nfs1 kernel: [] nfsd+0x0/0x27a [nfsd] Dec 31 09:12:46 nfs1 kernel: [] kthread+0x47/0x75 Dec 31 09:12:46 nfs1 kernel: [] child_rip+0xa/0x11 Dec 31 09:12:46 nfs1 kernel: [] kthread+0x0/0x75 Dec 31 09:12:46 nfs1 kernel: [] child_rip+0x0/0x11 Dec 31 09:12:46 nfs1 kernel: Dec 31 09:12:46 nfs1 kernel: nfsd: non-standard errno: -117 Dec 31 09:12:46 nfs1 kernel: 00000000: f5 83 23 77 26 c5 70 43 bb bd 3d 44 c9 63 e2 b1 ..#w&.pC..=D.c.. Dec 31 09:12:46 nfs1 kernel: Filesystem "dm-17": XFS internal error xfs_imap_to_bp at line 186 of file fs/xfs/xfs_inode.c. Caller 0xffffffff80374c48 Dec 31 09:12:46 nfs1 kernel: Pid: 4969, comm: nfsd Not tainted 2.6.27.4 #3 Dec 31 09:12:46 nfs1 kernel: Dec 31 09:12:46 nfs1 kernel: Call Trace: Dec 31 09:12:46 nfs1 kernel: [] xfs_itobp+0xa0/0xe7 Dec 31 09:12:46 nfs1 kernel: [] xfs_imap_to_bp+0xd6/0xfc Dec 31 09:12:46 nfs1 kernel: [] xfs_itobp+0xa0/0xe7 Dec 31 09:12:46 nfs1 kernel: [] xfs_imap+0x6a/0x135 Dec 31 09:12:46 nfs1 kernel: [] xfs_itobp+0xa0/0xe7 Dec 31 09:12:46 nfs1 kernel: [] xfs_iread+0x79/0x1ed Dec 31 09:12:46 nfs1 kernel: [] xfs_iget_core+0x2ea/0x54d Dec 31 09:12:46 nfs1 kernel: [] xfs_iget+0xe2/0x18a Dec 31 09:12:46 nfs1 kernel: [] xfs_nfs_get_inode+0x39/0x88 Dec 31 09:12:46 nfs1 kernel: [] xfs_fs_fh_to_dentry+0x64/0x97 Dec 31 09:12:46 nfs1 kernel: [] exportfs_decode_fh+0x30/0x1dc [exportfs] Dec 31 09:12:46 nfs1 kernel: [] nfsd_acceptable+0x0/0xc7 [nfsd] Dec 31 09:12:46 nfs1 kernel: [] exp_find_key+0x96/0xa9 [nfsd] Dec 31 09:12:46 nfs1 kernel: [] place_entity+0x9e/0xc7 Dec 31 09:12:46 nfs1 kernel: [] enqueue_task_fair+0x17e/0x1a7 Dec 31 09:12:46 nfs1 kernel: [] exp_find+0x63/0x6f [nfsd] Dec 31 09:12:46 nfs1 kernel: [] fh_verify+0x278/0x546 [nfsd] Dec 31 09:12:46 nfs1 kernel: [] __wake_up_common+0x41/0x74 Dec 31 09:12:46 nfs1 kernel: [] nfsd_access+0x29/0xff [nfsd] Dec 31 09:12:46 nfs1 kernel: [] nfsd3_proc_access+0x99/0xa6 [nfsd] Dec 31 09:12:46 nfs1 kernel: [] nfsd_dispatch+0xde/0x1c2 [nfsd] Dec 31 09:12:46 nfs1 kernel: [] svc_process+0x408/0x6eb [sunrpc] Dec 31 09:12:46 nfs1 kernel: [] __down_read+0x12/0x8b Dec 31 09:12:46 nfs1 kernel: [] nfsd+0x1ae/0x27a [nfsd] Dec 31 09:12:46 nfs1 kernel: [] nfsd+0x0/0x27a [nfsd] Dec 31 09:12:46 nfs1 kernel: [] kthread+0x47/0x75 Dec 31 09:12:46 nfs1 kernel: [] child_rip+0xa/0x11 Dec 31 09:12:46 nfs1 kernel: [] kthread+0x0/0x75 Dec 31 09:12:46 nfs1 kernel: [] child_rip+0x0/0x11 Dec 31 09:12:46 nfs1 kernel: Dec 31 09:12:46 nfs1 kernel: nfsd: non-standard errno: -117 --8<---------------cut here---------------end--------------->8--- -- Mario Becroft _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs