-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How can I check existence of an object? #22
Comments
That's a bug. Thanks for reporting. I'll have a fix soon. |
Just a supplemental report: it seems the behavior of |
do you have a minimal example of a script that will reproduce the error? |
Perfect thanks that's exactly what I was looking for. And what version of ceph and lua are u using
… On May 16, 2017, at 3:05 PM, Zheyuan Chen ***@***.***> wrote:
-- test.lua
rados = require 'rados'
cluster = rados.create()
cluster:conf_read_file()
cluster:connect()
ioctx = cluster:open_ioctx('test_pool')
print(ioctx:stat('test_obj'))
After several runs of the script, a segfault occurs as below. Sometimes, the segfault happens more often.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I'm testing with an older version of Ceph and the same verison of Lua, and I can't reproduce the error. I'll try with a newer version of Ceph soon. Would you be able to run this under GDB to get a back trace, or send me a core dump after the segfault? |
Here is the back trace generated from the core dump. It seems this is not caused by the
|
is it possible that you are running lua-rados with a version of rados that is different than the one you compiled with? |
I am running using this docker image: https://hub.docker.com/r/ceph/demo/ It seems librados-dev and ceph are both 11.2.0
|
I tried
stat()
on a non-existing object and I got a segfault. Do I have any way to check the existence of an object with this binding?The text was updated successfully, but these errors were encountered: