Not sure if it's useful to anyone, but there you go. This happened after a forced
power cycle:
BTRFS info (device dm-1): disk space caching is enabled
------------[ cut here ]------------
WARNING: CPU: 2 PID: 778 at fs/btrfs/delayed-inode.c:1410 btrfs_assert_delayed_root_empty+0x32/0x34()
Modules linked in: aes_x86_64 lm85 hwmon_vid dm_snapshot dm_bufio iptable_nat ip_tables nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_conntrack_ftp ipt_MASQUERADE nf_nat x_tables nf_conntrack sg st snd_pcm_oss snd_mixer_oss fuse snd_hda_codec_realtek snd_hda_codec_generic microcode snd_cmipci gameport snd_hda_intel kvm_intel snd_hda_controller kvm snd_hda_codec snd_opl3_lib eeepc_wmi snd_mpu401_uart snd_seq_midi snd_seq_midi_event snd_seq asus_wmi battery snd_rawmidi snd_hwdep sparse_keymap rfkill snd_pcm snd_seq_device tpm_infineon snd_timer tpm_tis rc_ati_x10 asix coretemp tpm i2c_i801 snd processor wmi pl2303 kl5kusb105 libphy ati_remote parport_pc rc_core xhci_hcd intel_rapl keyspan ftdi_sio evdev usbnet soundcore pcspkr parport lpc_ich intel_powerclamp ezusb usbserial x86_pkg_temp_thermal xts gf128mul dm_crypt dm_mod raid456 async_raid6_recov async_pq async_xor async_memcpy async_tx e1000e ptp pps_core crc32c_intel crc32_pclmul sata_sil24 thermal crct10dif_pclmul ehci_pci ehci_hcd ghash_clmulni_intel r8169 cryptd fan mii usbcore usb_common sata_mv
CPU: 2 PID: 778 Comm: btrfs-transacti Tainted: G W 3.16.7-amd64-i915-volpreempt-20141114 #1
Hardware name: System manufacturer System Product Name/P8H67-M PRO, BIOS 3806 08/20/2012
0000000000000000 ffff8802117abdc8 ffffffff816295db 0000000000000000
ffff8802117abe00 ffffffff81051e2d ffffffff8127038d ffff880211534000
ffff880212639980 0000000000000000 ffff8802137eaf00 ffff8802117abe10
Call Trace:
[<ffffffff816295db>] dump_stack+0x45/0x56
[<ffffffff81051e2d>] warn_slowpath_common+0x7f/0x98
[<ffffffff8127038d>] ? btrfs_assert_delayed_root_empty+0x32/0x34
[<ffffffff81051ef4>] warn_slowpath_null+0x1a/0x1c
[<ffffffff8127038d>] btrfs_assert_delayed_root_empty+0x32/0x34
[<ffffffff8122db95>] btrfs_commit_transaction+0x37f/0x867
[<ffffffff8122a2f1>] transaction_kthread+0xec/0x19f
[<ffffffff8122a205>] ? btrfs_cleanup_transaction+0x3f3/0x3f3
[<ffffffff8106cd8f>] kthread+0xae/0xb6
[<ffffffff8106cce1>] ? __kthread_parkme+0x61/0x61
[<ffffffff8163007c>] ret_from_fork+0x7c/0xb0
[<ffffffff8106cce1>] ? __kthread_parkme+0x61/0x61
---[ end trace 32de13ca415f14fa ]---
I'm now getting this on interval as kernel spam.
It doesn't say which of my 4 btrfs volumes this is linked to, which
doesn't make life easier.
Any idea what I should do from here?
Will btrfs scrub, even if it takes about 24H to run for me, tell me
which FS is affected and if so do I run btrfs repair?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
