From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id q8JHcgNs224420 for ; Wed, 19 Sep 2012 12:38:42 -0500 Received: from mail.sandeen.net (sandeen.net [63.231.237.45]) by cuda.sgi.com with ESMTP id f2PIL6dEUXNI9Ug1 for ; Wed, 19 Sep 2012 10:39:53 -0700 (PDT) Message-ID: <505A0369.3020708@sandeen.net> Date: Wed, 19 Sep 2012 12:39:53 -0500 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: XFS corruption with rsync References: <20120919155748.620e9230@harpe.intellique.com> In-Reply-To: <20120919155748.620e9230@harpe.intellique.com> 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: Emmanuel Florac Cc: xfs@oss.sgi.com On 9/19/12 8:57 AM, Emmanuel Florac wrote: > > I'"ve seen this error showing up on the list previously: while > rsync'ing a large volume (66 TB copied to a 114 TB filesystem), I've got > this error showing up: I think you trimmed some relevant lines before these, what actual error did it hit, there's probably a file & line number? > Pid: 2069, comm: rsync Not tainted 3.2.28-storiq64-opteron #1 > Call Trace: > [] ? xfs_alloc_fixup_trees+0x22f/0x370 > [] ? xfs_btree_get_rec+0x53/0x90 > [] ? xfs_alloc_ag_vextent_near+0x83e/0xbe0 > [] ? xfs_alloc_fix_freelist+0x3cb/0x460 > [] ? xfs_alloc_ag_vextent+0xc5/0xf0 > [] ? xfs_alloc_vextent+0x3aa/0x5f0 > [] ? xfs_trans_read_buf+0x22a/0x420 > [] ? xfs_ialloc_ag_alloc+0x3c7/0x4d0 > [] ? xfs_dialloc+0xcb/0x870 > [] ? up+0xd/0x40 > [] ? xfs_ialloc+0x75/0x760 > [] ? kmem_zone_alloc+0x66/0xe0 > [] ? xfs_dir_ialloc+0x93/0x330 > [] ? xfs_trans_reserve+0x9d/0x210 > [] ? xfs_create+0x455/0x670 > [] ? xfs_vn_mknod+0xa6/0x1b0 > [] ? vfs_create+0x89/0xc0 > [] ? do_last+0x550/0x750 > [] ? path_openat+0xdb/0x3d0 > [] ? do_sync_write+0xc7/0x100 > [] ? handle_mm_fault+0x226/0x270 > [] ? do_filp_open+0x4d/0xc0 > [] ? alloc_fd+0x43/0x130 > [] ? do_sys_open+0x105/0x1e0 > [] ? system_call_fastpath+0x16/0x1b > > > Rsync logs says that "structure needs cleaning". After running > xfs_repair, there's a few files making reference to a free block. Including the xfs_repair output would be helpful too. > This machine has had serious filesystem failure previously, but the > RAID array and filesystem have been rebuild from the ground up, so it > should be OK; however I'd like to be really sure there's no hidden > hardware glitch waiting to bite us again... -Eric _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs