From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: with ECARTIS (v1.0.0; list xfs); Mon, 17 Sep 2007 19:24:34 -0700 (PDT) Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id l8I2OLuw017322 for ; Mon, 17 Sep 2007 19:24:27 -0700 Date: Tue, 18 Sep 2007 12:27:57 +1000 Subject: Re: Bug Report From: "Barry Naujok" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 References: <170b1bd40709061005t787494b6lca283320cace6c31@mail.gmail.com> Message-ID: In-Reply-To: <170b1bd40709061005t787494b6lca283320cace6c31@mail.gmail.com> Content-Transfer-Encoding: 8bit Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com List-Id: xfs To: Mark Goodall , xfs@oss.sgi.com On Fri, 07 Sep 2007 03:05:29 +1000, Mark Goodall wrote: > Not sure what caused this bug, how much more information do you need? > > - 18:01:15: check for inodes claiming duplicate blocks - 198528 > of > 198528 inodes done > No modify flag set, skipping phase 5 > Phase 6 - check inode connectivity... > - traversing filesystem starting at / ... > corrupt dinode 25809974, extent total = 16, nblocks = 0. This is a bug. > Please report it to xfs@oss.sgi.com. > cache_node_purge: refcount was 1, not zero (node=0x8d65fd0) > couldn't map inode 25809974, err = 117 > entry "gobo_3.3-6_i386.deb" in shortform directory inode 1770978822 > points > to free inode 1770978825 > would junk entry "gobo_3.3-6_i386.deb" > - 18:01:48: traversing filesystem - 32 of 32 allocation groups > done > - traversal finished ... > - traversing all unattached subtrees ... > Segmentation fault (core dumped) > > OS: Ubuntu Linux mserve 2.6.20-16-386 #2 Fri Aug 31 00:51:58 UTC 2007 > i686 > GNU/Linux > fully patched from official repositories Latest xfsprogs 2.9.4 doesn't segfault anymore in Phase 6. The "corrupt dinode..." error is a symptom of running xfs_repair in -n mode where Phase 3 would have fixed the offending inode up: -n mode: bad attribute format 0 in inode 25809974, would reset value bad anextents 16 for inode 25809974, would reset to 0 repair mode: bad attribute format 0 in inode 25809974, resetting value correcting anextents for inode 25809974, was 16 - counted 0 Regards, Barry.