We have a large logical volume (6.91T) which contains a JFS. All of a sudden we were unable to mount the volume: mount /mnt/san mount: wrong fs type, bad option, bad superblock on /dev/vg00/lvol0, or too many mounted file systems We then tried to run fsck.jfs and got a Segmentation fault. lvdisplay and vgdisplay seem to work fine displaying the correct info. #> time fsck.jfs /dev/vg00/lvol0 fsck.jfs version 1.1.4, 30-Oct-2003 processing started: 6/8/2005 18.1.19 Using default parameter: -p The current device is: /dev/vg00/lvol0 Block size in bytes: 4096 Filesystem size in blocks: 1855561728 **Phase 0 - Replay Journal Log Segmentation fault real 1m40.396s user 0m0.038s sys 0m0.297s strace: <snip> lseek(3, 7600357904384, SEEK_SET) = 7600357904384 read(3, "8h\36\0\0\0t\17\0\206\1\0\0\0\0\0\0\10\204\0\0\0\0\0\1"..., 4096) = 4096 lseek(3, 4679075332096, SEEK_SET) = 4679075332096 read(3, "\301\v\201B\20\0\0\0 \357\20\0\336\\\24\0\4\0\0\0\370\351"..., 4096) = 4096 lseek(3, 4677018386432, SEEK_SET) = 4677018386432 read(3, "\0\0\0D\0\0\0\0\16\1\0\0\377\377\377\377\377\377\377\377"..., 4096) = 4096 lseek(3, 7600347168768, SEEK_SET) = 7600347168768 write(3, "D\0LOGREDO: Allocating for IMap:"..., 8192) = 8192 --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ /var/log/messages Jun 8 17:34:11 nutcracker fsck.jfs[12223]: segfault at 0000000000000490 rip 00000000004178f1 rsp 00007fffff996f40 error 6 Thanks in advance for any help. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Additional info: Linux nutcracker 2.6.12-rc6 #1 SMP Wed Jun 8 16:46:17 EDT 2005 x86_64 AMD Opteron(tm) Processor 244 AuthenticAMD GNU/Linux That's the only kernel version (2.6.12) that has support for a fiber channel Emulex card (lpfc).
This bug was reported to the jfs-discussion mailing list, and found to still be a problem with jfsutils-1.1.8. Running fsck.jfs --omit_journal_replay "fixed" the problem. I don't have x86_64 hardware, so I'd be interested in investigating this some more if you see it again.
Thanks Dave. Marking as UPSTREAM, please reopen or file a new bug when a patch (or new release) is available.