From: Eric Estabrooks (eric_at_urbanrage.com)
Date: Tue 06 May 2003 - 17:06:46 BST
Wray Cason wrote:
>>>>Very interesting. Is there any write-up available for this solution? I
>>>>am eager to learn more about the specifics. I gather that one important
>>>>point to consider is the fact that the vserver kernel doesn't support
>>>>journaling file systems.
>>>It doesn't? I've been using ext3 for years with vserver kernels.
>>i'm using xfs and ext3 with vserver kernels...
>I read somewhere that journaling was not yet supported. That appears to have
>changes as of ctx-17. I am presently running the precompiled vserver -17
>kernel. I see that there is no ext3.o module for my file system. Upon boot,
>it tries to load jfs.o with this error:
>/lib/modules/2.4.20ctx-17/kernel/fs/jfs/jfs.o: unresolved symbol IS_IMMUTABLE
>/lib/modules/2.4.20ctx-17/kernel/fs/jfs/jfs.o: insmod jfs failed
>I am not clear on what this means exactly for my system. I gather however
>that there is no journaling going on and that this is a particularly bad thing
>for this network RAID1 scenario.
If you compile your own kernel with the ctx patch you can have all the
journaling you want. I've been using ext3 since ctx13 and haven't seen
any problems with it.