We are running ext3 with external journal on an ssd disk, as
described on

http://insights.oetiker.ch/linux/external-journal-on-ssd/

Today our server crashed (reason unknown) and when it booted again,
all the ext3 filesystems with external journal refused to mount
with the following error message

Mar 3 12:16:58 srv-rhein kernel: [ 331.556972] EXT3-fs: journal UUID does not match [kern.err]
Mar 3 12:16:58 srv-rhein kernel: [ 331.605125] EXT3-fs: journal UUID does not match [kern.err]
Mar 3 12:16:58 srv-rhein kernel: [ 331.641793] EXT3-fs: journal UUID does not match [kern.err]
Mar 3 12:16:58 srv-rhein kernel: [ 331.668446] EXT3-fs: journal UUID does not match [kern.err]
Mar 3 12:16:58 srv-rhein kernel: [ 331.714423] EXT3-fs: journal UUID does not match [kern.err]
Mar 3 12:16:58 srv-rhein kernel: [ 331.749856] EXT3-fs: journal UUID does not match [kern.err]
Mar 3 12:16:58 srv-rhein kernel: [ 331.779711] EXT3-fs: journal UUID does not match [kern.err]

It was the same from ALL filesystems so I supect there is a
systematic problem ...

We are running kernel 2.6.22.18

The filesystems were all mounted with

defaults,rw,errors=panic,noatime,data=journal


I could recover from the problem by

- fsck of the filesystems (all were consistant)
- re-initializing all journals
- re-adding all the journals

Any ideas what caused the problem ? After all this is exactly the
type of crash we have these journals for, so it is pretty bad when
they fail exactly at that moment ...

Should we not be using the LABEL syntax for journal reference ?

cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
http://it.oetiker.ch tobi@oetiker.ch ++41 62 775 9902 / sb: -9900

_______________________________________________
Ext3-users mailing list
Ext3-users@redhat.com
https://www.redhat.com/mailman/listinfo/ext3-users