From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Nathan Scott <nathans@sgi.com>
Cc: Chris Wedgwood <cw@f00f.org>, David Greaves <david@dgreaves.com>,
Kasper Sandberg <lkml@metanurb.dk>,
Torsten Landschoff <torsten@debian.org>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com, ml@magog.se,
radsaq@gmail.com
Subject: Re: FAQ updated (was Re: XFS breakage...)
Date: Thu, 20 Jul 2006 19:10:46 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0607201910010.20652@p34.internal.lan> (raw)
In-Reply-To: <20060721090015.G1990742@wobbly.melbourne.sgi.com>
Nathan,
Running xfs_repair multiple times (after following the FAQ for the
write core.mode 0 fix), I get this:
- agno = 3
- agno = 4
- agno = 5
- agno = 6
entry ".." at block 0 offset 1352 in directory inode 3221227534 references
free inode 2112
clearing inode number in entry at offset 1352...
no .. entry for directory 3221227534
- agno = 7
- agno = 8
- agno = 9
disconnected inode 2684386082, moving to lost+found
disconnected inode 2684386083, moving to lost+found
disconnected inode 2684386084, moving to lost+found
disconnected inode 2684386085, moving to lost+found
disconnected inode 2684386086, moving to lost+found
disconnected inode 2684386087, moving to lost+found
disconnected inode 2684386088, moving to lost+found
disconnected inode 2684386089, moving to lost+found
disconnected inode 2684386090, moving to lost+found
disconnected inode 2684386091, moving to lost+found
disconnected inode 2684386092, moving to lost+found
disconnected inode 2684386093, moving to lost+found
disconnected inode 2684386094, moving to lost+found
disconnected inode 2684386095, moving to lost+found
disconnected inode 2684386096, moving to lost+found
disconnected inode 2684386097, moving to lost+found
disconnected inode 2684386098, moving to lost+found
disconnected inode 2684386099, moving to lost+found
disconnected inode 2684386100, moving to lost+found
disconnected inode 2684386101, moving to lost+found
disconnected inode 2684386102, moving to lost+found
disconnected inode 2684386103, moving to lost+found
disconnected inode 2684386104, moving to lost+found
disconnected inode 2684386105, moving to lost+found
disconnected inode 2684386106, moving to lost+found
disconnected inode 2684386107, moving to lost+found
disconnected inode 2684386108, moving to lost+found
disconnected inode 2684386109, moving to lost+found
disconnected inode 2684386110, moving to lost+found
disconnected inode 2684386111, moving to lost+found
disconnected inode 2684386112, moving to lost+found
disconnected inode 2684386113, moving to lost+found
disconnected inode 2684386114, moving to lost+found
disconnected inode 2684386115, moving to lost+found
disconnected inode 2684386116, moving to lost+found
disconnected inode 2684386117, moving to lost+found
disconnected inode 2684386118, moving to lost+found
disconnected inode 2684386119, moving to lost+found
disconnected inode 2684386120, moving to lost+found
disconnected inode 2684386121, moving to lost+found
disconnected inode 2684386122, moving to lost+found
disconnected inode 2684386123, moving to lost+found
disconnected inode 2684386124, moving to lost+found
disconnected inode 2684386125, moving to lost+found
disconnected inode 2684386126, moving to lost+found
disconnected inode 2684386127, moving to lost+found
disconnected inode 2684386128, moving to lost+found
disconnected inode 2684386129, moving to lost+found
disconnected inode 2684386130, moving to lost+found
disconnected inode 2684386131, moving to lost+found
disconnected inode 2684386132, moving to lost+found
disconnected inode 2684386133, moving to lost+found
disconnected inode 2684386134, moving to lost+found
disconnected inode 2684386135, moving to lost+found
disconnected inode 2684386136, moving to lost+found
disconnected inode 2684386137, moving to lost+found
disconnected inode 2684386138, moving to lost+found
disconnected inode 2684386139, moving to lost+found
disconnected inode 2684386140, moving to lost+found
disconnected inode 2684386141, moving to lost+found
disconnected inode 2684386142, moving to lost+found
disconnected inode 2684386143, moving to lost+found
disconnected inode 2684386144, moving to lost+found
disconnected inode 2684386145, moving to lost+found
disconnected inode 2684386146, moving to lost+found
disconnected inode 2684386147, moving to lost+found
disconnected inode 2684386148, moving to lost+found
disconnected inode 2684386149, moving to lost+found
disconnected inode 2684386150, moving to lost+found
disconnected inode 2684386151, moving to lost+found
disconnected inode 2684386152, moving to lost+found
disconnected inode 2684386153, moving to lost+found
disconnected inode 2684386154, moving to lost+found
disconnected inode 2684386155, moving to lost+found
disconnected inode 2684386156, moving to lost+found
disconnected inode 2684386157, moving to lost+found
disconnected inode 2684386158, moving to lost+found
disconnected inode 2684386159, moving to lost+found
disconnected inode 2684386160, moving to lost+found
disconnected inode 2684386161, moving to lost+found
disconnected inode 2684386162, moving to lost+found
disconnected inode 2684386163, moving to lost+found
disconnected inode 2684386164, moving to lost+found
disconnected inode 2684386165, moving to lost+found
disconnected inode 2684653605, moving to lost+found
disconnected dir inode 3221227534, moving to lost+found
Phase 7 - verify and correct link counts...
resetting inode 3221227534 nlinks from 3 to 2
done
p34:~#
I can run this over and over, and the result is the same?
On Fri, 21 Jul 2006, Nathan Scott wrote:
> On Thu, Jul 20, 2006 at 06:55:51PM -0400, Justin Piszcz wrote:
>> Phase 6 - check inode connectivity...
>> - traversing filesystem starting at / ...
>> free block 16777216 for directory inode 2684356622 bad nused
>> free block 16777216 for directory inode 2147485710 bad nused
>> - traversal finished ...
>> ...
>> I applied the "one line fix" - I should be ok now?
>
> You have two corrupt directory inodes (caused by this bug, that
> is exactly the signature I'd expect - it was a nused field that
> was affected by the dodgey endian change). The two inodes need
> to be fixed - consult the FAQ for details.
>
> Once fixed, and with a patched kernel, you're set.
>
> cheers.
>
> --
> Nathan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2006-07-20 23:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 22:29 XFS breakage in 2.6.18-rc1 Torsten Landschoff
2006-07-18 22:57 ` Nathan Scott
2006-07-19 8:08 ` Alistair John Strachan
2006-07-19 22:56 ` Nathan Scott
2006-07-20 10:29 ` Kasper Sandberg
2006-07-19 10:21 ` Kasper Sandberg
2006-07-19 12:43 ` Alistair John Strachan
2006-07-19 15:25 ` Kasper Sandberg
2006-07-19 22:59 ` Nathan Scott
2006-07-20 7:13 ` FAQ updated (was Re: XFS breakage...) Nathan Scott
2006-07-20 12:42 ` Hans-Peter Jansen
2006-07-20 13:28 ` David Greaves
2006-07-20 16:11 ` Chris Wedgwood
2006-07-20 22:14 ` Nathan Scott
2006-07-20 22:18 ` Justin Piszcz
2006-07-20 22:24 ` Nathan Scott
2006-07-20 22:43 ` Justin Piszcz
2006-07-20 22:52 ` Nathan Scott
2006-07-20 22:55 ` Justin Piszcz
2006-07-20 22:57 ` Justin Piszcz
2006-07-20 23:00 ` Nathan Scott
2006-07-20 23:10 ` Justin Piszcz [this message]
2006-07-20 23:12 ` Chris Wedgwood
2006-07-20 23:15 ` Justin Piszcz
2006-07-20 23:19 ` Nathan Scott
2006-07-20 15:13 ` Kevin Radloff
2006-07-20 16:51 ` Alistair John Strachan
2006-07-31 16:25 ` Jan Kasprzak
2006-07-31 16:38 ` Justin Piszcz
2006-08-02 4:32 ` Nathan Scott
2006-07-19 21:14 ` XFS breakage in 2.6.18-rc1 Torsten Landschoff
2006-07-19 23:09 ` Nathan Scott
2006-07-22 16:27 ` Christian Kujau
2006-07-23 23:01 ` Nathan Scott
2006-07-28 17:01 ` Christian Kujau
2006-07-28 21:48 ` Nathan Scott
2006-07-29 20:22 ` Ralf Hildebrandt
2006-07-29 22:28 ` David Chatterton
2006-07-18 23:06 ` Kevin Radloff
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=Pine.LNX.4.64.0607201910010.20652@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=cw@f00f.org \
--cc=david@dgreaves.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=ml@magog.se \
--cc=nathans@sgi.com \
--cc=radsaq@gmail.com \
--cc=torsten@debian.org \
--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
all inboxes | Powered by JetHome®