ocfs2: Switch over to JBD2.
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 3 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Ocfs2-devel] [PATCH 0/3] ocfs2: Switch over to JBD2.
Quoted 20 lines · Joel Becker
ocfs2 currently uses the Journaled Block Device (JBD) for its journaling. This is a very stable and tested codebase. However, JBD is limited by architecture to 32bit block numbers. This means an ocfs2 filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB. People want larger volumes.
Fortunately, there is now JBD2. JBD2 adds 64bit block number support and some other features. JBD2 is backwards compatible, so it can be used with existing filesystems. The new features won't be accessed until the ocfs2-tools turn them on.
Before we support JBD2, however, we need to ensure that inode blocks are allocated below that 32bit boundary. stat(2) cannot handle larger inode numbers on 32bit machines. With that limit in place, we can fully support JBD2 in the kernel filesystem. Like XFS, we provide the 'inode64' option to remove that limit.
A config option is provided (
OCFS2_COMPAT_JBD) to force ocfs2 to use the old JBD. This is for the paranoid while we test JBD2.
Quoted 6 lines
The kernel code is available on the 'jbd2' branch of my git repository.
View:
http://oss.oracle.com/git/?p=jlbec/linux-2.6.git;a=shortlog;h=jbd2
Pull:
git pullgit://oss.oracle.com/git/jlbec/linux-2.6.gitjbd2
Ok, these look great. A couple of notes:
- I removed an ML_NOTICE in the 1st patch
- I added information to Documentation/filesystems/ocfs2.txt in the 2nd patch
- Unsurprisingly, the last patch conflicted with lots of things:
CONFLICT (content): Merge conflict in fs/ocfs2/ocfs2.h CONFLICT (content): Merge conflict in fs/ocfs2/suballoc.c CONFLICT (content): Merge conflict in fs/ocfs2/super.c
They were fairly easy to fix - please double check my work. I created a branch 'feature_merge' in which I pulled in xattrs, dyn_la, and then jbd2 (purposfully keeping it on top). I'll just pull that into linux-next for now, since linux-next is throwaway and I don't want to have to re-merge every time I create it.
--Mark
--
Mark Fasheh