From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: jfs-discussion@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ag@m-cam.com
Subject: Re: [Jfs-discussion] fsck.jfs segfaults on x86_64
Date: Fri, 10 Jun 2005 11:16:30 -0500 [thread overview]
Message-ID: <1118420190.21406.4.camel@localhost> (raw)
In-Reply-To: <a728f9f905061009097081c0a6@mail.gmail.com>
On Fri, 2005-06-10 at 12:09 -0400, Alex Deucher wrote:
> 1.1.8 segfaulted as well.
Hmm. This bothers me.
> running fsck.jfs --omit_journal_replay did the trick! thanks,
Well, at least it got you going again. :^)
Thanks,
Shaggy
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2005-06-10 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 14:00 fsck.jfs segfaults on x86_64 Alex Deucher
2005-06-10 14:14 ` [Jfs-discussion] " Dave Kleikamp
2005-06-10 14:21 ` Alex Deucher
2005-06-10 16:09 ` Alex Deucher
2005-06-10 16:16 ` Dave Kleikamp [this message]
2005-06-10 16:22 ` Alex Deucher
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=1118420190.21406.4.camel@localhost \
--to=shaggy@austin.ibm.com \
--cc=ag@m-cam.com \
--cc=alexdeucher@gmail.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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