From: "Jens Rehpöhler" <jens.rehpoehler@filoo.de>
To: ceph-devel@vger.kernel.org
Cc: oliver.francke@filoo.de
Subject: BTRFS Warning
Date: Mon, 19 Dec 2011 09:28:55 +0100 [thread overview]
Message-ID: <4EEEF5C7.7090701@filoo.de> (raw)
Good morning !!
i got the following warning as soon as i use btrfs as underlaying
filesystem (for stability reasons i use ext4). I converted one OSD back
to btrfs to give it another try.
kernel: 3.2rc6
ceph: ceph/stable uptodate 0.39-9-g37e7a52-1~bpo60+1
dist: debian squeeze
[ 8930.692232] ------------[ cut here ]------------
[ 8930.692282] WARNING: at fs/btrfs/inode.c:1969
btrfs_orphan_commit_root+0x7f/0x9b [btrfs]()
[ 8930.692327] Hardware name: X8DT3
[ 8930.692349] Modules linked in: loop aes_x86_64 aes_generic cbc
kvm_intel xt_multiport ext2 iptable_filter ip_tables vhost_net macvtap
macvlan tun brd ebt_arp ebtable_filter ebtables x_tables kvm fuse ceph
libceph bridge stp llc ext4 jbd2 crc16 tpm_tis tpm joydev pcspkr ioatdma
tpm_bios processor i2c_i801 thermal_sys serio_raw button i2c_core evdev
ext3 jbd mbcache btrfs zlib_deflate crc32c libcrc32c sd_mod crc_t10dif
usbhid hid uhci_hcd ehci_hcd usbcore ixgbe 3w_sas mdio usb_common
scsi_mod igb dca [last unloaded: scsi_wait_scan]
[ 8930.698021] Pid: 336, comm: kworker/2:1 Tainted: G C
3.2.0-rc6 #2
[ 8930.698050] Call Trace:
[ 8930.698075] [<ffffffff81047257>] ? warn_slowpath_common+0x78/0x8c
[ 8930.698116] [<ffffffffa011ee22>] ?
btrfs_orphan_commit_root+0x7f/0x9b [btrfs]
[ 8930.698171] [<ffffffffa01182f3>] ? commit_fs_roots+0xa2/0x159 [btrfs]
[ 8930.698208] [<ffffffffa0118fcd>] ?
btrfs_commit_transaction+0x3e2/0x71b [btrfs]
[ 8930.698254] [<ffffffff8103b794>] ? pick_next_task_fair+0xfc/0x10e
[ 8930.698285] [<ffffffff81060b69>] ? wake_up_bit+0x20/0x20
[ 8930.698320] [<ffffffffa011952f>] ? btrfs_end_transaction+0x12/0x12
[btrfs]
[ 8930.698361] [<ffffffffa0119541>] ? do_async_commit+0x12/0x1b [btrfs]
[ 8930.698392] [<ffffffff8105cd0e>] ? process_one_work+0x1cc/0x2ea
[ 8930.698420] [<ffffffff8105cf59>] ? worker_thread+0x12d/0x247
[ 8930.698448] [<ffffffff8105ce2c>] ? process_one_work+0x2ea/0x2ea
[ 8930.698476] [<ffffffff8105ce2c>] ? process_one_work+0x2ea/0x2ea
[ 8930.698504] [<ffffffff8106072d>] ? kthread+0x7a/0x82
[ 8930.698531] [<ffffffff813316b4>] ? kernel_thread_helper+0x4/0x10
[ 8930.698560] [<ffffffff810606b3>] ? kthread_worker_fn+0x147/0x147
[ 8930.698588] [<ffffffff813316b0>] ? gs_change+0x13/0x13
[ 8930.698614] ---[ end trace 3b774941bf3fc465 ]---
Anything to worry about ?
thanks
Jens
next reply other threads:[~2011-12-19 8:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 8:28 Jens Rehpöhler [this message]
2011-12-19 18:51 ` BTRFS Warning Gregory Farnum
2011-12-21 13:22 ` Jens Rehpöhler
2011-12-21 15:35 ` Christian Brunner
2011-12-21 16:25 ` Gregory Farnum
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=4EEEF5C7.7090701@filoo.de \
--to=jens.rehpoehler@filoo.de \
--cc=ceph-devel@vger.kernel.org \
--cc=oliver.francke@filoo.de \
/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.