Hi,
I'm trying to test the btrfs and ceph contributions to 3.11, without
testing all of 3.11-rc1 (just yet), so I'm testing with the "next"
branch of Chris Mason's tree (commit cbacd76bb3 from
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git)
merged into the for-linus branch of
What version are you running? How did you move the osds from 2TB to 4TB?
-Sam
On Wed, Jul 17, 2013 at 12:59 AM, Ta Ba Tuan wrote:
> Hi everyone,
>
> I converted every osds from 2TB to 4TB, and when moving complete, show log
> Ceph realtime"ceph -w":
> displays error: "I don't have pgid 0.2c8"
>
On Wed, 17 Jul 2013, Li Wang wrote:
> This patch implements fallocate and punch hole support for Ceph fuse client.
>
> Signed-off-by: Yunchuan Wen
> Signed-off-by: Li Wang
> ---
> The version of fsx.c at ceph.com/qa refered by qa/workunits/suites/fsx.sh
> does not support hole punching.
> Inste
From: "Yan, Zheng"
Once a lock is in LOCK_XLOCKDONE state, client already holds xlock
can acquire extra xlock. So wake up xlock waiter when we set lock
state to LOCK_XLOCKDONE.
Signed-off-by: Yan, Zheng
---
src/mds/Locker.cc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a
From: "Yan, Zheng"
commit 0071b8e75b (mds: stay in SCAN state in file_eval) makes
Locker::file_eval() ignore lock in LOCK_SCAN state. If there
is no request changes the lock state, the lock can be stuck in
LOCK_SCAN state forever. This can cause client read/write hang
because lock in LOCK_SCAN st
From: "Yan, Zheng"
For acquiring/cancelling xlock, the lock state transitions for
dentry lock and other types of locks are the same. So I think
the "type != CEPH_LOCK_DN" check doesn't make sense.
Signed-off-by: Yan, Zheng
---
src/mds/Locker.cc | 12 +---
1 file changed, 5 insertions(+
From: "Yan, Zheng"
these patches are also in:
git://github.com/ukernel/ceph.git wip-mds
Regards
Yan, Zheng
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-inf
From: "Yan, Zheng"
If we find lock state is LOCK_LOCK_XLOCK when cancelling xlock,
set lock state to LOCK_XLOCK_DONE and call Locker::eval_gather().
This makes sure the lock will eventually transit to a stable state.
(LOCK_XLOCK_DONE's next state is stable)
Signed-off-by: Yan, Zheng
---
src/md
From: "Yan, Zheng"
If lock state is LOCK_XLOCKDONE, the xlocker can have GSHARED cap.
So when finishing xlock, we may need to revoke the GSHARED cap.
In most cases Locker::_finish_xlock() directly set lock state to
LOCK_LOCK or LOCK_EXCL, which hides the issue. If 'num_rdlock > 0'
or 'num_wrlock
From: "Yan, Zheng"
There are several issues in the Capability::confirm_receipt()
1. when receiving a client caps message with 'seq == last_sent',
it doesn't mean we finish revoking caps. The client can send
caps message that only flushes dirty metadata.
2. When receiving a client caps mes
This patch implements fallocate and punch hole support for Ceph fuse client.
Signed-off-by: Yunchuan Wen
Signed-off-by: Li Wang
---
The version of fsx.c at ceph.com/qa refered by qa/workunits/suites/fsx.sh
does not support hole punching.
Instead, we are using the one from git://ceph.newdream.ne
On Wed, Jul 17, 2013 at 08:59:43AM +0200, Kasper Dieter wrote:
> Hi Xiaoxi, Wheats,
>
> you hit the right point: We are looking for an Enterprise Linux distribution
> as base for Ceph.
> RHEL and CentOS has a very broad distribution and a high acceptance in the
> Data Center due to our observati
Hi Xiaoxi, Wheats,
you hit the right point: We are looking for an Enterprise Linux distribution as
base for Ceph.
RHEL and CentOS has a very broad distribution and a high acceptance in the Data
Center due to our observation.
The pain of this distro (from Ceph point of view) is the old kernel.
A
13 matches
Mail list logo
