All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yura Pakhuchiy <pakhuchiy@gmail.com>
To: Nathan Scott <nathans@sgi.com>
Cc: linux-xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, tibor@altlinux.ru,
	pakhuchiy@gmail.com
Subject: Re: XFS corruption on move from xscale to i686
Date: Wed, 13 Jul 2005 18:22:28 +0300	[thread overview]
Message-ID: <60868aed0507130822c2e9e97@mail.gmail.com> (raw)
In-Reply-To: <20050708042146.GA1679@frodo>

2005/7/8, Nathan Scott <nathans@sgi.com>:
> On Thu, Jul 07, 2005 at 08:15:52PM +0300, Yura Pakhuchiy wrote:
> > Hi,
> >
> > I'm creadted XFS volume on 2.6.10 linux xscale/iq31244 box, then I
> > copyied files on it and moved this hard drive to i686 machine. When I
> > mounted it on i686, I found no files on it. I runned xfs_check, here is
> > output:
> 
> Someone else was doing this awhile back, and also had issues.
> Their trouble seemed to be related to xscale gcc miscompiling
> parts of XFS - search the linux-xfs archives for details.

I found patch by Greg Ungreger to fix this problem, but why it's still
not in mainline? Or it's a gcc problem and should be fixed by gcc folks?
BTW, my kernel on xscale is compiled using gcc 3.4.3.

Thanks,
        Yura

  reply	other threads:[~2005-07-13 15:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 17:15 XFS corruption on move from xscale to i686 Yura Pakhuchiy
2005-07-08  4:21 ` Nathan Scott
2005-07-13 15:22   ` Yura Pakhuchiy [this message]
2005-07-14  1:20     ` Nathan Scott
2005-07-14 13:50       ` Yura Pakhuchiy
2005-07-14 13:50       ` Yura Pakhuchiy
2005-07-14 14:38         ` Christoph Hellwig
2005-07-14 14:45           ` Yura Pakhuchiy
2005-07-14 14:49             ` 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=60868aed0507130822c2e9e97@mail.gmail.com \
    --to=pakhuchiy@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=nathans@sgi.com \
    --cc=tibor@altlinux.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.