Messages in this thread | | | Date | Fri, 10 Jun 2005 12:09:44 -0400 | From | Alex Deucher <> | Subject | Re: [Jfs-discussion] fsck.jfs segfaults on x86_64 |
| |
On 6/10/05, Alex Deucher <alexdeucher@gmail.com> wrote: > On 6/10/05, Dave Kleikamp <shaggy@austin.ibm.com> wrote: > > 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 > > sorry, I should have mentioned that. we also tried 1.1.7 with the > same result. I can try 1.1.8 too. >
1.1.8 segfaulted as well.
> > > > 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. > > cool I'll give that a try.
running fsck.jfs --omit_journal_replay did the trick! thanks,
Alex
> > Thanks! > > Alex > > > > > Thanks, > > Shaggy > > -- > > David Kleikamp > > IBM Linux Technology Center > > > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |