From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com ([209.132.183.28]:48066 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936166AbcJaL5q (ORCPT ); Mon, 31 Oct 2016 07:57:46 -0400 Date: Mon, 31 Oct 2016 07:57:43 -0400 From: Brian Foster Subject: Re: BUG: Metadata corruption detected at xfs_attr3_leaf_read_verify Message-ID: <20161031115743.GA57171@bfoster.bfoster> References: <5244720.RPRsZ88NJ0@libor-nb> <3822835.q6ryES8eE3@libor-nb> <20161024024024.GX14023@dastard> <3301912.kAxTXXYXM8@libor-nb> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3301912.kAxTXXYXM8@libor-nb> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Libor =?utf-8?B?S2xlcMOhxI0=?= Cc: Dave Chinner , linux-xfs@vger.kernel.org On Mon, Oct 31, 2016 at 09:54:00AM +0100, Libor Klepáč wrote: > Hello, > i have upgrade VM called vps1 in original email (the one on bottom of email) > to debian kernel 4.7.8-1~bpo8+1 and compiled xfsprogs 4.8.0. > > Here is output of xfs_repair -n and xfs_repair. Is it supposed to write if/ > what is being repaired, when i forgot -v option? > Yes, xfs_repair will write some things to the fs when -n is not provided (if that was your question?). > With regards, > Libor > > root@vps1:~# xfs_repair -n /dev/vgEOSVPS1Disk2/lvData > 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 (but don't clear) agi unlinked lists... > - process known inodes and perform inode discovery... > - agno = 0 > - agno = 1 > - 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 > - agno = 2 > - agno = 3 > No modify flag set, skipping phase 5 > Phase 6 - check inode connectivity... > - traversing filesystem ... > - traversal finished ... > - moving disconnected inodes to lost+found ... > Phase 7 - verify link counts... > No modify flag set, skipping filesystem flush and exiting. > Hmm, and it looks like all is well with the fs. Have you reproduced the original issue since updating the kernel as well? Brian > ----- > > root@vps1:~# xfs_repair /dev/vgEOSVPS1Disk2/lvData > 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 > - 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 > - agno = 2 > - agno = 3 > Phase 5 - rebuild AG headers and trees... > - reset superblock... > Phase 6 - check inode connectivity... > - resetting contents of realtime bitmap and summary inodes > - traversing filesystem ... > - traversal finished ... > - moving disconnected inodes to lost+found ... > Phase 7 - verify and correct link counts... > done > > -- > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html