Corrupt filesystem after power failure
Hi, I am using btrfs on my /home successfully for a while now. After a power failure I am no longer able to mount it. I tried to use btrfsck without any success. The backup I have is about a month old, is there a way I can salvage my files?. Full backtrace is at http://pastebin.com/4Re7tVFP I am aware of the danger of dataloss and wanted to change the filesystem. Anyway it's too late now Anil -- 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: Corrupt filesystem after power failure
I'm far from an expert here, but perhaps you would be worth trying a newer version of the BTRFS drivers, either via a newer kernel or re-compiling a kernel with updated BTRFS patches. I would think that the simplest quick test to see if this would help you would be to get a snapshot from Ubuntu's daily build live CD iso, and try mounting the filesystem with that... since it will have a recent RC of 2.6.38 kernel which has a much more recent BTRFS version than the 2.6.34 which you are using. http://cdimage.ubuntu.com/daily-live/current/ YMMV, but it's certainly something else to try. James. On Thu, 2011-02-10 at 22:29 +1100, Anil Kumar wrote: Hi, I am using btrfs on my /home successfully for a while now. After a power failure I am no longer able to mount it. I tried to use btrfsck without any success. The backup I have is about a month old, is there a way I can salvage my files?. Full backtrace is at http://pastebin.com/4Re7tVFP I am aware of the danger of dataloss and wanted to change the filesystem. Anyway it's too late now Anil -- 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 -- 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: Corrupt filesystem after power failure
On Thu, Feb 10, 2011 at 10:29:41PM +1100, Anil Kumar wrote: Full backtrace is at http://pastebin.com/4Re7tVFP Pastebins aren't archived. For posterity, here it is: Feb 10 21:57:36 linux-wuce kernel: [ 337.522818] Btrfs loaded Feb 10 21:57:36 linux-wuce kernel: [ 337.538044] device fsid d0485eeb5612434f-456b063393781ea9 devid 1 transid 131812 /dev/sda7 Message from syslogd@linux-wuce at Feb 10 21:57:40 ... kernel:[ 341.616905] [ cut here ] Message from syslogd@linux-wuce at Feb 10 21:57:40 ... kernel:[ 341.616919] invalid opcode: [#1] PREEMPT SMP Message from syslogd@linux-wuce at Feb 10 21:57:40 ... kernel:[ 341.616926] last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:32/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/voltage_now Message from syslogd@linux-wuce at Feb 10 21:57:40 ... kernel:[ 341.617148] Stack: Message from syslogd@linux-wuce at Feb 10 21:57:40 ... kernel:[ 341.617173] Call Trace: Message from syslogd@linux-wuce at Feb 10 21:57:40 ... kernel:[ 341.617866] Code: f4 52 96 e0 31 c0 48 81 c4 98 00 00 00 5b 5d 41 5c 41 5d 41 5e 41 5f c3 b8 fe ff ff ff eb e7 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 0f 0b 66 66 2e 0f 1f 84 00 00 00 00 00 48 81 ec 28 01 00 00 48 Feb 10 21:57:40 linux-wuce kernel: [ 341.616905] [ cut here ] Feb 10 21:57:40 linux-wuce kernel: [ 341.616912] kernel BUG at /usr/src/packages/BUILD/kernel-desktop-2.6.34.7/linux-2.6.34/fs/btrfs/tree-log.c:813! Feb 10 21:57:40 linux-wuce kernel: [ 341.616919] invalid opcode: [#1] PREEMPT SMP Feb 10 21:57:40 linux-wuce kernel: [ 341.616926] last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:32/PNP0C09:00/PNP0C0A:00/power_supply/BAT0/voltage_now Feb 10 21:57:40 linux-wuce kernel: [ 341.616932] CPU 0 Feb 10 21:57:40 linux-wuce kernel: [ 341.616935] Modules linked in: btrfs zlib_deflate crc32c libcrc32c arc4 ecb ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit af_packet vmsync vmblock snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd vboxdrv ip6t_REJECT nf_conntrack_ipv6 ip6table_raw xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq mperf ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter ip6_tables x_tables vfat fat fuse loop dm_mod snd_hda_codec_intelhdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore sr_mod iTCO_wdt usb_storage r8192se_pci atl1c iTCO_vendor_support cdrom sg pcspkr acer_wmi snd_page_alloc i2c_i801 battery ac joydev rfkill wmi ext4 jbd2 crc16 sd_mod i915 ahci libata drm_kms_helper scsi_mod drm i2c_algo_bit video intel_agp button fan thermal processor thermal_sys [last unloaded: preloadtrace] Feb 10 21:57:40 linux-wuce kernel: [ 341.617054] Feb 10 21:57:40 linux-wuce kernel: [ 341.617060] Pid: 7628, comm: mount Not tainted 2.6.34.7-0.7-desktop #1 E7214 /E7214 Feb 10 21:57:40 linux-wuce kernel: [ 341.617065] RIP: 0010:[a07d5eb3] [a07d5eb3] add_inode_ref+0x4a3/0x4b0 [btrfs] Feb 10 21:57:40 linux-wuce kernel: [ 341.617094] RSP: 0018:8800b09af8b8 EFLAGS: 00010246 Feb 10 21:57:40 linux-wuce kernel: [ 341.617098] RAX: RBX: 0097 RCX: Feb 10 21:57:40 linux-wuce kernel: [ 341.617103] RDX: 0002 RSI: 880074374820 RDI: 8800b0d9a280 Feb 10 21:57:40 linux-wuce kernel: [ 341.617107] RBP: 0002 R08: R09: ff6dc8d155c6ee03 Feb 10 21:57:40 linux-wuce kernel: [ 341.617112] R10: R11: R12: 8800b09afb78 Feb 10 21:57:40 linux-wuce kernel: [ 341.617116] R13: 88007215db50 R14: 0009 R15: 8800b09af9d8 Feb 10 21:57:40 linux-wuce kernel: [ 341.617121] FS: 7fb2eddb07e0() GS:880001e0() knlGS: Feb 10 21:57:40 linux-wuce kernel: [ 341.617126] CS: 0010 DS: ES: CR0: 8005003b Feb 10 21:57:40 linux-wuce kernel: [ 341.617131] CR2: 7f01f58e5020 CR3: b1d7f000 CR4: 06f0 Feb 10 21:57:40 linux-wuce kernel: [ 341.617135] DR0: DR1: DR2: Feb 10 21:57:40 linux-wuce kernel: [ 341.617140] DR3: DR6: 0ff0 DR7: 0400 Feb 10 21:57:40 linux-wuce kernel: [ 341.617145] Process mount (pid: 7628, threadinfo 8800b09ae000, task 8800b1dca540) Feb 10 21:57:40 linux-wuce kernel: [ 341.617148] Stack: Feb 10 21:57:40 linux-wuce kernel: [ 341.617151] a079a930 88007215db50 Feb 10 21:57:40 linux-wuce kernel: [ 341.617158] 0 8800b17fe000 88007e035eb0 8800b5991000 0009 Feb 10 21:57:40 linux-wuce kernel: [ 341.617165] 0 8800b09af9b8 880074374d78 88007215db50 0004 Feb 10
