All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: jfs-discussion@lists.sourceforge.net,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ag@m-cam.com
Subject: Re: [Jfs-discussion] jfs mount causes oops on sparc64
Date: Sat, 2 Jul 2005 21:45:40 -0400	[thread overview]
Message-ID: <a728f9f905070218459cd140@mail.gmail.com> (raw)
In-Reply-To: <1120345779.9901.6.camel@kleikamp.austin.ibm.com>

On 7/2/05, Dave Kleikamp <shaggy@austin.ibm.com> wrote:
> On Fri, 2005-07-01 at 14:13 -0400, Alex Deucher wrote:
> > I have a 6.9 TB jfs LVM volume on a sparc64 debian box, however mount
> > seems to cause an oops when I attempt to mount the volume:
> >
> > jfs_mount: diMount(ipaimap) failed w/rc = -5
> > data_access_exception: SFSR[0000000000801009] SFAR[000000000043f770], going.
> 
> > kernel is 2.6.12rc3 on debian sparc.  Any ideas?
> 
> JFS has never worked on architectures with a page size greater than 4K
> until (would you believe?) 2.6.12-rc4.  I bet if you would try a more
> recent kernel, you would no longer see this problem.
> 
> In case you would continue to see problems with a newer kernel, I'd like
> to know.  I'll be on vacation until July 13, so my email access will be
> sporadic.
> 

I too will be on vacation until July 17th, but thanks for the heads
up!  We should probably upgrade that box to the latest 2.6.12 kernel
anyway.

Thanks,

Alex

> Thanks,
> Shaggy
> --
> David Kleikamp
> IBM Linux Technology Center
> 
>

      reply	other threads:[~2005-07-03  1:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 18:13 jfs mount causes oops on sparc64 Alex Deucher
2005-07-01 18:42 ` Luigi Genoni
2005-07-01 22:04   ` Alex Deucher
2005-07-02 23:09 ` [Jfs-discussion] " Dave Kleikamp
2005-07-03  1:45   ` Alex Deucher [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=a728f9f905070218459cd140@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=ag@m-cam.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@austin.ibm.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 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.