From: Eric Sandeen <sandeen@sandeen.net>
To: Jan Yves Brueckner <jyb@gmx.com>
Cc: xfs@oss.sgi.com
Subject: Re: Aw: Re: xfs_repair segfaulting in phase 3
Date: Fri, 25 Oct 2013 10:12:46 -0500 [thread overview]
Message-ID: <526A8A6E.4050402@sandeen.net> (raw)
In-Reply-To: <trinity-561a8e56-e327-4695-b591-ab534badbca2-1382700222681@3capp-gmx-bs25>
On 10/25/13 6:23 AM, Jan Yves Brueckner wrote:
> Thanks a lot for taking care,
>
> I just teted with 3.2 alpha1 and had these results:
>
> corrupt block 21 in directory inode 39869938
> will junk block
> xfs_dir3_data_read_verify: XFS_CORRUPTION_ERROR
> corrupt block 34 in directory inode 39869938
> will junk block
> xfs_dir3_data_read_verify: XFS_CORRUPTION_ERROR
> corrupt block 35 in directory inode 39869938
> will junk block
> xfs_dir3_data_read_verify: XFS_CORRUPTION_ERROR
> corrupt block 51 in directory inode 39869938
> will junk block
> xfs_da3_node_read_verify: XFS_CORRUPTION_ERROR
> Segmentation fault
>
>
> Should I go on with git latest?
Hm, trying to remember which "3 patches" I referred to. ;)
This one:
commit 44dae5e6804408b4123a916a2738b73e21d8c61e
Author: Eric Sandeen <sandeen@sandeen.net>
Date: Thu Sep 12 20:56:36 2013 +0000
xfs_repair: test for bad level in dir2 node
is indeed committed post 3.2.0-alpha1.
Let me try to remember what the other two were, and where
they're at.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-10-25 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 11:38 xfs_repair segfaulting in phase 3 Jan Yves Brueckner
2013-08-12 14:02 ` Eric Sandeen
2013-08-26 20:41 ` Eric Sandeen
2013-09-04 13:39 ` Eric Sandeen
2013-10-25 11:23 ` Aw: " Jan Yves Brueckner
2013-10-25 15:12 ` Eric Sandeen [this message]
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=526A8A6E.4050402@sandeen.net \
--to=sandeen@sandeen.net \
--cc=jyb@gmx.com \
--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