On Mon, Jun 27, 2005 at 10:42:10PM -0700, Elliott Mitchell wrote:
> Package: e2fsprogs
> Version: 1.37-2sarge1
>
> `tune2fs` happily allows the creation of shared journals, and the kernel
> I've got happily allows mounting of filesystems utilizing a shared
> journal. OTOH `e2fsck` explodes when being run on such filesystems,
> whether or not they're clean.
>
> Documenting whether shared journals are supported would be nice...
Does the kernel actually work with shared journalled turned on? You
have multiple filesystems all using a single journal, and it does the
right thing? I didn't think that worked at the moment...
The problem with shared journals in general is that we need to handle
replaying multiple journals in a sane fashion, even if one of the
disks that is using a shared journal is temporarily unavailable. This
in practice means we need to be able to extract out the journal
entries that pertains to a particular filesystem, and save it to
persistent storage somewhere (which may be tricky if we haven't
checked the root filesystem yet, so it is read-only and other
filesystems haven't been mounted yet).
As far as I know the kernel-level replay code doesn't handle shared
journals, either.
But yeah, putting in a warning that shared journals don't quite work
would be a good thing.
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
