search for: ocfs2_reserve_local_alloc_bits

...--------------- cp/3919 is trying to acquire lock: (&oi->ip_alloc_sem){----}, at: [<ffffffffa02e789e>] ocfs2_prepare_dir_for_insert+0x13d3/0x1999 [ocfs2] but task is already holding lock: (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#4){--..}, at: [<ffffffffa03017ff>] ocfs2_reserve_local_alloc_bits+0xf6/0xdec [ocfs2] which lock already depends on the new lock. the existing dependency chain (in reverse order) is: -> #1 (&ocfs2_sysfile_lock_key[args->fi_sysfile_type]#4){--..}: [<ffffffff80249be9>] add_lock_to_list+0x74/0xb3 [<ffffffff8024ce4d>] __lock_acq...

...881,0):ocfs2_search_chain:1244 ERROR: status = -5 (2881,0):ocfs2_claim_suballoc_bits:1433 ERROR: status = -5 (2881,0):__ocfs2_claim_clusters:1715 ERROR: status = -5 (2881,0):ocfs2_local_alloc_new_window:1013 ERROR: status = -5 (2881,0):ocfs2_local_alloc_slide_window:1116 ERROR: status = -5 (2881,0):ocfs2_reserve_local_alloc_bits:537 ERROR: status = -5 (2881,0):__ocfs2_reserve_clusters:725 ERROR: status = -5 (2881,0):ocfs2_lock_allocators:677 ERROR: status = -5 (2881,0):__ocfs2_extend_allocation:739 ERROR: status = -5 (2881,0):ocfs2_extend_no_holes:952 ERROR: status = -5 (2881,0):ocfs2_expand_nonsparse_inode:1678 ERROR: sta...

...017.413519] [<ffffffffa050f8ff>] ocfs2_local_alloc_new_window+0x1cf/0x320 [ocfs2] Jun 19 14:22:45 posta2 kernel: [885017.413581] [<ffffffffa050fdd0>] ocfs2_local_alloc_slide_window+0x380/0x5e0 [ocfs2] Jun 19 14:22:45 posta2 kernel: [885017.413642] [<fffffffbyefa05101d3>] ocfs2_reserve_local_alloc_bits+0x1a3/0x330 [ocfs2] Jun 19 14:22:45 posta2 kernel: [885017.413706] [<ffffffffa053396b>] ocfs2_reserve_clusters_with_limit+0xab/0x330 [ocfs2] Jun 19 14:22:45 posta2 kernel: [885017.413780] [<ffffffffa0534d15>] ocfs2_lock_allocators+0xc5/0x290 [ocfs2] Jun 19 14:22:45 posta2 ke...

...:1363 ERROR: status = -5 (kvm,12322,1):ocfs2_claim_suballoc_bits:1524 ERROR: status = -5 (kvm,12322,1):__ocfs2_claim_clusters:1806 ERROR: status = -5 (kvm,12322,1):ocfs2_local_alloc_new_window:1013 ERROR: status = -5 (kvm,12322,1):ocfs2_local_alloc_slide_window:1116 ERROR: status = -5 (kvm,12322,1):ocfs2_reserve_local_alloc_bits:537 ERROR: status = -5 (kvm,12322,1):__ocfs2_reserve_clusters:816 ERROR: status = -5 (kvm,12322,1):ocfs2_lock_allocators:677 ERROR: status = -5 (kvm,12322,1):ocfs2_write_begin_nolock:1750 ERROR: status = -5 (kvm,12322,1):ocfs2_write_begin:1860 ERROR: status = -5 (kvm,12322,1):ocfs2_file_buffered_wr...

Hi all, this patch set are the backport of inode alloc improvement from mainline to ocfs2-1.4. the patches are almost the same excpet one thing: Joel has added JBD2 support to ocfs2, so he has added "max_blocks" to alloc_context and add a new function "ocfs2_reserve_clusters_with_limit". We don't have that in ocfs2-1.4. So there are some great difference in patch 2.

In ocfs2, the inode block search looks for the "emptiest" inode group to allocate from. So if an inode alloc file has many equally (or almost equally) empty groups, new inodes will tend to get spread out amongst them, which in turn can put them all over the disk. This is undesirable because directory operations on conceptually "nearby" inodes force a large number of seeks. So

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

Changelog from V1 to V2: 1. Modify some codes according to Mark's advice. 2. Attach some test statistics in the commit log of patch 3 and in this e-mail also. See below. Hi all, In ocfs2, when we create a fresh file system and create inodes in it, they are contiguous and good for readdir+stat. While if we delete all the inodes and created again, the new inodes will get spread out and that

I'm running a bit late with the e-mail this time around, but I think that's ok since there really isn't any major new features here - the bulk of the Ocfs2 update is bug fixes, or cleanups. The same goes for configfs. The only two things that could be described as features would be: - Sunil has updated Ocfs2 to provide even more live cluster locking information via debugfs. - Joel

Please review the list of patches being applied to the ocfs2 1.4 tree. All patches list the mainline commit hash. Thanks Sunil

Hi, The following patches comprise the bulk of Ocfs2 updates for the 2.6.30 merge window. Aside from larger, more involved fixes, we're adding the following features, which I will describe in the order their patches are mailed. Sunil's exported some more state to our debugfs files, and consolidated some other aspects of our debugfs infrastructure. This will further aid us in debugging

The following series of patches comprises the bulk of our outstanding changes for Ocfs2. Aside from the usual set of cleanups and fixes that were inappropriate for 2.6.25, there are a few highlights: The '/sys/o2cb' directory has been moved to '/sys/fs/o2cb'. The new location meshes better with modern sysfs layout. A symbolic link has been placed in the old location so as to