Re: Newstore Read ?

[Mark Nelson <mnelson@redhat.com>]

On 05/05/2015 05:11 PM, kernel neophyte wrote:
> Hi,
>
> I am unable to get any reads out of Newstore. The log is filled with
> assert failures.
>
>> 2015-05-05 14:49:46.654113 7f4236387700 -1 os/newstore/NewStore.cc: In function 'virtual int NewStore::fiemap(coll_t, const ghobject_t&, uint64_t, size_t, ceph::bufferlist&)' thread 7f4236387700 time 2015-05-05 14:49:46.582991
>
> os/newstore/NewStore.cc: 1371: FAILED assert(0)
>
>
>   ceph version 0.93-1098-g66e555d (66e555d4a6e2fd21efd9da0d1ebd3feb024b041e)
>
>   1: (ceph::__ceph_assert_fail(char const*, char const*, int, char
> const*)+0x8b) [0xc9bdeb]
>
>   2: ceph-osd() [0x9ea293]
>
>   3: (ReplicatedPG::do_osd_ops(ReplicatedPG::OpContext*,
> std::vector<OSDOp, std::allocator<OSDOp> >&)+0x708c) [0x8d8ccc]
>
>   4: (ReplicatedPG::prepare_transaction(ReplicatedPG::OpContext*)+0x97)
> [0x8e6427]
>
>   5: (ReplicatedPG::execute_ctx(ReplicatedPG::OpContext*)+0x5e5) [0x8e6c85]
>
>   6: (ReplicatedPG::do_op(std::tr1::shared_ptr<OpRequest>&)+0x2907) [0x8eac87]
>
>   7: (ReplicatedPG::do_request(std::tr1::shared_ptr<OpRequest>&,
> ThreadPool::TPHandle&)+0x66a) [0x877bea]
>
>   8: (OSD::dequeue_op(boost::intrusive_ptr<PG>,
> std::tr1::shared_ptr<OpRequest>, ThreadPool::TPHandle&)+0x3bd)
> [0x6d94fd]
>
>   9: (OSD::ShardedOpWQ::_process(unsigned int,
> ceph::heartbeat_handle_d*)+0x331) [0x6d9a21]
>
>   10: (ShardedThreadPool::shardedthreadpool_worker(unsigned int)+0x875)
> [0xc77905]
>
>   11: (ShardedThreadPool::WorkThreadSharded::entry()+0x10) [0xc79a20]
>
>   12: (()+0x8182) [0x7f427fe7c182]
>
>   13: (clone()+0x6d) [0x7f427de8e47d]
>
>   NOTE: a copy of the executable, or `objdump -rdS <executable>` is
> needed to interpret this.
>
> Is anyone else seeing this ?

I've mostly been focused on write performance.  Reads used to work, but 
it's possible something broke recently.  I'll try to reproduce.

>
> -Neo
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>