From: Noah Watkins <jayhawk@cs.ucsc.edu>
To: ceph-devel@vger.kernel.org
Cc: John Ralston <jralston@ucsc.edu>
Subject: Fwd: Intermittent Assert Failure
Date: Wed, 07 Dec 2011 21:20:14 -0800 [thread overview]
Message-ID: <4EE0490E.2000205@cs.ucsc.edu> (raw)
Stack trace from a simple Ceph client that does nothing more than open a
file and call ceph_read(...) on it.
- Noah
Hey,
I just wanted to note that I got this failure occasionally when I was
running ceph_read on issdm-29
@issdm-29:~$ time ./ceph_read /etc/ceph/ceph.conf /john.1gb.bin
client/Client.cc: In function 'void Client::put_inode(Inode*, int)', in
thread '7fbccb1ea760'
client/Client.cc: 1763: FAILED assert(!unclean)
ceph version 0.38-259-gd4aef20
(commit:d4aef20210d43e25eefe945009e6f77d5b045381)
1: (Client::put_inode(Inode*, int)+0x615) [0x7fbccabe0455]
2: (Client::unlink(Dentry*, bool)+0x27d) [0x7fbccabe1fed]
3: (Client::trim_dentry(Dentry*)+0x73) [0x7fbccabe31a3]
4: (Client::trim_cache()+0x215) [0x7fbccabe3585]
5: (Client::unmount()+0x4d4) [0x7fbccac06474]
6: (ceph_shutdown()+0x79) [0x7fbccabd00e9]
7: ./ceph_read() [0x400e3e]
8: (__libc_start_main()+0xfe) [0x7fbcca7fcd8e]
9: ./ceph_read() [0x400a69]
ceph version 0.38-259-gd4aef20
(commit:d4aef20210d43e25eefe945009e6f77d5b045381)
1: (Client::put_inode(Inode*, int)+0x615) [0x7fbccabe0455]
2: (Client::unlink(Dentry*, bool)+0x27d) [0x7fbccabe1fed]
3: (Client::trim_dentry(Dentry*)+0x73) [0x7fbccabe31a3]
4: (Client::trim_cache()+0x215) [0x7fbccabe3585]
5: (Client::unmount()+0x4d4) [0x7fbccac06474]
6: (ceph_shutdown()+0x79) [0x7fbccabd00e9]
7: ./ceph_read() [0x400e3e]
8: (__libc_start_main()+0xfe) [0x7fbcca7fcd8e]
9: ./ceph_read() [0x400a69]
terminate called after throwing an instance of 'ceph::FailedAssertion'
Aborted
next reply other threads:[~2011-12-08 5:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 5:20 Noah Watkins [this message]
2011-12-08 5:54 ` Fwd: Intermittent Assert Failure Sage Weil
2012-04-16 18:33 ` Joe Buck
2012-04-16 18:41 ` Sage Weil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE0490E.2000205@cs.ucsc.edu \
--to=jayhawk@cs.ucsc.edu \
--cc=ceph-devel@vger.kernel.org \
--cc=jralston@ucsc.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.