search for: jdb2

Hi, I'm pretty new to ocfs2 and a bit stuck. I have two Debian/Squeeze (testing) machines accessing an ocfs2 filesystem over aoe. The filesystem sits on an lvm2 volume, but I guess that is irrelevant. Even when mostly idle, everything accessing the cluster sometimes hangs for about 20 seconds. This happens rather frequently, say every 5 minutes, but the interval seems irregular while the

...nect to wine.budgetdedicated.com http: [IP: 81.171.111.184 80] W: Some index files failed to download, they have been ignored, or old ones used instead. W: You may want to run apt-get update to correct these problems Does anyone know what's going on and/or when this issue will be resolved? jdb2

>>> If you run top what are you seeing on the %Cpu(s) line? http://i.hizliresim.com/NrmV9Y.png On Mon, Feb 8, 2016 at 10:53 PM, Alvin Starr <alvin at netvel.net> wrote: > You need to provide more information. > 20% is what number. > There are something like 6 numbers on that line. > > > On 02/08/2016 02:56 PM, Gokan Atmaca wrote: >>> >>> If you

This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use

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