* Re: btrfs_drop_snapshot "IO failure" after RAID controller reset [not found] <20170203101651.GA20944@midas.ntm-gmbh.de> @ 2017-02-03 12:57 ` Juergen 'Louis' Fluk 0 siblings, 0 replies; 3+ messages in thread From: Juergen 'Louis' Fluk @ 2017-02-03 12:57 UTC (permalink / raw) To: linux-btrfs On Fri, Feb 03, 2017 at 11:16:51AM +0100, Juergen 'Louis' Fluk wrote: > Dear all, > > the RAID controller underneath our 32T BTRFS container had a sudden reset, > and after rebooting BTRFS drops to readonly after some list of messages. > > I did recovery + btrfs-zero-log + recovery (using a LVM snapshot), yet > the error persists. From "transid verify failed" I understand that journal > and data are not in sync (data is newer). BTRFS tries to drop a snapshot > and fails there - is there a way to ignore it or force it? > > RAID controller does not signal new errors so I assume it's not a problem > of accessing some single disk block, but possibly some information was not > written to disk at the time of controller reset. ... > > mount -o recovery /dev/vg/snap /mnt/backup > > Feb 3 08:05:57 zeus kernel: [336619.494618] BTRFS info (device dm-2): enabling auto recovery > Feb 3 08:05:57 zeus kernel: [336619.494625] BTRFS info (device dm-2): disk space caching is enabled > Feb 3 08:09:32 zeus kernel: [336834.568348] BTRFS: checking UUID tree > Feb 3 08:10:44 zeus kernel: [336905.752787] BTRFS info (device dm-2): The free space cache file (814462533632) is invalid. skip it > Feb 3 08:10:44 zeus kernel: [336905.752787] > Feb 3 08:11:26 zeus kernel: [336948.358199] BTRFS (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 > Feb 3 08:11:26 zeus kernel: [336948.397901] BTRFS (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 > Feb 3 08:11:46 zeus kernel: [336968.341996] BTRFS (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 > Feb 3 08:11:46 zeus kernel: [336968.362567] BTRFS (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 > Feb 3 08:11:46 zeus kernel: [336968.406344] BTRFS: error (device dm-2) in btrfs_drop_snapshot:8367: errno=-5 IO failure > Feb 3 08:11:46 zeus kernel: [336968.418816] BTRFS info (device dm-2): forced readonly > ... > The server is running kernel 3.19.0-79-generic (ubuntu 14.04), btrfs-tools 3.12-1ubuntu0.1. > Does it make sense to use newer kernel and/or tools to recover? Running on kernel 4.4.0-62-generic now, procedure looks quite similar: mount -o recovery /dev/vg/snap /mnt/backup Feb 3 11:38:30 zeus kernel: [ 297.414369] BTRFS info (device dm-2): enabling auto recovery Feb 3 11:38:30 zeus kernel: [ 297.414375] BTRFS info (device dm-2): disk space caching is enabled Feb 3 11:41:54 zeus kernel: [ 501.145009] BTRFS: checking UUID tree Feb 3 11:43:02 zeus kernel: [ 568.938947] BTRFS info (device dm-2): The free space cache file (814462533632) is invalid. skip it Feb 3 11:43:02 zeus kernel: [ 568.938947] Feb 3 11:44:57 zeus kernel: [ 683.656849] BTRFS error (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 11:44:57 zeus kernel: [ 683.718674] BTRFS error (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 11:44:59 zeus kernel: [ 686.344684] BTRFS error (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 11:44:59 zeus kernel: [ 686.370777] BTRFS error (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 11:44:59 zeus kernel: [ 686.374094] BTRFS: error (device dm-2) in btrfs_drop_snapshot:9008: errno=-5 IO failure Feb 3 11:44:59 zeus kernel: [ 686.377772] BTRFS info (device dm-2): forced readonly umount /mnt/backup Feb 3 11:46:36 zeus kernel: [ 783.112240] BTRFS error (device dm-2): cleaner transaction attach returned -30 btrfs-zero-log /dev/vg/snap # takes 180s, no messages mount -o recovery /dev/vg/snap /mnt/backup Feb 3 11:49:35 zeus kernel: [ 961.805605] BTRFS info (device dm-2): enabling auto recovery Feb 3 11:49:35 zeus kernel: [ 961.805611] BTRFS info (device dm-2): disk space caching is enabled Feb 3 11:53:03 zeus kernel: [ 1170.373099] BTRFS: checking UUID tree Feb 3 11:54:12 zeus kernel: [ 1238.660425] BTRFS error (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 11:54:12 zeus kernel: [ 1238.807281] BTRFS error (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 11:54:25 zeus kernel: [ 1252.132065] BTRFS error (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 11:54:25 zeus kernel: [ 1252.422404] BTRFS error (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 11:54:25 zeus kernel: [ 1252.425953] BTRFS: error (device dm-2) in btrfs_drop_snapshot:9008: errno=-5 IO failure Feb 3 11:54:25 zeus kernel: [ 1252.429649] BTRFS info (device dm-2): forced readonly Feb 3 11:59:14 zeus kernel: [ 1541.593077] BTRFS warning (device dm-2): btrfs_uuid_scan_kthread failed -30 Feb 3 12:00:28 zeus kernel: [ 1614.931233] BTRFS error (device dm-2): parent transid verify failed on 4052043694080 wanted 451805 found 451973 Feb 3 12:00:28 zeus kernel: [ 1615.014242] BTRFS error (device dm-2): parent transid verify failed on 4052043694080 wanted 451805 found 451973 Feb 3 12:00:34 zeus kernel: [ 1621.247906] BTRFS error (device dm-2): parent transid verify failed on 4050351652864 wanted 451804 found 451973 Feb 3 12:00:34 zeus kernel: [ 1621.259342] BTRFS error (device dm-2): parent transid verify failed on 4050351652864 wanted 451804 found 451973 Feb 3 12:00:40 zeus kernel: [ 1626.875601] BTRFS error (device dm-2): parent transid verify failed on 4052066533376 wanted 451806 found 451974 Feb 3 12:00:40 zeus kernel: [ 1627.015048] BTRFS error (device dm-2): parent transid verify failed on 4052066533376 wanted 451806 found 451974 Feb 3 12:00:46 zeus kernel: [ 1632.837738] BTRFS error (device dm-2): parent transid verify failed on 4051971883008 wanted 451804 found 451973 Feb 3 12:00:46 zeus kernel: [ 1632.884797] BTRFS error (device dm-2): parent transid verify failed on 4051971883008 wanted 451804 found 451973 Feb 3 12:00:47 zeus kernel: [ 1634.432228] BTRFS error (device dm-2): parent transid verify failed on 4050367676416 wanted 451804 found 451973 Feb 3 12:00:47 zeus kernel: [ 1634.551432] BTRFS error (device dm-2): parent transid verify failed on 4050367676416 wanted 451804 found 451973 Feb 3 12:00:51 zeus kernel: [ 1637.714149] BTRFS error (device dm-2): parent transid verify failed on 4052133838848 wanted 451807 found 451974 Feb 3 12:00:51 zeus kernel: [ 1637.768666] BTRFS error (device dm-2): parent transid verify failed on 4052133838848 wanted 451807 found 451974 Feb 3 12:00:51 zeus kernel: [ 1638.554131] BTRFS error (device dm-2): parent transid verify failed on 4051397328896 wanted 451804 found 451973 Feb 3 12:00:52 zeus kernel: [ 1638.665906] BTRFS error (device dm-2): parent transid verify failed on 4051397328896 wanted 451804 found 451973 Feb 3 12:00:52 zeus kernel: [ 1639.356236] BTRFS error (device dm-2): parent transid verify failed on 4052072022016 wanted 451806 found 451974 Feb 3 12:00:52 zeus kernel: [ 1639.437114] BTRFS error (device dm-2): parent transid verify failed on 4052072022016 wanted 451806 found 451974 Feb 3 12:05:33 zeus kernel: [ 1920.132049] INFO: task btrfs-transacti:8053 blocked for more than 120 seconds. Feb 3 12:07:33 zeus kernel: [ 2040.156049] INFO: task btrfs-transacti:8053 blocked for more than 120 seconds. Feb 3 12:09:33 zeus kernel: [ 2160.164049] INFO: task btrfs-transacti:8053 blocked for more than 120 seconds. Feb 3 12:11:33 zeus kernel: [ 2280.180054] INFO: task btrfs-transacti:8053 blocked for more than 120 seconds. umount /mnt/backup Feb 3 12:55:37 zeus kernel: [ 4924.048310] BTRFS error (device dm-2): cleaner transaction attach returned -30 mount /dev/vg/snap /backup Feb 3 12:55:45 zeus kernel: [ 4932.561424] BTRFS info (device dm-2): disk space caching is enabled Feb 3 12:59:04 zeus kernel: [ 5130.898771] BTRFS: checking UUID tree Feb 3 12:59:34 zeus kernel: [ 5160.957529] BTRFS error (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 12:59:34 zeus kernel: [ 5160.994059] BTRFS error (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 12:59:34 zeus kernel: [ 5160.996986] BTRFS: error (device dm-2) in btrfs_drop_snapshot:9008: errno=-5 IO failure Feb 3 12:59:34 zeus kernel: [ 5161.000282] BTRFS info (device dm-2): forced readonly Feb 3 13:00:36 zeus kernel: [ 5223.300104] BTRFS warning (device dm-2): btrfs_uuid_scan_kthread failed -30 So the OOPS after btrfs-zero-log is gone, and we reduced to a single "parent transid verify failed" and just "btrfs_drop_snapshot:9008: errno=-5 IO failure". louis -- Jürgen 'Louis' Fluk Linux Information Systems AG Thomas-Dehler-Str. 9, 81737 München Fon: +49 89 993412-21, Fax: +49 89 993412-99 jfluk@linux-ag.com, http://www.linux-ag.com ---------------------------------------------------------- Sitz der Gesellschaft: Thomas-Dehler-Str. 9, 81737 München Amtsgericht München: HRB 128 019 Vorstand: Rudolf Strobl Aufsichtsrat: Michael Tarabochia (Vorsitzender) *** Die bestere IT für den Mittelstand *** ^ permalink raw reply [flat|nested] 3+ messages in thread
* btrfs_drop_snapshot "IO failure" after RAID controller reset @ 2017-02-03 10:16 Juergen 'Louis' Fluk 2017-02-04 8:01 ` Duncan 0 siblings, 1 reply; 3+ messages in thread From: Juergen 'Louis' Fluk @ 2017-02-03 10:16 UTC (permalink / raw) To: linux-btrfs Dear all, the RAID controller underneath our 32T BTRFS container had a sudden reset, and after rebooting BTRFS drops to readonly after some list of messages. I did recovery + btrfs-zero-log + recovery (using a LVM snapshot), yet the error persists. From "transid verify failed" I understand that journal and data are not in sync (data is newer). BTRFS tries to drop a snapshot and fails there - is there a way to ignore it or force it? RAID controller does not signal new errors so I assume it's not a problem of accessing some single disk block, but possibly some information was not written to disk at the time of controller reset. mount -o recovery /dev/vg/snap /mnt/backup Feb 3 08:05:57 zeus kernel: [336619.494618] BTRFS info (device dm-2): enabling auto recovery Feb 3 08:05:57 zeus kernel: [336619.494625] BTRFS info (device dm-2): disk space caching is enabled Feb 3 08:09:32 zeus kernel: [336834.568348] BTRFS: checking UUID tree Feb 3 08:10:44 zeus kernel: [336905.752787] BTRFS info (device dm-2): The free space cache file (814462533632) is invalid. skip it Feb 3 08:10:44 zeus kernel: [336905.752787] Feb 3 08:11:26 zeus kernel: [336948.358199] BTRFS (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 08:11:26 zeus kernel: [336948.397901] BTRFS (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 08:11:46 zeus kernel: [336968.341996] BTRFS (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 08:11:46 zeus kernel: [336968.362567] BTRFS (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 08:11:46 zeus kernel: [336968.406344] BTRFS: error (device dm-2) in btrfs_drop_snapshot:8367: errno=-5 IO failure Feb 3 08:11:46 zeus kernel: [336968.418816] BTRFS info (device dm-2): forced readonly umount /mnt/backup Feb 3 08:14:13 zeus kernel: [337114.733143] BTRFS warning (device dm-2): page private not zero on page 4049746657280 Feb 3 08:14:13 zeus kernel: [337114.733148] BTRFS warning (device dm-2): page private not zero on page 4049746661376 Feb 3 08:14:13 zeus kernel: [337114.733151] BTRFS warning (device dm-2): page private not zero on page 4049746665472 Feb 3 08:14:13 zeus kernel: [337114.733154] BTRFS warning (device dm-2): page private not zero on page 4049746669568 btrfs-zero-log /dev/vg/snap # takes about 180s, no messages mount -o recovery /dev/vg/snap /mnt/backup Feb 3 08:17:01 zeus kernel: [337282.701412] BTRFS info (device dm-2): enabling auto recovery Feb 3 08:17:01 zeus kernel: [337282.701418] BTRFS info (device dm-2): disk space caching is enabled Feb 3 08:20:30 zeus kernel: [337492.359931] BTRFS: checking UUID tree Feb 3 08:21:01 zeus kernel: [337523.269214] BTRFS (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 08:21:01 zeus kernel: [337523.382927] BTRFS (device dm-2): parent transid verify failed on 4052030455808 wanted 451805 found 451973 Feb 3 08:26:06 zeus kernel: [337828.194444] BTRFS (device dm-2): parent transid verify failed on 4052043694080 wanted 451805 found 451973 Feb 3 08:26:06 zeus kernel: [337828.291338] BTRFS (device dm-2): parent transid verify failed on 4052043694080 wanted 451805 found 451973 Feb 3 08:26:11 zeus kernel: [337833.611569] BTRFS (device dm-2): parent transid verify failed on 4050351652864 wanted 451804 found 451973 Feb 3 08:26:12 zeus kernel: [337833.662051] BTRFS (device dm-2): parent transid verify failed on 4050351652864 wanted 451804 found 451973 Feb 3 08:26:15 zeus kernel: [337837.077964] BTRFS (device dm-2): parent transid verify failed on 4052066533376 wanted 451806 found 451974 Feb 3 08:26:15 zeus kernel: [337837.106540] BTRFS (device dm-2): parent transid verify failed on 4052066533376 wanted 451806 found 451974 Feb 3 08:26:20 zeus kernel: [337842.595882] BTRFS (device dm-2): parent transid verify failed on 4050367676416 wanted 451804 found 451973 Feb 3 08:26:21 zeus kernel: [337842.686296] BTRFS (device dm-2): parent transid verify failed on 4050367676416 wanted 451804 found 451973 Feb 3 08:26:24 zeus kernel: [337845.666495] BTRFS (device dm-2): parent transid verify failed on 4051971883008 wanted 451804 found 451973 Feb 3 08:26:24 zeus kernel: [337845.728624] BTRFS (device dm-2): parent transid verify failed on 4051971883008 wanted 451804 found 451973 Feb 3 08:26:27 zeus kernel: [337848.780978] BTRFS (device dm-2): parent transid verify failed on 4051397328896 wanted 451804 found 451973 Feb 3 08:26:27 zeus kernel: [337848.827572] BTRFS (device dm-2): parent transid verify failed on 4051397328896 wanted 451804 found 451973 Feb 3 08:26:27 zeus kernel: [337849.116946] BTRFS (device dm-2): parent transid verify failed on 4052072022016 wanted 451806 found 451974 Feb 3 08:26:27 zeus kernel: [337849.164664] BTRFS (device dm-2): parent transid verify failed on 4052072022016 wanted 451806 found 451974 Feb 3 08:26:29 zeus kernel: [337850.848836] BTRFS (device dm-2): parent transid verify failed on 4052133838848 wanted 451807 found 451974 Feb 3 08:26:29 zeus kernel: [337850.904191] BTRFS (device dm-2): parent transid verify failed on 4052133838848 wanted 451807 found 451974 Feb 3 08:56:43 zeus kernel: [339665.075509] BTRFS (device dm-2): parent transid verify failed on 4052075757568 wanted 451806 found 451974 Feb 3 08:56:43 zeus kernel: [339665.169955] BTRFS (device dm-2): parent transid verify failed on 4052075757568 wanted 451806 found 451974 Feb 3 08:56:43 zeus kernel: [339665.169960] ------------[ cut here ]------------ Feb 3 08:56:43 zeus kernel: [339665.170003] WARNING: CPU: 2 PID: 22338 at /build/linux-lts-vivid-YU4K27/linux-lts-vivid-3.19.0/fs/btrfs/super.c:260 __btrfs_abort_transaction+0x54/0x130 [btrfs]() Feb 3 08:56:43 zeus kernel: [339665.170005] BTRFS: Transaction aborted (error -5) Feb 3 08:56:43 zeus kernel: [339665.170006] Modules linked in: rpcsec_gss_krb5 nfsv4 dm_snapshot dm_bufio p4_clockmod speedstep_lib dm_crypt nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache coretemp gpio_ich kvm ppdev i5000_edac edac_core dm_multipath serio_raw scsi_dh lpc_ich i5k_amb ioatdma 8250_fintek shpchp parport_pc parport dca mac_hid e100 via_rhine 3c59x 8139too mii btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 hid_generic e1000e i2c_algo_bit ttm ptp drm_kms_helper usbhid drm pata_acpi hid arcmsr pps_core e1000 floppy [last unloaded: sata_promise] Feb 3 08:56:43 zeus kernel: [339665.170055] CPU: 2 PID: 22338 Comm: btrfs-transacti Tainted: G W 3.19.0-79-generic #87~14.04.1-Ubuntu Feb 3 08:56:43 zeus kernel: [339665.170057] Hardware name: Supermicro X7DB8/X7DB8, BIOS 6.00 08/13/2007 Feb 3 08:56:43 zeus kernel: [339665.170059] 0000000000000000 ffff880055d27958 ffffffff817b63c3 ffff880055d279a8 Feb 3 08:56:43 zeus kernel: [339665.170063] ffffffffc0380f40 ffff880055d27998 ffffffff81075d6a 0000000000000000 Feb 3 08:56:43 zeus kernel: [339665.170066] ffff88020d45ad10 ffff88020a1bc000 00000000fffffffb ffffffffc037d070 Feb 3 08:56:43 zeus kernel: [339665.170069] Call Trace: Feb 3 08:56:43 zeus kernel: [339665.170077] [<ffffffff817b63c3>] dump_stack+0x63/0x81 Feb 3 08:56:43 zeus kernel: [339665.170083] [<ffffffff81075d6a>] warn_slowpath_common+0x8a/0xc0 Feb 3 08:56:43 zeus kernel: [339665.170086] [<ffffffff81075de6>] warn_slowpath_fmt+0x46/0x50 Feb 3 08:56:43 zeus kernel: [339665.170101] [<ffffffffc02e2537>] ? update_block_group.isra.61+0xd7/0x310 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170115] [<ffffffffc02cfec4>] __btrfs_abort_transaction+0x54/0x130 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170130] [<ffffffffc02e2a63>] __btrfs_free_extent+0x2f3/0xbf0 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170149] [<ffffffffc0348e15>] ? find_ref_head+0x65/0x90 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170165] [<ffffffffc02e85e3>] __btrfs_run_delayed_refs+0x9b3/0x1270 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170183] [<ffffffffc03165a0>] ? btrfs_set_token_32+0x60/0xf0 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170200] [<ffffffffc02ed013>] btrfs_run_delayed_refs.part.66+0x73/0x270 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170216] [<ffffffffc02ed75d>] btrfs_write_dirty_block_groups+0x48d/0x6e0 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170234] [<ffffffffc0375bf6>] commit_cowonly_roots+0x17b/0x230 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170251] [<ffffffffc02fe48c>] btrfs_commit_transaction+0x4dc/0xa50 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170255] [<ffffffff810b63f0>] ? prepare_to_wait_event+0x110/0x110 Feb 3 08:56:43 zeus kernel: [339665.170272] [<ffffffffc02f9cf5>] transaction_kthread+0x1b5/0x240 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170289] [<ffffffffc02f9b40>] ? btrfs_cleanup_transaction+0x580/0x580 [btrfs] Feb 3 08:56:43 zeus kernel: [339665.170294] [<ffffffff81094bc9>] kthread+0xc9/0xe0 Feb 3 08:56:43 zeus kernel: [339665.170297] [<ffffffff81094b00>] ? kthread_create_on_node+0x1c0/0x1c0 Feb 3 08:56:43 zeus kernel: [339665.170301] [<ffffffff817bde18>] ret_from_fork+0x58/0x90 Feb 3 08:56:43 zeus kernel: [339665.170304] [<ffffffff81094b00>] ? kthread_create_on_node+0x1c0/0x1c0 Feb 3 08:56:43 zeus kernel: [339665.170306] ---[ end trace 8850f26850fef130 ]--- Feb 3 08:56:43 zeus kernel: [339665.170315] BTRFS: error (device dm-2) in __btrfs_free_extent:5990: errno=-5 IO failure Feb 3 08:56:43 zeus kernel: [339665.170330] BTRFS warning (device dm-2): btrfs_uuid_scan_kthread failed -5 Feb 3 08:56:43 zeus kernel: [339665.170333] BTRFS: error (device dm-2) in btrfs_drop_snapshot:8367: errno=-5 IO failure Feb 3 08:56:43 zeus kernel: [339665.170335] BTRFS info (device dm-2): forced readonly Feb 3 08:56:43 zeus kernel: [339665.194784] BTRFS: error (device dm-2) in btrfs_run_delayed_refs:2792: errno=-5 IO failure Feb 3 08:56:46 zeus kernel: [339668.601034] BTRFS warning (device dm-2): Skipping commit of aborted transaction. Feb 3 08:56:46 zeus kernel: [339668.601043] BTRFS: error (device dm-2) in cleanup_transaction:1670: errno=-5 IO failure The server is running kernel 3.19.0-79-generic (ubuntu 14.04), btrfs-tools 3.12-1ubuntu0.1. Does it make sense to use newer kernel and/or tools to recover? Thanx for any hint or advise :) louis -- Jürgen 'Louis' Fluk Linux Information Systems AG Thomas-Dehler-Str. 9, 81737 München jfluk@linux-ag.com, http://www.linux-ag.com ---------------------------------------------------------- Sitz der Gesellschaft: Thomas-Dehler-Str. 9, 81737 München Amtsgericht München: HRB 128 019 Vorstand: Rudolf Strobl Aufsichtsrat: Michael Tarabochia (Vorsitzender) *** Die bestere IT für den Mittelstand *** ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: btrfs_drop_snapshot "IO failure" after RAID controller reset 2017-02-03 10:16 Juergen 'Louis' Fluk @ 2017-02-04 8:01 ` Duncan 0 siblings, 0 replies; 3+ messages in thread From: Duncan @ 2017-02-04 8:01 UTC (permalink / raw) To: linux-btrfs Juergen 'Louis' Fluk posted on Fri, 03 Feb 2017 11:16:51 +0100 as excerpted: > The server is running kernel 3.19.0-79-generic (ubuntu 14.04), > btrfs-tools 3.12-1ubuntu0.1. > Does it make sense to use newer kernel and/or tools to recover? I'm not a dev, just a list regular and btrfs user, but I can answer this part. =:^) General list policy is that btrfs is still under heavy development and stabilization, not fully stable and mature. And we're focused on forward development, not history. As such, staying /relatively/ current is strongly recommended. For the kernel, we best support the last two kernel release series in one of two tracks, current or LTS. On the LTS track, that's 4.4 and 4.1. On the current track, 4.9 is out and 4.10 is getting close, so it's currently 4.9 and 4.8, but will soon be 4.10 and 4.9. For the btrfs userspace (btrfs-progs), during normal operation it's the kernel doing most of the work, with userspace simply calling the kernel to do it, so userspace doesn't matter quite so much as long as it supports the features you are using. However, once something goes wrong and you're trying to recover, userspace code gets its workout, so that's when you need newer userspace. However, get /too/ far out of date and the commands have changed enough that someone, either user side or helper side, has to translate between old form and new form, making things harder. As a result, given that the kernel and userspace releases are version-synced, with similar versions developed with the same problems being worked on at the time, a good rule of thumb is use a userspace similar in version to your kernel space and it won't get too outdated. Now we recognize that some distros support btrfs on older code, and that's fine, but that's their support, not ours, and they're best positioned to give it, since we don't track what patches they may have backported and what not, all we see is the old version number and think how many bugs have been fixed since then. So your best bet if you want to stay with an older distro supported kernel is to actually use that distro support. Meanwhile, while kernel 3.19 isn't /too/ far back from the oldest LTS supported 4.1, the 3.12 userspace is positively /ancient/ /history/! Consider that it wasn't until 3.12 or 3.14 (I've forgotten exacty) that the experimental, might eat your kids, level label, was stripped from btrfs, and we went to heavy development but stabilizing, and you see just how bad 3.12 looks... it was basically still experimental level! So definitely, for this list, trying with something newer, at /least/ 4.1 LTS and preferably at least 4.4 LTS as it has been out for quite awhile now, should be one of the first things to try. If the problem's still there with that, then at least your posted logs, etc, will still have at least /some/ relevance to current development, not simply look like artifacts from ancient history. Or as I said, try your distro, as they're best positioned to support the longer term stuff they offer. Meanwhile, a standard point/question I make/ask when people post with such stale^H^Hble software, is whether they're actually sure they chose the best filesystem for their needs. As I said, btrfs is still under heavy development, stabilizing and maturing, and there are still critical bugs showing up from time to time, as well as continuing development challenges where existing features stil don't work as well as we'd like. By contrast, people generally choose to run such stale^H^Hble distros for their long-term stable support. That would seem to be enough of a mis- match that it's worth asking yourself whether perhaps you need to reevaluate your choices and maybe change one or the other. If you need stable and mature, btrfs isn't likely to be an appropriate choice. OTOH, if you like the new features and can live with a bit less predictability in terms of known and tested stability, then btrfs may be correct, but it would be the older "stable" distro that may be inappropriate to your needs. They just don't seem to be a particularly good match, at least for the general case. That isn't to say it's the /wrong/ choice for your particular use-case, but it's worth considering a reevaluation to be sure, if you haven't asked yourself that sort of questions, recently. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-02-04 8:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20170203101651.GA20944@midas.ntm-gmbh.de>
2017-02-03 12:57 ` btrfs_drop_snapshot "IO failure" after RAID controller reset Juergen 'Louis' Fluk
2017-02-03 10:16 Juergen 'Louis' Fluk
2017-02-04 8:01 ` Duncan
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).