Re: Segmentation Faults
Dear David and Liu, I need to reclaim the drive space being taken up by this perhaps corrupt btrfs file system. Is there any additional information you would like before this problem will no longer be reproducible? Thanks, Tim On Fri, Nov 25, 2011 at 11:25 AM, Timothy Crone tjcr...@gmail.com wrote: Okay, I built the version you sent me. I am guessing that this has the newest btrfs code in it even though it is labeled 3.1.0? Is that because it has not been merged? Relevant commands and a stack trace below. Still says something about a null pointer. root@berna:~# uname -a Linux berna 3.1.0+ #3 SMP Wed Nov 23 08:27:28 EST 2011 x86_64 GNU/Linux root@berna:~# rm -rf /home/myusername/.cache/chromium [180054.695188] parent transid verify failed on 1782596403200 wanted 25633 found 44577 [180054.695264] parent transid verify failed on 1782596403200 wanted 25633 found 44577 [180054.695337] parent transid verify failed on 1782596403200 wanted 25633 found 44577 [180054.695409] parent transid verify failed on 1782596403200 wanted 25633 found 44577 [180054.695482] parent transid verify failed on 1782596403200 wanted 25633 found 44577 [180054.695562] parent transid verify failed on 1782596403200 wanted 25633 found 44577 [180054.695635] parent transid verify failed on 1782596403200 wanted 25633 found 44577 [180054.695708] parent transid verify failed on 1782596403200 wanted 25633 found 44577 [180054.695780] parent transid verify failed on 1782596403200 wanted 25633 found 44577 [180054.695852] parent transid verify failed on 1782596403200 wanted 25633 found 44577 [180059.285139] btrfs: corrupt leaf, slot offset bad: block=1782603522048,root=1, slot=0 [180059.285229] BUG: unable to handle kernel NULL pointer dereference at 0020 [180059.285366] IP: [a020ad3f] btrfs_print_leaf+0x28/0x766 [btrfs] [180059.285465] PGD 31a5c5067 PUD 31c6c6067 PMD 0 [180059.285614] Oops: [#1] SMP [180059.285730] CPU 6 [180059.285765] Modules linked in: parport_pc ppdev lp parport bridge stp bnep rfcomm cpufreq_conservative bluetooth xt_tcpudp cpufreq_userspace ipt_LOG cpufreq_powersave xt_recent cpufreq_stats nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack rfkill crc16 xt_multiport mperf iptable_filter ip_tables x_tables binfmt_misc fuse nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc firewire_sbp2 loop snd_hda_codec_analog mxm_wmi wmi tpm_tis tpm psmouse snd_hda_intel snd_hda_codec tpm_bios snd_hwdep snd_pcm snd_seq snd_timer i7core_edac snd_seq_device edac_core snd soundcore asus_atk0110 processor snd_page_alloc pcspkr button i2c_i801 i2c_core serio_raw evdev joydev thermal_sys ext3 jbd mbcache dm_mod btrfs zlib_deflate crc32c libcrc32c raid1 md_mod sg hid_microsoft usbhid hid sd_mod sr_mod cdrom crc_t10dif ata_generic uhci_hcd firewire_ohci ata_piix firewire_core crc_itu_t libata ehci_hcd scsi_mod usbcore usb_common [last unloaded: scsi_wait_scan] [180059.289277] [180059.289325] Pid: 11097, comm: rm Not tainted 3.1.0+ #3 System manufacturer System Product Name/P6T DELUXE V2 [180059.289497] RIP: 0010:[a020ad3f] [a020ad3f] btrfs_print_leaf+0x28/0x766 [btrfs] [180059.289609] RSP: 0018:88031cd8db48 EFLAGS: 00010296 [180059.289664] RAX: 1600 RBX: RCX: 019f0b733000 [180059.289735] RDX: 8802cb879500 RSI: RDI: 88031cb25000 [180059.289806] RBP: 8800 R08: 88031cd8dfd8 R09: [180059.289877] R10: 003a R11: 88033fcce7f0 R12: 1600 [180059.289948] R13: 0005 R14: 88031cb25000 R15: [180059.290020] FS: 7f23410ee700() GS:88033fcc() knlGS: [180059.290092] CS: 0010 DS: ES: CR0: 8005003b [180059.290148] CR2: 0020 CR3: 00031c4c7000 CR4: 06e0 [180059.290219] DR0: DR1: DR2: [180059.290290] DR3: DR6: 0ff0 DR7: 0400 [180059.290362] Process rm (pid: 11097, threadinfo 88031cd8c000, task 88031ad76d00) [180059.290434] Stack: [180059.290483] a000 88031cb25000 019e0330b000 [180059.290682] 019e03294000 88031cd8dc60 019e0330b000 001000a8 [180059.290881] 1168a000 810f705e 019e0328a000 8802cb4ec000 [180059.291081] Call Trace: [180059.291134] [810f705e] ? kmem_cache_alloc+0x2a/0xe2 [180059.291195] [a0208bae] ? __btrfs_free_extent+0x28a/0x5e8 [btrfs] [180059.291253] [810f6a64] ? __slab_free+0xdb/0x245 [180059.291314] [a02095d2] ? run_clustered_refs+0x6c6/0x716 [btrfs] [180059.291376] [a02096ef] ? btrfs_run_delayed_refs+0xcd/0x16c [btrfs] [180059.291454] [a0215610] ? __btrfs_end_transaction+0x83/0x1e2 [btrfs] [180059.291532] [a021e9cb
Re: Segmentation Faults
bc 00 00 00 00 00 16 00 00 4c 89 e0 55 48 bd 00 00 00 00 00 88 ff ff 53 48 89 f3 48 83 ec 58 [180059.293313] 03 46 20 48 c1 f8 06 48 c1 e0 0c 8b 44 28 60 89 44 24 2c e8 [180059.294084] RIP [a020ad3f] btrfs_print_leaf+0x28/0x766 [btrfs] [180059.294178] RSP 88031cd8db48 [180059.294230] CR2: 0020 [180059.294286] ---[ end trace a7d81066cd58d1c9 ]--- On Tue, Nov 22, 2011 at 8:14 PM, Liu Bo liubo2...@cn.fujitsu.com wrote: On 11/23/2011 06:02 AM, Timothy Crone wrote: Okay, I got it. Dmesg had what I think you need. Some relavent commands then the trace follow. I was trying to delete my Chrome cache, because I determined that this part of the file system was possibly causing my problems. I've heard of others having issues with Chrome and btrfs. Not sure if this is related. If you figure out what is going on, I would be interested to hear back. Cheers. root@berna:~# uname -a Linux berna 3.1.1 #1 SMP Thu Nov 17 13:51:31 EST 2011 x86_64 GNU/Linux root@berna:/home/myusername/.cache# rm -rf chromium Nov 22 16:37:18 localhost kernel: [11287.116968] parent transid verify failed on 1782596403200 wanted 25633 found 44577 Nov 22 16:37:18 localhost kernel: [11287.116973] parent transid verify failed on 1782596403200 wanted 25633 found 44577 Nov 22 16:37:18 localhost kernel: [11287.116977] parent transid verify failed on 1782596403200 wanted 25633 found 44577 Nov 22 16:37:18 localhost kernel: [11287.116980] parent transid verify failed on 1782596403200 wanted 25633 found 44577 Nov 22 16:37:18 localhost kernel: [11287.116983] parent transid verify failed on 1782596403200 wanted 25633 found 44577 Nov 22 16:37:18 localhost kernel: [11287.116997] parent transid verify failed on 1782596403200 wanted 25633 found 44577 Nov 22 16:37:18 localhost kernel: [11287.116999] parent transid verify failed on 1782596403200 wanted 25633 found 44577 Nov 22 16:37:18 localhost kernel: [11287.117001] parent transid verify failed on 1782596403200 wanted 25633 found 44577 Nov 22 16:37:18 localhost kernel: [11287.117003] parent transid verify failed on 1782596403200 wanted 25633 found 44577 Nov 22 16:37:18 localhost kernel: [11287.117004] parent transid verify failed on 1782596403200 wanted 25633 found 44577 Nov 22 16:37:20 localhost kernel: [11288.764956] btrfs: corrupt leaf, slot offset bad: block=1782603522048,root=1, slot=0 Nov 22 16:37:20 localhost kernel: [11288.764979] BUG: unable to handle kernel NULL pointer dereference at 0020 Hi, I've seen that you have updated to v3.1, but I'm afraid that is not enough... Apparently the latest code can provide us more debug info(Not just a NULL pointer). Could you please update to the latest code and see what is going on? Here it is: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus thanks, liubo Nov 22 16:37:20 localhost kernel: [11288.764983] IP: [a00d8d3f] btrfs_print_leaf+0x28/0x766 [btrfs] Nov 22 16:37:20 localhost kernel: [11288.764999] PGD 313061067 PUD 31c39f067 PMD 0 Nov 22 16:37:20 localhost kernel: [11288.765001] Oops: [#1] SMP Nov 22 16:37:20 localhost kernel: [11288.765003] CPU 5 Nov 22 16:37:20 localhost kernel: [11288.765004] Modules linked in: parport_pc ppdev lp parport bridge stp rfcomm bnep xt_tcpudp ipt_LOG xt_recent nf_conntrack_ipv4 nf_defrag_ipv4 xt_state bluetooth nf_conntrack cpufreq_conservative cpufreq_userspace cpufreq_powersave xt_multiport rfkill crc16 cpufreq_stats iptable_filter mperf ip_tables x_tables binfmt_misc fuse nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc firewire_sbp2 loop nvidia(P) snd_hda_codec_analog i2c_i801 i2c_core asus_atk0110 psmouse processor tpm_tis i7core_edac edac_core pcspkr thermal_sys tpm serio_raw snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device mxm_wmi wmi snd soundcore snd_page_alloc evdev button tpm_bios joydev ext3 jbd mbcache dm_mod btrfs zlib_deflate crc32c libcrc32c raid1 md_mod sg hid_microsoft usbhid hid sr_mod cdrom sd_mod crc_t10dif ata_generic uhci_hcd ata_piix firewire_ohci e1000 libata firewire_core ehci_hcd crc_itu_t scsi_mod usbcore sky2 [last unloaded: scsi_wait_scan] Nov 22 16:37:20 localhost kernel: [11288.765038] Nov 22 16:37:20 localhost kernel: [11288.765040] Pid: 3232, comm: rm Tainted: P 3.1.1 #1 System manufacturer System Product Name/P6T DELUXE V2 Nov 22 16:37:20 localhost kernel: [11288.765042] RIP: 0010:[a00d8d3f] [a00d8d3f] btrfs_print_leaf+0x28/0x766 [btrfs] Nov 22 16:37:20 localhost kernel: [11288.765049] RSP: 0018:88031ea69b48 EFLAGS: 00010296 Nov 22 16:37:20 localhost kernel: [11288.765050] RAX: 1600 RBX: RCX: 019f0b733000 Nov 22 16:37:20 localhost kernel: [11288.765052] RDX: 8803099c5c80 RSI: RDI: 88032f91c800 Nov 22 16:37:20 localhost kernel: [11288.765053] RBP: 8800 R08: 88031ea69fd8 R09:
Re: Segmentation Faults
If you tell me the best way to generate them for you, I will do that. It doesn't seem that anything is printed to /var/log/messages, and my machine locks up pretty soon after the segfault, so I haven't been able to get a detailed stack trace. On Tue, Nov 22, 2011 at 12:14 PM, David Sterba d...@jikos.cz wrote: On Fri, Nov 18, 2011 at 07:29:52AM -0500, Timothy Crone wrote: Okay, I installed 3.1.1 and continue to oops when trying to delete a directory. Please let me know if you would like any additional information. Do you have more detailed stacktraces from the crash? david -- Timothy J. Crone Lamont-Doherty Earth Observatory Columbia University 61 Route 9W Palisades, NY 10964 Tel: 845-365-8687 http://www.fluidcontinuity.org -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Segmentation Faults
88032eaf5f60) Nov 22 16:37:20 localhost kernel: [11288.765065] Stack: Nov 22 16:37:20 localhost kernel: [11288.765065] a000 88032f91c800 019e0330b000 Nov 22 16:37:20 localhost kernel: [11288.765068] 019e03294000 88031ea69c60 019e0330b000 001000a8 Nov 22 16:37:20 localhost kernel: [11288.765070] 1168a000 810f3272 019e0328a000 880321178000 Nov 22 16:37:20 localhost kernel: [11288.765072] Call Trace: Nov 22 16:37:20 localhost kernel: [11288.765076] [810f3272] ? kmem_cache_alloc+0x2a/0xe1 Nov 22 16:37:20 localhost kernel: [11288.765083] [a00d6bae] ? __btrfs_free_extent+0x28a/0x5e8 [btrfs] Nov 22 16:37:20 localhost kernel: [11288.765089] [a00d75d2] ? run_clustered_refs+0x6c6/0x716 [btrfs] Nov 22 16:37:20 localhost kernel: [11288.765096] [a00d76ef] ? btrfs_run_delayed_refs+0xcd/0x16c [btrfs] Nov 22 16:37:20 localhost kernel: [11288.765103] [a00e3610] ? __btrfs_end_transaction+0x83/0x1e2 [btrfs] Nov 22 16:37:20 localhost kernel: [11288.765111] [a00ec9cd] ? btrfs_evict_inode+0x184/0x20d [btrfs] Nov 22 16:37:20 localhost kernel: [11288.765115] [81110500] ? evict+0x9a/0x14e Nov 22 16:37:20 localhost kernel: [11288.765117] [81108d6f] ? do_unlinkat+0x10a/0x15e Nov 22 16:37:20 localhost kernel: [11288.765118] [8110ac88] ? vfs_readdir+0x91/0xa7 Nov 22 16:37:20 localhost kernel: [11288.765121] [81129f63] ? fsnotify_find_inode_mark+0x23/0x2e Nov 22 16:37:20 localhost kernel: [11288.765124] [81343052] ? system_call_fastpath+0x16/0x1b Nov 22 16:37:20 localhost kernel: [11288.765125] Code: 21 26 e1 41 57 41 56 41 55 41 54 49 bc 00 00 00 00 00 16 00 00 4c 89 e0 55 48 bd 00 00 00 00 00 88 ff ff 53 48 89 f3 48 83 ec 58 Nov 22 16:37:20 localhost kernel: [11288.765140] RIP [a00d8d3f] btrfs_print_leaf+0x28/0x766 [btrfs] Nov 22 16:37:20 localhost kernel: [11288.765146] RSP 88031ea69b48 Nov 22 16:37:20 localhost kernel: [11288.765147] CR2: 0020 Nov 22 16:37:20 localhost kernel: [11288.765148] ---[ end trace 6db8d0a7667ab7d9 ]--- On Tue, Nov 22, 2011 at 1:28 PM, Timothy Crone tjcr...@gmail.com wrote: If you tell me the best way to generate them for you, I will do that. It doesn't seem that anything is printed to /var/log/messages, and my machine locks up pretty soon after the segfault, so I haven't been able to get a detailed stack trace. On Tue, Nov 22, 2011 at 12:14 PM, David Sterba d...@jikos.cz wrote: On Fri, Nov 18, 2011 at 07:29:52AM -0500, Timothy Crone wrote: Okay, I installed 3.1.1 and continue to oops when trying to delete a directory. Please let me know if you would like any additional information. Do you have more detailed stacktraces from the crash? david -- Timothy J. Crone Lamont-Doherty Earth Observatory Columbia University 61 Route 9W Palisades, NY 10964 Tel: 845-365-8687 http://www.fluidcontinuity.org -- Timothy J. Crone Lamont-Doherty Earth Observatory Columbia University 61 Route 9W Palisades, NY 10964 Tel: 845-365-8687 http://www.fluidcontinuity.org -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Segmentation Faults
Okay, I installed 3.1.1 and continue to oops when trying to delete a directory. Please let me know if you would like any additional information. I'm going to rebuild from a backup later today. Cheers,Tim On Wed, Nov 16, 2011 at 6:00 PM, David Sterba d...@jikos.cz wrote: Hi, On Wed, Nov 16, 2011 at 04:39:21PM +, Tim Crone wrote: root@berna:~# uname -a Linux berna 2.6.38-bpo.2-amd64 #1 SMP Mon Jun 6 15:24:02 UTC 2011 x86_64 GNU/Linux 2.6.38 is quite old from btrfs perspective and it's highly possible that the bug you've hit is already fixed. Try newer (like 3.1) kernel and if you still hit some sort of crash, please send the report. root@berna:/home/tjc# rm -rf .cache/chromium Segmentation fault root@berna:/home/tjc# Message from syslogd@localhost at Nov 16 11:19:35 ... kernel:[ 66.877568] [ cut here ] Message from syslogd@localhost at Nov 16 11:19:35 ... kernel:[ 66.877572] invalid opcode: [#1] SMP Message from syslogd@localhost at Nov 16 11:19:35 ... kernel:[ 66.877573] last sysfs file: /sys/devices/virtual/block/md0/uevent Message from syslogd@localhost at Nov 16 11:19:35 ... kernel:[ 66.877633] Stack: Message from syslogd@localhost at Nov 16 11:19:35 ... kernel:[ 66.877640] Call Trace: Message from syslogd@localhost at Nov 16 11:19:35 ... kernel:[ 66.877703] Code: 24 24 48 8b 74 24 28 48 8d 54 24 50 41 b9 01 00 00 00 48 89 d9 4c 89 e7 e8 80 6e ff ff 83 f8 00 41 89 c5 0f 8c c5 02 00 00 74 04 0f 0b eb fe 4c 8b 2b 8b 73 40 4c 89 ef e8 a3 e5 ff ff 41 89 c6 btw such output is printed to every console when the crash occurs, but lacks important information like stacktrace and names of functions. without that it's very hard to get a clue what happened. (I was going to include some log entries, but the lines are longer than 80 characters and your system will not accept them.) As for stacktrace and line length, I personally want to see the lines not wrapped at 80 (except the eg. byte dump of instructions), it helps readability. david -- Timothy J. Crone Lamont-Doherty Earth Observatory Columbia University 61 Route 9W Palisades, NY 10964 Tel: 845-365-8687 http://www.fluidcontinuity.org -- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
