From: Hendrik Friedel <hendrik@friedels.name>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfsck errors is it save to fix?
Date: Mon, 04 Nov 2013 22:14:08 +0100 [thread overview]
Message-ID: <52780E20.8020405@friedels.name> (raw)
In-Reply-To: <5274BEC8.5060804@friedels.name>
Hello,
the list was quite full with patches, so this might have been hidden.
Here the complete Stack.
Does this help? Is this what you needed?
Greetings,
Hendrik
> sorry about that:
> [ 126.444603] init: plymouth-stop pre-start process (3446) terminated
> with status 1
> [11189.299864] hda-intel: IRQ timing workaround is activated for card
> #0. Suggest a bigger bdl_pos_adj.
> [94999.489736] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 2
> transid 140408 /dev/sdc1
> [94999.489755] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 1
> transid 140408 /dev/sdb1
> [95394.400840] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 1
> transid 140420 /dev/sdb1
> [95394.400872] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 2
> transid 140420 /dev/sdc1
> [95585.149738] init: smbd main process (1168) killed by TERM signal
> [95725.171156] nfsd: last server has exited, flushing export cache
> [95764.899173] ------------[ cut here ]------------
> [95764.899216] WARNING: CPU: 1 PID: 21798 at
> /home/apw/COD/linux/fs/btrfs/disk-io.c:3423 free_fs_root+0x99/0xa
> 0 [btrfs]()
> [95764.899219] Modules linked in: nvram pci_stub vboxpci(OF)
> vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) ip6tabl
> e_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat
> nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_de
> frag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle
> xt_tcpudp iptable_filter ip_tables x_tab
> les bridge stp llc kvm_intel kvm nfsd nfs_acl auth_rpcgss nfs fscache
> binfmt_misc lockd sunrpc ftdi_sio usbser
> ial stv6110x lnbp21 snd_hda_codec_realtek snd_hda_intel stv090x
> snd_hda_codec snd_hwdep snd_pcm ddbridge dvb_c
> ore snd_timer snd soundcore snd_page_alloc cxd2099(C) mei_me psmouse
> i915 drm_kms_helper mei drm lpc_ich i2c_a
> lgo_bit serio_raw video mac_hid coretemp lp parport hid_generic usbhid
> hid btrfs raid6_pq e1000e ptp pps_core
> ahci libahci xor zlib_deflate libcrc32c
> [95764.899294] CPU: 1 PID: 21798 Comm: umount Tainted: GF CIO
> 3.11.0-031100rc2-generic #201307211535
> [95764.899297] Hardware name: /DH87RL, BIOS
> RLH8710H.86A.0320.2013.0606.1802 06/06/2013
> [95764.899300] 0000000000000d5f ffff880118b59cb8 ffffffff8171e74d
> 0000000000000007
> [95764.899306] 0000000000000000 ffff880118b59cf8 ffffffff8106532c
> ffff880118b59d08
> [95764.899311] ffff8801184cb800 ffff8801184cb800 ffff880118118000
> ffff880118b59d78
> [95764.899315] Call Trace:
> [95764.899324] [<ffffffff8171e74d>] dump_stack+0x46/0x58
> [95764.899331] [<ffffffff8106532c>] warn_slowpath_common+0x8c/0xc0
> [95764.899336] [<ffffffff8106537a>] warn_slowpath_null+0x1a/0x20
> [95764.899359] [<ffffffffa00d9a59>] free_fs_root+0x99/0xa0 [btrfs]
> [95764.899384] [<ffffffffa00dd653>]
> btrfs_drop_and_free_fs_root+0x93/0xc0 [btrfs]
> [95764.899408] [<ffffffffa00dd74f>] del_fs_roots+0xcf/0x130 [btrfs]
> [95764.899433] [<ffffffffa00ddac6>] close_ctree+0x146/0x270 [btrfs]
> [95764.899441] [<ffffffff811cd24e>] ? evict_inodes+0xce/0x130
> [95764.899461] [<ffffffffa00b4eb9>] btrfs_put_super+0x19/0x20 [btrfs]
> [95764.899467] [<ffffffff811b47e2>] generic_shutdown_super+0x62/0xf0
> [95764.899475] [<ffffffff811b4906>] kill_anon_super+0x16/0x30
> [95764.899493] [<ffffffffa00b754a>] btrfs_kill_super+0x1a/0x90 [btrfs]
> [95764.899500] [<ffffffff811b512d>] deactivate_locked_super+0x4d/0x80
> [95764.899505] [<ffffffff811b57ae>] deactivate_super+0x4e/0x70
> [95764.899510] [<ffffffff811d1266>] mntput_no_expire+0x106/0x160
> [95764.899515] [<ffffffff811d2b79>] SyS_umount+0xa9/0xf0
> [95764.899520] [<ffffffff817333ef>] tracesys+0xe1/0xe6
> [95764.899524] ---[ end trace 0024dfebf572e76c ]---
> [95764.985245] VFS: Busy inodes after unmount of sdb1. Self-destruct in
> 5 seconds. Have a nice day...
> [95790.079663] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 1
> transid 140425 /dev/sdb1
> [95790.101778] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 2
> transid 140425 /dev/sdc1
> [95790.162960] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 1
> transid 140425 /dev/sdb1
> [95790.163825] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 2
> transid 140425 /dev/sdc1
> [95924.393344] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 1
> transid 140425 /dev/sdb1
> [95924.421118] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 2
> transid 140425 /dev/sdc1
> [95924.676571] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 1
> transid 140425 /dev/sdb1
> [95924.677046] device fsid 989306aa-d291-4752-8477-0baf94f8c42f devid 2
> transid 140425 /dev/sdc1
>
>
> Greetings,
> Hendrik
>
>
> Am 02.11.2013 09:12, schrieb cwillu:
>>> Now that I am searching, I see this in dmesg:
>>> [95764.899359] [<ffffffffa00d9a59>] free_fs_root+0x99/0xa0 [btrfs]
>>> [95764.899384] [<ffffffffa00dd653>]
>>> btrfs_drop_and_free_fs_root+0x93/0xc0
>>> [btrfs]
>>> [95764.899408] [<ffffffffa00dd74f>] del_fs_roots+0xcf/0x130 [btrfs]
>>> [95764.899433] [<ffffffffa00ddac6>] close_ctree+0x146/0x270 [btrfs]
>>> [95764.899461] [<ffffffffa00b4eb9>] btrfs_put_super+0x19/0x20 [btrfs]
>>> [95764.899493] [<ffffffffa00b754a>] btrfs_kill_super+0x1a/0x90 [btrfs]
>>
>> Need to see the rest of the trace this came from.
>>
>
>
--
Hendrik Friedel
Auf dem Brink 12
28844 Weyhe
Mobil 0178 1874363
next prev parent reply other threads:[~2013-11-04 21:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 22:29 btrfsck errors is it save to fix? Hendrik Friedel
2013-11-02 8:12 ` cwillu
2013-11-02 8:58 ` Hendrik Friedel
2013-11-04 21:14 ` Hendrik Friedel [this message]
2013-11-05 2:03 ` cwillu
2013-11-06 6:45 ` Hendrik Friedel
2013-11-07 19:16 ` Hendrik Friedel
2013-11-08 10:09 ` Duncan
2013-11-09 8:33 ` Hendrik Friedel
2013-11-11 19:06 ` Hendrik Friedel
2013-11-11 23:58 ` Kai Krakow
2013-11-12 7:32 ` Duncan
2013-11-12 19:37 ` Kai Krakow
2013-11-13 12:20 ` Duncan
2013-11-13 12:24 ` Duncan
2013-11-16 12:32 ` Hendrik Friedel
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=52780E20.8020405@friedels.name \
--to=hendrik@friedels.name \
--cc=cwillu@cwillu.com \
--cc=linux-btrfs@vger.kernel.org \
/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.