On 2015年05月02日 03:02, John Spray wrote:
On 30/04/2015 09:21, flisky wrote:
When I read the file through the ceph-fuse, the process crashed.
Here is the log -
terminate called after throwing an instance of
'ceph::buffer::end_of_buffer'
what(): buffer::end_of_buffer
***
On 30/04/2015 09:21, flisky wrote:
When I read the file through the ceph-fuse, the process crashed.
Here is the log -
terminate called after throwing an instance of
'ceph::buffer::end_of_buffer'
what(): buffer::end_of_buffer
*** Caught signal (Aborted) **
in thread 7
It turns out the permission problem.
When I change to ceph.admin, I can read the file, and the file content
seems garbage.
Best regards,
On 2015年05月01日 02:07, Gregory Farnum wrote:
The not permitted bit usually means that your client doesn't have
access permissions to the data pool in use.
The not permitted bit usually means that your client doesn't have
access permissions to the data pool in use.
I'm not sure why it would be getting aborted without any output though
— is there any traceback at all in the logs? A message about the
OOM-killer zapping it or something?
-Greg
On Thu,
Sorry，I cannot reproduce the "Operation not permitted" log
Here is a small portion of log with "debug_client = 20/20"
==
-22> 2015-04-30 16:29:12.858309 7fe9757f2700 10 client.58272
check_caps on 115.head(ref=2 ll_ref=10 cap_refs
When I read the file through the ceph-fuse, the process crashed.
Here is the log -
terminate called after throwing an instance of 'ceph::buffer::end_of_buffer'
what(): buffer::end_of_buffer
*** Caught signal (Aborted) **
in thread 7fe0814d3700
ceph version 0.94.1 (e4bfad
