Hi,
I am trying out ext3 with an external journal (on a battery backed
RAM card). I use data=journal, and sync nfs writes go nice and fast :-)
But.. I had to power cycle it (buggy VM.. grumble :-) and now I cannot
get my filesystem back. It is only a test filesystem so I don't need
the data. But I want this to work before I put real data on it.
If I "fsck /dev/md1", it says
Parallelizing fsck version 1.22 (22-Jun-2001)
e2fsck 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09
Superblock has external ext3 journal device (unsupported).
Abort<y>?
So I say yes.
I try to mount it :
mount /dev/md1 /export/eno/1 -t ext3
and the kernel log says:
EXT3-fs: External journal has more than one user (unsupported) - 2
which is a lie. There is only one user.
I am using 2.4.13 with EXT3 FS 2.4-0.9.13, 21 Oct 2001, and
e2fsprocs 1.22.
I appreciate that there is a 0.9.14 out but the changelog doesn't
mention anything about external journals.
I created the filesystem and journal as per the instructions on
andrewm's ext3 web page.
Any patches or suggestions most welcome.
NeilBrown
Hi,
I am trying out ext3 with an external journal (on a battery backed
RAM card). I use data=journal, and sync nfs writes go nice and fast :-)
But.. I had to power cycle it (buggy VM.. grumble :-) and now I cannot
get my filesystem back. It is only a test filesystem so I don't need
the data. But I want this to work before I put real data on it.
If I "fsck /dev/md1", it says
Parallelizing fsck version 1.22 (22-Jun-2001)
e2fsck 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09
Superblock has external ext3 journal device (unsupported).
Abort<y>?
So I say yes.
I try to mount it :
mount /dev/md1 /export/eno/1 -t ext3
and the kernel log says:
EXT3-fs: External journal has more than one user (unsupported) - 2
which is a lie. There is only one user.
I am using 2.4.13 with EXT3 FS 2.4-0.9.13, 21 Oct 2001, and
e2fsprocs 1.22.
I appreciate that there is a 0.9.14 out but the changelog doesn't
mention anything about external journals.
I created the filesystem and journal as per the instructions on
andrewm's ext3 web page.
Any patches or suggestions most welcome.
NeilBrown
On Fri, Nov 02, 2001 at 12:06:32PM +1100, Neil Brown wrote:> > I am trying out ext3 with an external journal (on a battery backed > RAM card). I use data=journal, and sync nfs writes go nice and fast :-)Which battery-backed RAM card are you using? I've been wanting to make a list available of non-volatile RAM cards that are both (a) cheap, and (b) work with Linux, so I'm curious which card you're playing with.> If I "fsck /dev/md1", it says > > Parallelizing fsck version 1.22 (22-Jun-2001) > e2fsck 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09 > Superblock has external ext3 journal device (unsupported).E2fsprogs 1.23 was the first version that supported external journals, but some bugs weren't worked out until 1.24, and I'd strongly suggest that you use e2fsprogs 1.25 if you're playing with such bleeding-edge features. I'm really glad that you're playing with the external journal feature. I can't quite recommend that you use it for production data just yet, since we haven't had that many people report success using it. So if it does work out for you, please let us know!! - Ted
On Nov 02, 2001 12:06 +1100, Neil Brown wrote:> If I "fsck /dev/md1", it says > > Parallelizing fsck version 1.22 (22-Jun-2001) > e2fsck 1.22, 22-Jun-2001 for EXT2 FS 0.5b, 95/08/09 > Superblock has external ext3 journal device (unsupported). > Abort<y>?I just re-read this message - you are using e2fsck 1.22, and it is possible that journal-device support wasn't added until after that. Try with 1.25 and see if the problem still happens.> and the kernel log says: > > EXT3-fs: External journal has more than one user (unsupported) - 2 > > which is a lie. There is only one user. > > I am using 2.4.13 with EXT3 FS 2.4-0.9.13, 21 Oct 2001, and > e2fsprogs 1.22.Note that external journals aren't really supported fully. The e2fsck code does not yet work when e2fsck'ing a journal device directly. What _should_ happen is that it goes out and e2fsck's all of the users of the journal, and any devices which can't be found (by UUID) have their journal data written to a file, and when they are e2fsck'd they first check for this journal file to recover their journal transactions. Granted that we are nowhere close to supporting shared external journals yet, but the basic support could be added (i.e. fsck'ing the journal device instead of the filesystem itself). Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/