EXT3: failed to claim external journal device.

Johann Lombardi johann.lombardi at bull.net
Thu Jan 26 09:52:34 UTC 2006


> > Here's the system information and command line used to create the
> > filesystem :
> > SuSE SLES9 2 , kernel 2.6.5
> > ada718-5:/ # rpm -qa | grep e2fs
> > e2fsprogs-1.36-6.2
> > -----------------------------------------
> > mke2fs -O journal_dev   /dev/mapper/home_jou_vol_grp-home_jou 400000
> > mke2fs -E stride=16 -O sparse_super,dir_index -j -J
> > device=/dev/mapper/home_jou_vol_grp-home_jou 
> > /dev/mapper/home_vol_grp-home
> >
> > Any ideas?
>
> I believe the kernel does the journal device lookup by the device
> major/minor, and those are not fixed for LVM devices.  

If the filesystem was _cleanly_ unmounted, you can try to remove/reattach the
external journal. It will update the superblock with the new major/minor
numbers.
You can proceed as follows:
# tune2fs -f -O^has_journal /dev/mapper/home_vol_grp-home
# tune2fs -J device=/dev/mapper/home_jou_vol_grp-home_jou /dev/mapper/home_vol_grp-home

It will work until the journal device's major/minor numbers change again 
(the next reboot?).

> Bull recently posted a patch here for mount to automatically find the
> correct block device for this journal UUID.

Actually, it was on ext2-devel:
http://thread.gmane.org/gmane.comp.file-systems.ext2.devel/2950

Johann
-------------- next part --------------
An embedded message was scrubbed...
From: Pekka Enberg <penberg at cs.helsinki.fi>
Subject: [Ext2-devel] [PATCH] ext2: return FSID for statvfs
Date: Tue, 06 Dec 2005 22:22:48 +0200
Size: 5581
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20060126/20cc0461/attachment.eml>


More information about the Ext3-users mailing list