From: Andreas Dilger <aedilger@gmail.com>
To: Kevin Shanahan <kmshanah@disenchant.net>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Ext4 external journal UUID mismatch?
Date: Sun, 15 Jul 2012 22:32:01 -0600 [thread overview]
Message-ID: <11FEA6E4-EF75-4CD9-B2B6-78E42410027B@gmail.com> (raw)
In-Reply-To: <20120716025610.GB2562@tuon.disenchant.local>
On 2012-07-15, at 20:56, Kevin Shanahan <kmshanah@disenchant.net> wrote:
> On Mon, Jul 16, 2012 at 09:10:58AM +0930, Kevin Shanahan wrote:
>> I have created some filesystems with external journals, and after
>> reboot (clean shutdown) these will not mount anymore. I see in dmesg:
>>
>> [42214.365496] EXT4-fs (dm-10): journal UUID does not match
>>
>> However, the UUIDs look fine when viewed with dumpe2fs:
>>
> Here is what e2fsck said about it.
>
> # e2fsck -p -j /dev/ssdvg/jnl-kvmhost0 /dev/it8/nfs-kvmhost0
> /dev/it8/nfs-kvmhost0: Superblock hint for external superblock should be 0xfd0d. FIXED.
> /dev/it8/nfs-kvmhost0: clean, 43229/983040 files, 303609/3932160 blocks
>
> I guess that is the "Journal Device" field? Mount worked fine after
> that and the data looks okay.
>
> Any idea how this might have happened across all three fs with
> external journals?
Because LVM changed the block device numbers after the reboot, and the device number used previously for the external journal was different.
The lookup of the journal by UUID (instead of relying on the "device hint" in the superblock) _should_ be handled by mount, but I don't recall if we ever got a mount.ext4 to handle this or not. It would also be possible for the "fast e2fsck" check to verify the journal UUID before mounting the filesystem, but again I'm not sure if this is done yet, and I can't check right now.
Cheers, Andreas
next prev parent reply other threads:[~2012-07-16 4:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 23:40 Ext4 external journal UUID mismatch? Kevin Shanahan
2012-07-16 2:56 ` Kevin Shanahan
2012-07-16 4:32 ` Andreas Dilger [this message]
2012-07-16 10:00 ` Kevin Shanahan
2012-07-16 14:13 ` Andreas Dilger
2012-07-16 15:40 ` Theodore Ts'o
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=11FEA6E4-EF75-4CD9-B2B6-78E42410027B@gmail.com \
--to=aedilger@gmail.com \
--cc=kmshanah@disenchant.net \
--cc=linux-ext4@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