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 09:14:42 -0500 [thread overview]
Message-ID: <1118412882.7944.6.camel@localhost> (raw)
In-Reply-To: <a728f9f90506100700107976f0@mail.gmail.com>
On Fri, 2005-06-10 at 10:00 -0400, Alex Deucher wrote:
> We have a large lvm2 logical volume (6.91T) which contains a JFS
> filesystem. The volumes accessed via emulex FC HBAs connected to a
> nexsan SAN. There was a bug in the SAN firmware that caused the
> primary controller to lose sync with the other controller and go down.
> Normally when this happens we are able to reboot the SAN and the
> server and then run fsck on the volume, and everything is fine (on a
> side note, we have updated the SAN firmware to fix the sync problem).
> however, fsck now segfaults and the volume is dirty so it can't be
> mounted. lvdisplay and vgdisplay seem to work fine displaying the
> correct info. Does anyone know what may be causing the problem or how
> we can fix it? If possible I'd like to save the data on the volumes.
>
> #> time fsck.jfs /dev/vg00/lvol0
> fsck.jfs version 1.1.4, 30-Oct-2003
1.1.4 is quite old. Can you try a recent version of jfsutils?
http://jfs.sourceforge.net/project/pub/jfsutils-1.1.8.tar.gz
If that doesn't work, you can try running "fsck.jfs
--omit_journal_replay", since it is trapping while replaying the
journal. If all else fails, you should be able to mount it read-only
(mount -oro) to recover the data.
Thanks,
Shaggy
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2005-06-10 14:14 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 ` Dave Kleikamp [this message]
2005-06-10 14:21 ` [Jfs-discussion] " Alex Deucher
2005-06-10 16:09 ` Alex Deucher
2005-06-10 16:16 ` Dave Kleikamp
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=1118412882.7944.6.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