From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Nathan Scott <nathans@sgi.com>
Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org,
debian-user@lists.debian.org
Subject: Re: xfs_db -c frag -r /dev/hda1 - Segmentation fault
Date: Sun, 23 Oct 2005 19:40:19 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0510231940140.5116@p34> (raw)
In-Reply-To: <20051024085451.C5863161@wobbly.melbourne.sgi.com>
Thanks, I will give this a try.
On Mon, 24 Oct 2005, Nathan Scott wrote:
> On Sun, Oct 23, 2005 at 07:39:34AM -0400, Justin Piszcz wrote:
>> p34:~# xfs_db -c frag -r /dev/hda1
>> Segmentation fault
>> p34:~# xfs_db -c frag -r /dev/hde1
>> Segmentation fault
>> p34:~# xfs_db -c frag -r /dev/hdk1
>> Segmentation fault
>> p34:~#
>>
>> Debian Etch, 2.6.13.4, stopped working a while ago, either before newer
>> debian packages or a newer kernel, does anyone who uses Debian+XFS have
>> this problem as well?
>
> I see it too - this looks like an endian issue in xfs_db, this patch
> should fix it (Works For Me).
>
> cheers.
>
> --
> Nathan
>
>
> Index: xfsprogs/db/frag.c
> ===================================================================
> --- xfsprogs.orig/db/frag.c
> +++ xfsprogs/db/frag.c
> @@ -294,7 +294,7 @@ process_exinode(
> xfs_bmbt_rec_32_t *rp;
>
> rp = (xfs_bmbt_rec_32_t *)XFS_DFORK_PTR(dip, whichfork);
> - process_bmbt_reclist(rp, XFS_DFORK_NEXTENTS(dip, whichfork), extmapp);
> + process_bmbt_reclist(rp, XFS_DFORK_NEXTENTS_HOST(dip, whichfork), extmapp);
> }
>
> static void
> @@ -305,7 +305,7 @@ process_fork(
> extmap_t *extmap;
> int nex;
>
> - nex = XFS_DFORK_NEXTENTS(dip, whichfork);
> + nex = XFS_DFORK_NEXTENTS_HOST(dip, whichfork);
> if (!nex)
> return;
> extmap = extmap_alloc(nex);
>
>
prev parent reply other threads:[~2005-10-23 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4080C826.F4C53CD@dmministries.org>
2005-10-23 11:39 ` Justin Piszcz
2005-10-23 22:54 ` Nathan Scott
2005-10-23 23:40 ` Justin Piszcz [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=Pine.LNX.4.64.0510231940140.5116@p34 \
--to=jpiszcz@lucidpixels.com \
--cc=debian-user@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@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®