Fwd: Can't mount btrfs raid1
Hi, Same error when mouting with this fedora iso, with mount, mount -o recovery and mount -o ro,recovery # [ 682.954511] BTRFS info (device sdc2): disk space caching is enabled [ 682.954518] BTRFS info (device sdc2): has skinny extents [ 691.321125] BTRFS critical (device sdc2): corrupt leaf, bad key order: block=1957998690304,root=1, slot=29 [ 691.321156] [ cut here ] [ 691.321203] WARNING: CPU: 3 PID: 3502 at fs/btrfs/extent-tree.c:6957 __btrfs_free_extent.isra.68+0x79c/0xca0 [btrfs] [ 691.321204] BTRFS: Transaction aborted (error -5) [ 691.321206] Modules linked in: fuse nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_security ip6table_mangle iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_security iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables ir_lirc_codec snd_hda_codec_realtek lirc_dev snd_hda_codec_generic rc_rc6_mce snd_hda_codec_hdmi coretemp mceusb snd_hda_intel rc_core i2c_algo_bit kvm_intel snd_hda_codec ttm ppdev joydev kvm snd_hda_core drm_kms_helper snd_hwdep irqbypass drm snd_seq snd_seq_device snd_pcm snd_timer snd soundcore parport_pc shpchp wmi parport video nv_tco [ 691.321276] acpi_cpufreq i2c_nforce2 tpm_tis tpm_tis_core tpm nfsd auth_rpcgss nfs_acl lockd grace nls_utf8 isofs squashfs btrfs ata_generic pata_acpi xor raid6_pq serio_raw 8021q garp stp llc mrp firewire_ohci forcedeth firewire_core pata_jmicron crc_itu_t fjes hid_logitech_hidpp hid_logitech ff_memless hid_logitech_dj sunrpc scsi_transport_iscsi loop [ 691.321310] CPU: 3 PID: 3502 Comm: mount Not tainted 4.8.0-0.rc7.git1.1.fc26.x86_64 #1 [ 691.321311] Hardware name: Gigabyte Technology Co., Ltd. GA-E7AUM-DS2H/GA-E7AUM-DS2H, BIOS F2 12/17/2008 [ 691.321314] 0286 2c34a0c3 a37a76593688 8f466ff3 [ 691.321318] a37a765936d8 a37a765936c8 8f0ae7ab [ 691.321322] 1b2d0246 01c81f86 fffb a379a9209000 [ 691.321326] Call Trace: [ 691.321331] [] dump_stack+0x86/0xc3 [ 691.321333] [] __warn+0xcb/0xf0 [ 691.321335] [] warn_slowpath_fmt+0x5f/0x80 [ 691.321351] [] __btrfs_free_extent.isra.68+0x79c/0xca0 [btrfs] [ 691.321366] [] ? __btrfs_run_delayed_refs+0x195/0x1780 [btrfs] [ 691.321383] [] __btrfs_run_delayed_refs+0xc62/0x1780 [btrfs] [ 691.321399] [] btrfs_run_delayed_refs+0xa1/0x2d0 [btrfs] [ 691.321417] [] btrfs_commit_transaction+0x52/0xb40 [btrfs] [ 691.321420] [] ? rcu_read_lock_sched_held+0x45/0x80 [ 691.321423] [] ? kmem_cache_free+0x2f9/0x340 [ 691.321442] [] btrfs_recover_log_trees+0x3e8/0x480 [btrfs] [ 691.321462] [] ? replay_one_extent+0x710/0x710 [btrfs] [ 691.321480] [] open_ctree+0x237f/0x2660 [btrfs] [ 691.321494] [] btrfs_mount+0xda3/0xef0 [btrfs] [ 691.321498] [] mount_fs+0x38/0x160 [ 691.321500] [] ? alloc_vfsmnt+0x19e/0x230 [ 691.321502] [] vfs_kern_mount+0x6b/0x150 [ 691.321516] [] btrfs_mount+0x1a3/0xef0 [btrfs] [ 691.321520] [] ? lockdep_init_map+0x61/0x210 [ 691.321522] [] mount_fs+0x38/0x160 [ 691.321523] [] ? alloc_vfsmnt+0x19e/0x230 [ 691.321525] [] vfs_kern_mount+0x6b/0x150 [ 691.321527] [] do_mount+0x1dd/0xcf0 [ 691.321529] [] ? __check_object_size+0xd3/0x214 [ 691.321531] [] ? memdup_user+0x60/0x90 [ 691.321534] [] SyS_mount+0x83/0xd0 [ 691.321537] [] entry_SYSCALL_64_fastpath+0x1f/0xbd [ 691.321539] ---[ end trace 8e57b3f7e61b4de9 ]--- [ 691.321740] BTRFS: error (device sdc2) in __btrfs_free_extent:6957: errno=-5 IO failure [ 691.321752] BTRFS: error (device sdc2) in btrfs_run_delayed_refs:2960: errno=-5 IO failure [ 691.324478] BTRFS: error (device sdc2) in btrfs_replay_log:2470: errno=-5 IO failure (Failed to recover log tree) [ 691.326725] pending csums is 4096 [ 691.327863] BTRFS error (device sdc2): cleaner transaction attach returned -30 [ 691.407116] BTRFS: open_ctree failed [ 691.408577] mount (3502) used greatest stack depth: 9880 bytes left btrfs check --repair crashes : [root@new-host mnt]# btrfs check --repair /dev/sda2 enabling repair mode repair mode will force to clear out log tree, Are you sure? [y/N]: y Unable to find block group for 0 extent-tree.c:289: find_search_start: Assertion `1` failed. btrfs(+0x514da)[0x555c5edee4da] btrfs(btrfs_reserve_extent+0xa3f)[0x555c5edf34cf] btrfs(btrfs_alloc_free_block+0x5f)[0x555c5edf359f] btrfs(__btrfs_cow_block+0xc4)[0x555c5ede43d4] btrfs(btrfs_cow_block+0x35)[0x555c5ede49d5] btrfs(+0x4cf26)[0x555c5ede9f26] btrfs(btrfs_commit_transaction+0x95)[0x555c5edebd65] btrfs(cmd_check+0x843)[0x555c5edd1723] btrfs(main+0x7b)[0x555c5edad03b] /lib64/lib
Fwd: Can't mount btrfs raid1
2016-09-21 3:00 GMT+02:00 Chris Murphy : > On Tue, Sep 20, 2016 at 5:16 PM, Mirak M wrote: >> Hello, >> >> I have a failure when mounting btrfs. >> >>> mount -oro,recovery /dev/sda2 sda2_btrfs >>> mount: /dev/sda2: can't read superblock > > What do you get for 'btrfs super-recover -v ' and 'btrfs check ' I get this : ### All Devices: Device: id = 1, name = /dev/sdc2 Device: id = 2, name = /dev/sda2 Before Recovering: [All good supers]: device name = /dev/sdc2 superblock bytenr = 65536 device name = /dev/sdc2 superblock bytenr = 67108864 device name = /dev/sdc2 superblock bytenr = 274877906944 device name = /dev/sda2 superblock bytenr = 65536 device name = /dev/sda2 superblock bytenr = 67108864 device name = /dev/sda2 superblock bytenr = 274877906944 [All bad supers]: All supers are valid, no need to recover ### ### root@vdr-box:/mnt# btrfs check /dev/sda2 Checking filesystem on /dev/sda2 UUID: 64543f0e-ebb5-4384-8119-f5b6d52dea6e checking extents bad key ordering 29 30 bad block 1957998690304 Errors found in extent allocation tree or chunk allocation checking free space cache There is no free space entry for 1959033618432-859521990656 There is no free space entry for 1959033618432-1959071318016 cache appears valid but isnt 1957997576192 found 54593218 bytes used err is -22 total csum bytes: 0 total tree bytes: 1146880 total fs tree bytes: 0 total extent tree bytes: 212992 btree space waste bytes: 212465 file data blocks allocated: 453378048 referenced 453378048 ### > > For this purpose any 4.4+ version is probably OK, except 4.7 and 4.7.1 > which might spit out some bogus items (it's just noise it won't hurt > anything as long as you don't use --repair). > > >> >> The kernel log is here http://pastebin.com/tHihHT92 and at the bottom >> of the email >> >> I must admit I did the error of running btrfs check --repair at some >> point, not knowing this was not a good idea. >> >> I run ubuntu 16.04 with kernel 4.4.0-36-generic . > > OK what version of btrrfs-progs? What was the output from btrfs check? btrfs-progs v4.4 Output is above, > > >> [ 1692.712574] BTRFS critical (device sda2): corrupt leaf, bad key >> order: block=1957998690304,root=1, slot=29 >> [ 1692.712819] BTRFS critical (device sda2): corrupt leaf, bad key >> order: block=1957998690304,root=1, slot=29 > > List archives suggest this might be due to bad RAM. I also see there > are some bugs that can cause it, but I'm not finding any post kernel > 4.4 patches for this (there are a metric f tonne of changes since > 4.4). I would suggest kernel 4.4.21 if you need to stick with a long > term kernel, I have no idea what 4.4.0-36 translates into. My computer freezing a lot recently, but I though it was related to a X server problem with the radeon gpu. > > >> [ 1692.713963] BTRFS: error (device sda2) in btrfs_replay_log:2401: >> errno=-5 IO failure (Failed to recover log tree) > > This is kinda curious, was there a crash or power failure? Yes many since I upgraded to xenial and btrfs, about at the same time. only /home is on btrfs raid 1 on harddrive. The system / is on LVM+ext4 on a SSD. > > > > > -- > Chris Murphy -- 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
