public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartosz Cisek <bartosz.cisek@nasza-klasa.pl>
To: Christoph Hellwig <hch@infradead.org>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>, xfs@oss.sgi.com
Subject: Re: xfs_repair segfaut in stage 6
Date: Wed, 14 Sep 2011 11:38:44 +0200	[thread overview]
Message-ID: <4E707624.9030703@nasza-klasa.pl> (raw)
In-Reply-To: <20110912161215.GA17798@infradead.org>

W dniu 12.09.2011 18:12, Christoph Hellwig pisze:
> I've repaired the image fine using xfs_repair from the Debian testing
> xfsprogs 3.1.5+nmu1 package.  It found two invalid blocks in a
> directory, which look like the result from the hardware error you saw.
> 
> You should be able to just rebuild the current xfsprogs (from
> testing/unstable or git) on Lenny and get the same result.

I've build xfs_repair from git on lenny and got segfault before my first
email to this list (please refer to first email in this thread) :)

What else I can do to find what differ our two cases?


hd-slave5 ~/devel/xfsprogs/repair # LC_ALL=en_EN ./xfs_repair -v
/dev/cciss/c0d5p1
Phase 1 - find and verify superblock...
        - block cache size set to 3446312 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 2 tail block 2
        - 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
xfs_repair: read failed: Input/output error
can't read block 0 for directory inode 146453
no . entry for directory 146453
no .. entry for directory 146453
        - 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 = 2
        - agno = 3
        - agno = 1
xfs_repair: read failed: Input/output error
can't read block 0 for directory inode 146453
no . entry for directory 146453
no .. entry for directory 146453
Phase 5 - rebuild AG headers and trees...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
entry "subdir49" in dir ino 437 doesn't have a .. entry, will set it in
ino 146453.
xfs_repair: read failed: Input/output error
Naruszenie ochrony pamięci (segfault)
hd-slave5 ~/devel/xfsprogs/repair # LC_ALL=en_EN ./xfs_repair -V
xfs_repair version 3.1.5

-- 
Bartosz Cisek
Admin

email: bartosz.cisek@nasza-klasa.pl
tel: +48 519 300 122

Nasza Klasa Sp. z o.o.,
ul. Gen. J. Bema 2, 50-265 Wrocław

Sąd Rejonowy dla Wrocławia - Fabrycznej we Wrocławiu,
VI Wydział Gospodarczy Krajowego Rejestru Sądowego,
nr KRS:0000289629, NIP:898-21-22-104 REGON:020586020,
Kapitał zakładowy: 67 850,00 PLN

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2011-09-14  9:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09  8:43 xfs_repair segfaut in stage 6 Bartosz Cisek
2011-09-09 12:01 ` Michael Monnerie
2011-09-09 15:06   ` Bartosz Cisek
2011-09-12 15:42     ` Bartosz Cisek
2011-09-12 15:58       ` Christoph Hellwig
2011-09-12 16:12     ` Christoph Hellwig
2011-09-14  9:38       ` Bartosz Cisek [this message]
2011-09-14 14:24         ` Christoph Hellwig
2011-09-14 14:57           ` Eric Sandeen
2011-09-14 15:10             ` Bartosz Cisek
2011-09-14 15:23               ` Eric Sandeen
2011-09-14 14:59           ` Bartosz Cisek
2011-09-14 15:38             ` Christoph Hellwig
2011-09-14 16:05               ` Bartosz Cisek
2011-09-20 20:25               ` Alex Elder
2011-09-20 20:28                 ` Christoph Hellwig
2011-09-09 12:38 ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E707624.9030703@nasza-klasa.pl \
    --to=bartosz.cisek@nasza-klasa.pl \
    --cc=hch@infradead.org \
    --cc=michael.monnerie@is.it-management.at \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox