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 o2JKZ13F228073 for ; Fri, 19 Mar 2010 15:35:01 -0500 Received: from mail.sandeen.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 9B9F11448EC5 for ; Fri, 19 Mar 2010 13:36:39 -0700 (PDT) Received: from mail.sandeen.net (64-131-60-146.usfamily.net [64.131.60.146]) by cuda.sgi.com with ESMTP id dL3BKGqhYAjDs0qa for ; Fri, 19 Mar 2010 13:36:39 -0700 (PDT) Message-ID: <4BA3E055.2060100@sandeen.net> Date: Fri, 19 Mar 2010 15:36:37 -0500 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: xfs_repair deletes file References: In-Reply-To: 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: "Agarwal, Amit" Cc: "xfs@oss.sgi.com" Agarwal, Amit wrote: > Hi > > I need some help related to xfs repair. > > xfs_repair is deleting files which are more than ~10G from the real time partition. This is happening quite frequently. > > xfs_repair version 3.0.0 > Linux -> 2.6.18.8 might be best to retest on a recent kernel, as this looks like something went wrong at runtime. Do you have a testcase to recreate the situation? -Eric > Following is the output of xfs_repair > > Phase 1 - find and verify superblock... > Phase 2 - using internal log > - zero log... > - scan filesystem freespace and inode maps... > - found root inode chunk > Phase 3 - for each AG... > - scan and clear agi unlinked lists... > - process known inodes and perform inode discovery... > - agno = 0 > - agno = 1 > data fork in rt inode 16779171 claims used rt block 16538 > bad data fork in inode 16779171 > cleared inode 16779171 > data fork in rt inode 16779185 claims used rt block 24441 > bad data fork in inode 16779185 > cleared inode 16779185 > - agno = 2 > - agno = 3 > - process newly discovered inodes... > Phase 4 - check for duplicate blocks... > - setting up duplicate extent list... > - check for inodes claiming duplicate blocks... > - agno = 0 > - agno = 1 > entry "es33554469.tsp" at block 0 offset 4040 in directory inode 16777344 references free inode 16779171 > clearing inode number in entry at offset 4040... > entry "es33554472.tsp" at block 1 offset 432 in directory inode 16777344 references free inode 16779185 > clearing inode number in entry at offset 432... > - agno = 2 > - agno = 3 > Phase 5 - rebuild AG headers and trees... > - generate realtime summary info and bitmap... > - reset superblock... > Phase 6 - check inode connectivity... > - resetting contents of realtime bitmap and summary inodes > - traversing filesystem ... > bad hash table for directory inode 16777344 (no data entry): rebuilding > rebuilding directory inode 16777344 > - traversal finished ... > - moving disconnected inodes to lost+found ... > Phase 7 - verify and correct link counts... > done > > Thanks for your time > > Amit Agarwal > > > _______________________________________________ > 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