Hello all, I recently had a power failure and can no longer mount my /home directory. The harddrive has two BTRFS partitions: sda7(/) and sda8(/home). The / partition loads up just fine, but /home does not. I''ve tried btrfsck as shown below and I''ve included dmesg pertaining to btrfs. This is on ArchLinux and the software versions are as follows: btrfs-progs-unstable 0.19.20101006-1 linux 3.0 I actually have quite a bit of data on this partition that I would rather not lose. Please help! Thanks, Adam btrfsck /dev/sda8: found 152764059648 bytes used err is 1 total csum bytes: 148756860 total tree bytes: 436686848 total fs tree bytes: 160870400 btree space waste bytes: 110424811 file data blocks allocated: 4925582483456 referenced 114231959552 Btrfs Btrfs v0.19 root 5 inode 738980 errors 400 root 5 inode 771936 errors 400 root 5 inode 771937 errors 400 root 5 inode 771938 errors 400 root 5 inode 771939 errors 400 root 5 inode 771941 errors 400 root 5 inode 771942 errors 400 dmesg |grep btrfs [ 15.148281] btrfs: unlinked 13 orphans [ 27.156006] kernel BUG at fs/btrfs/inode.c:4586! [ 27.156124] Modules linked in: vboxnetflt vboxdrv snd_hda_codec_hdmi joydev usbhid hid snd_hda_codec_idt snd_hda_intel snd_hda_codec sdhci_pci sdhci psmouse snd_pcm snd_hwdep btusb firewire_ohci bluetooth crc16 dell_wmi sg nvidia(P) firewire_core arc4 snd_timer evdev serio_raw sparse_keymap i2c_i801 iwlagn mmc_core snd battery video soundcore intel_ips wmi ppdev dell_laptop parport_pc container button ac mac80211 cfg80211 pcspkr rfkill parport dcdbas iTCO_wdt i2c_core crc_itu_t iTCO_vendor_support intel_agp snd_page_alloc processor intel_gtt e1000e btrfs zlib_deflate crc32c libcrc32c ext2 mbcache ehci_hcd usbcore sr_mod cdrom sd_mod ahci libahci libata scsi_mod [ 27.157096] RIP: 0010:[<ffffffffa010b781>] [<ffffffffa010b781>] btrfs_add_link+0x161/0x1c0 [btrfs] [ 27.158176] [<ffffffffa013482f>] add_inode_ref+0x30f/0x3d0 [btrfs] [ 27.158245] [<ffffffffa013567b>] replay_one_buffer+0x2bb/0x3b0 [btrfs] [ 27.158318] [<ffffffffa0122f27>] ? alloc_extent_buffer+0x87/0x3d0 [btrfs] [ 27.158391] [<ffffffffa0132cd1>] walk_down_log_tree+0x391/0x540 [btrfs] [ 27.160851] [<ffffffffa0132f7d>] walk_log_tree+0xfd/0x270 [btrfs] [ 27.165784] [<ffffffffa0136d11>] btrfs_recover_log_trees+0x211/0x300 [btrfs] [ 27.168297] [<ffffffffa01353c0>] ? replay_one_dir_item+0xe0/0xe0 [btrfs] [ 27.170832] [<ffffffffa00fd907>] open_ctree+0x13e7/0x17a0 [btrfs] [ 27.178506] [<ffffffffa00d879e>] btrfs_mount+0x40e/0x5c0 [btrfs] [ 27.212137] RIP [<ffffffffa010b781>] btrfs_add_link+0x161/0x1c0 [btrfs] -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Aug 03, 2011 at 04:46:01PM -0400, Adam Newby wrote:> I recently had a power failure and can no longer mount my /home > directory. The harddrive has two BTRFS partitions: sda7(/) and > sda8(/home). The / partition loads up just fine, but /home does > not. I''ve tried btrfsck as shown below and I''ve included dmesg > pertaining to btrfs. This is on ArchLinux and the software versions > are as follows: > btrfs-progs-unstable 0.19.20101006-1 > linux 3.0Try the instructions on the wiki at [1]. (And please feed back and/or fix any issues you have with the instructions -- they''re still quite new and probably have awkward corners).> I actually have quite a bit of data on this partition that I would > rather not lose. Please help!You *really* need to think about making good backups (otherwise we''ll have to set the cwillu on you). Hugo. [1] https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_can.27t_mount_my_filesystem.2C_and_I_get_a_kernel_oops.21> Thanks, > Adam > > btrfsck /dev/sda8: > found 152764059648 bytes used err is 1 > total csum bytes: 148756860 > total tree bytes: 436686848 > total fs tree bytes: 160870400 > btree space waste bytes: 110424811 > file data blocks allocated: 4925582483456 > referenced 114231959552 > Btrfs Btrfs v0.19 > root 5 inode 738980 errors 400 > root 5 inode 771936 errors 400 > root 5 inode 771937 errors 400 > root 5 inode 771938 errors 400 > root 5 inode 771939 errors 400 > root 5 inode 771941 errors 400 > root 5 inode 771942 errors 400 > > dmesg |grep btrfs > [ 15.148281] btrfs: unlinked 13 orphans > [ 27.156006] kernel BUG at fs/btrfs/inode.c:4586! > [ 27.156124] Modules linked in: vboxnetflt vboxdrv snd_hda_codec_hdmi joydev usbhid hid snd_hda_codec_idt snd_hda_intel snd_hda_codec sdhci_pci sdhci psmouse snd_pcm snd_hwdep btusb firewire_ohci bluetooth crc16 dell_wmi sg nvidia(P) firewire_core arc4 snd_timer evdev serio_raw sparse_keymap i2c_i801 iwlagn mmc_core snd battery video soundcore intel_ips wmi ppdev dell_laptop parport_pc container button ac mac80211 cfg80211 pcspkr rfkill parport dcdbas iTCO_wdt i2c_core crc_itu_t iTCO_vendor_support intel_agp snd_page_alloc processor intel_gtt e1000e btrfs zlib_deflate crc32c libcrc32c ext2 mbcache ehci_hcd usbcore sr_mod cdrom sd_mod ahci libahci libata scsi_mod > [ 27.157096] RIP: 0010:[<ffffffffa010b781>] [<ffffffffa010b781>] btrfs_add_link+0x161/0x1c0 [btrfs] > [ 27.158176] [<ffffffffa013482f>] add_inode_ref+0x30f/0x3d0 [btrfs] > [ 27.158245] [<ffffffffa013567b>] replay_one_buffer+0x2bb/0x3b0 [btrfs] > [ 27.158318] [<ffffffffa0122f27>] ? alloc_extent_buffer+0x87/0x3d0 [btrfs] > [ 27.158391] [<ffffffffa0132cd1>] walk_down_log_tree+0x391/0x540 [btrfs] > [ 27.160851] [<ffffffffa0132f7d>] walk_log_tree+0xfd/0x270 [btrfs] > [ 27.165784] [<ffffffffa0136d11>] btrfs_recover_log_trees+0x211/0x300 [btrfs] > [ 27.168297] [<ffffffffa01353c0>] ? replay_one_dir_item+0xe0/0xe0 [btrfs] > [ 27.170832] [<ffffffffa00fd907>] open_ctree+0x13e7/0x17a0 [btrfs] > [ 27.178506] [<ffffffffa00d879e>] btrfs_mount+0x40e/0x5c0 [btrfs] > [ 27.212137] RIP [<ffffffffa010b781>] btrfs_add_link+0x161/0x1c0 [btrfs]-- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- "You got very nice eyes, Deedee. Never noticed them --- before. They real?"
On Wed, 3 Aug 2011 16:46:01 -0400 Adam Newby <anewby@ceradyne.com> wrote:> Hello all, > > I recently had a power failure and can no longer mount my /home directory. The harddrive has two BTRFS partitions: sda7(/) and sda8(/home). The / partition loads up just fine, but /home does not. I''ve tried btrfsck as shown below and I''ve included dmesg pertaining to btrfs. This is on ArchLinux and the software versions are as follows: > btrfs-progs-unstable 0.19.20101006-1 > linux 3.0Just a question here: how come corruption after power loss is *so* common by reading this list? I mean, are there some/hidden journal flushing issues that lead to this or what? I tried to cycle my testing machines several times to test the fs consistency months ago and I never had any corruption issues so far, but it seems I just could be lucky. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Aug 3, 2011 at 3:50 PM, Hugo Mills <hugo@carfax.org.uk> wrote:> > Try the instructions on the wiki at [1]. (And please feed back > and/or fix any issues you have with the instructions -- they''re still > quite new and probably have awkward corners). > > [1] https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_can.27t_mount_my_filesystem.2C_and_I_get_a_kernel_oops.21this worked perfectly for me ... just saved my night from tedious restoration :-) im on kernel 3.0.1 -- hard poweroff led to that problem. i haven''t had any issues for some time ... im not sure what the problem was exactly, but sometimes systemd gets a little twacky and takes a year to shutdown ... guess i got a little impatient :-) anyways, thanks for the integration work! -- C Anthony -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
I have to say this solution saved me. I've lost a BTRFS partition before and this tool was not available at that time. Is this going to be making it into a kernel pull anytime soon? The only reason I mention it is because pretty much everyone I know has soured on BTRFS due to losing a partition at some point or another due to frivolous error. This seems like a fine addition to the filesystem. -----Original Message----- From: C Anthony Risinger [mailto:anthony@xtfx.me] Sent: Monday, August 08, 2011 11:54 PM To: Hugo Mills; Adam Newby; linux-btrfs@vger.kernel.org Subject: Re: BTRFS partition won't mount On Wed, Aug 3, 2011 at 3:50 PM, Hugo Mills <hugo@carfax.org.uk> wrote:> > Try the instructions on the wiki at [1]. (And please feed back > and/or fix any issues you have with the instructions -- they're still > quite new and probably have awkward corners). > > [1] > https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_can.27t_mount_my > _filesystem.2C_and_I_get_a_kernel_oops.21this worked perfectly for me ... just saved my night from tedious restoration :-) im on kernel 3.0.1 -- hard poweroff led to that problem. i haven't had any issues for some time ... im not sure what the problem was exactly, but sometimes systemd gets a little twacky and takes a year to shutdown ... guess i got a little impatient :-) anyways, thanks for the integration work! -- C Anthony NrybXǧv^){.n+{n߲)w*jgݢj/zޖ2ޙ&)ߡaGhj:+vw٥
On Tue, Aug 09, 2011 at 08:29:06AM -0400, Adam Newby wrote:> I have to say this solution saved me. I''ve lost a BTRFS partition > before and this tool was not available at that time. Is this going > to be making it into a kernel pull anytime soon? The only reason I > mention it is because pretty much everyone I know has soured on > BTRFS due to losing a partition at some point or another due to > frivolous error. This seems like a fine addition to the filesystem.My understanding is that the btrfs-zero-log tool is something of a blunt object, and shouldn''t be applied automatically, so I think it''s unlikely to go into the kernel in its current form. From what Chris implied on IRC a few days ago, if we encounter corrupt items in the log, we should drop only those items (and their dependents?), not the entire log tree. I''d guess that as people work on reducing the number of BUG_ONs in the code and passing the errors back up the stack, this will become easier to do. Until then, we do have btrfs-zero-log. (And the new recovery tool coming shortly, too). Hugo.> -----Original Message----- > From: C Anthony Risinger [mailto:anthony@xtfx.me] > Sent: Monday, August 08, 2011 11:54 PM > To: Hugo Mills; Adam Newby; linux-btrfs@vger.kernel.org > Subject: Re: BTRFS partition won''t mount > > On Wed, Aug 3, 2011 at 3:50 PM, Hugo Mills <hugo@carfax.org.uk> wrote: > > > > Try the instructions on the wiki at [1]. (And please feed back > > and/or fix any issues you have with the instructions -- they''re still > > quite new and probably have awkward corners). > > > > [1] > > https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_can.27t_mount_my > > _filesystem.2C_and_I_get_a_kernel_oops.21 > > this worked perfectly for me ... just saved my night from tedious restoration :-) > > im on kernel 3.0.1 -- hard poweroff led to that problem. i haven''t had any issues for some time ... im not sure what the problem was exactly, but sometimes systemd gets a little twacky and takes a year to shutdown ... guess i got a little impatient :-) > > anyways, thanks for the integration work! >-- === Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk == PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk --- 2 + 2 = 5, for sufficiently large values of 2. ---
On Mon, Aug 8, 2011 at 10:54 PM, C Anthony Risinger <anthony@xtfx.me> wrote:> On Wed, Aug 3, 2011 at 3:50 PM, Hugo Mills <hugo@carfax.org.uk> wrote: >> >> Try the instructions on the wiki at [1]. (And please feed back >> and/or fix any issues you have with the instructions -- they''re still >> quite new and probably have awkward corners). >> >> [1] https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#I_can.27t_mount_my_filesystem.2C_and_I_get_a_kernel_oops.21 > > this worked perfectly for me ... just saved my night from tedious > restoration :-) > > im on kernel 3.0.1 -- hard poweroff led to that problem. i haven''t > had any issues for some time ... im not sure what the problem was > exactly, but sometimes systemd gets a little twacky and takes a year > to shutdown ... guess i got a little impatient :-) > > anyways, thanks for the integration work!well i tried to shutdown again and had to force poweroff via `echo b > /proc/sysrq-trigger` (but this time it was because dbus segfaulted and i couldnt ask systemd to reboot ... `kill -INT 1` wasn''t working either, maybe all systemd related) ... the same thing happened again. i''m wondering if btrfs is causing the hang to begin with? i will watch it after i fix it tonight by making systemd more verbose and see what it has to say. im wondering: ) what else i could try to determine if btrfs is contributing to the issue ) any other more graceful options than `echo b > /proc/sysrq-trigger` exist thanks, -- C Anthony -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html