linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Robert Munteanu <robert.munteanu@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs partition converted from ext4 becomes read-only minutes after booting: WARNING: CPU: 2 PID: 2777 at ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120
Date: Wed, 17 Jun 2015 10:46:30 -0700	[thread overview]
Message-ID: <20150617174630.GM16468@merlins.org> (raw)
In-Reply-To: <CAC8ULPYHuqsZN1Lm_2TxGMw7z6n=4zAprqYr9uoi=3kjoiSxQw@mail.gmail.com>

On Fri, Jun 12, 2015 at 03:19:06PM +0300, Robert Munteanu wrote:
> Hi,
 
Note to others: kernel 4.0.4

Reply to you:
I tried ext4 to btrfs once a year ago and it severely mangled my
filesystem.
I looked at it as a cool feature/hack that may have worked some time ago, but
that no one really uses anymore, and that may not work right at this
point.

Unless you hear back from a developer interested in debugging/fixing
this, I would assume that this feature is broken and dead.

Marc

> I have converted my root ext4 partition to btrfs. I used an USB stick
> to boot and used btrfs-convert.
> 
> I also did a balance and defrag ( in that order ) , both when the fs
> was mounted.
> 
> After logging in to KDE I quickly get a read-only filesystem. I've
> pasted the backtrace below
> 
> Jun 11 23:13:08 mars kernel: WARNING: CPU: 2 PID: 2777 at
> ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120 [btrfs]()
> Jun 11 23:13:08 mars kernel: BTRFS: Transaction aborted (error -95)
> Jun 11 23:13:08 mars kernel: Modules linked in: bnep bluetooth rfkill
> fuse vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) af_packet
> nf_log_ipv6 xt_pkttype nf_log_ip
> v4 nf_log_common xt_LOG xt_limit ip6t_REJECT xt_tcpudp
> nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT iptable_raw
> xt_CT iptable_filter ip6table_mangle nf_con
> ntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4
> nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter
> ip6_tables x_tables xfs libcrc32c snd_hda
> _codec_hdmi raid1 md_mod gpio_ich ppdev iTCO_wdt iTCO_vendor_support
> coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel
> snd_hda_intel dm_mod kvm snd_hda_co
> ntroller snd_hda_codec snd_hwdep serio_raw pcspkr snd_pcm i2c_i801
> snd_seq joydev snd_seq_device snd_timer snd 8250_fintek parport_pc
> parport acpi_cpufreq lpc_ich
> Jun 11 23:13:08 mars kernel:  soundcore mfd_core shpchp processor
> ata_generic btrfs hid_logitech_hidpp xor raid6_pq sr_mod cdrom
> nvidia_uvm(PO) nvidia(PO) firewire_ohc
> i firewire_core crc_itu_t uas usb_storage r8169 mii pata_jmicron
> hid_logitech_dj drm button sg
> Jun 11 23:13:08 mars kernel: CPU: 2 PID: 2777 Comm: kworker/u8:0
> Tainted: P           O    4.0.4-3-desktop #1
> Jun 11 23:13:08 mars kernel: Hardware name: Gigabyte Technology Co.,
> Ltd. EP35-DS4/EP35-DS4, BIOS F6d 01/08/2009
> Jun 11 23:13:08 mars kernel: Workqueue: btrfs-endio-write
> btrfs_endio_write_helper [btrfs]
> Jun 11 23:13:08 mars kernel:  0000000000000000 ffffffffa0a92832
> ffffffff8167c4aa ffff880128513ca8
> Jun 11 23:13:08 mars kernel:  ffffffff81063bb1 ffff880031929d28
> ffff880221e71800 00000000ffffffa1
> Jun 11 23:13:08 mars kernel:  ffffffffa0a914e0 0000000000000b50
> ffffffff81063c2a ffffffffa0a95928
> Jun 11 23:13:08 mars kernel: Call Trace:
> Jun 11 23:13:08 mars kernel:  [<ffffffff8100574c>] dump_trace+0x8c/0x340
> Jun 11 23:13:08 mars kernel:  [<ffffffff81005aa3>] show_stack_log_lvl+0xa3/0x190
> Jun 11 23:13:08 mars kernel:  [<ffffffff81007201>] show_stack+0x21/0x50
> Jun 11 23:13:08 mars kernel:  [<ffffffff8167c4aa>] dump_stack+0x47/0x67
> Jun 11 23:13:08 mars kernel:  [<ffffffff81063bb1>]
> warn_slowpath_common+0x81/0xb0
> Jun 11 23:13:08 mars kernel:  [<ffffffff81063c2a>] warn_slowpath_fmt+0x4a/0x50
> Jun 11 23:13:08 mars kernel:  [<ffffffffa09e598b>]
> __btrfs_abort_transaction+0x4b/0x120 [btrfs]
> Jun 11 23:13:08 mars kernel:  [<ffffffffa0a1d18a>]
> btrfs_finish_ordered_io+0x5aa/0x620 [btrfs]
> Jun 11 23:13:08 mars kernel:  [<ffffffffa0a43253>]
> normal_work_helper+0xc3/0x320 [btrfs]
> Jun 11 23:13:08 mars kernel:  [<ffffffff8107bcf2>] process_one_work+0x142/0x420
> Jun 11 23:13:08 mars kernel:  [<ffffffff8107c0e4>] worker_thread+0x114/0x460
> Jun 11 23:13:08 mars kernel:  [<ffffffff81081261>] kthread+0xc1/0xe0
> Jun 11 23:13:08 mars kernel:  [<ffffffff81682d58>] ret_from_fork+0x58/0x90
> Jun 11 23:13:08 mars kernel: ---[ end trace 4c4eb7d6e98afa91 ]---
> Jun 11 23:13:08 mars kernel: BTRFS: error (device sda1) in
> btrfs_finish_ordered_io:2896: errno=-95 unknown
> Jun 11 23:13:08 mars kernel: BTRFS info (device sda1): forced readonly
> 
> Some diagnostic info:
> 
> - btrfs scrub reports no errors
> - on the host machine I'm running btrfs v4.0+20150429 and kernel 4.0.4-3-desktop
> - on the live medium, used to run btrfs-convert, I was running btrfs
> v4.0+20150429 and kernel 4.0.3-1-default
> 
> # btrfs fi show
> Label: none  uuid: 54dea125-74cd-4bb2-86a2-f7bc645b76cf
>         Total devices 1 FS bytes used 90.22GiB
>         devid    1 size 223.57GiB used 92.03GiB path /dev/sda1
> 
> btrfs-progs v4.0+20150429
> 
> # btrfs fi df /
> Data, single: total=89.00GiB, used=88.17GiB
> System, single: total=32.00MiB, used=16.00KiB
> Metadata, single: total=3.00GiB, used=2.05GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
> 
> Is there a way out? I still have the old ext4 image and can revert,
> but I'm keeping the btrfs one for now, in case I can extract some
> useful debugging information from it.
> 
> Thanks,
> 
> Robert
> 
> 
> -- 
> http://robert.muntea.nu/
> --
> 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
> 

-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  reply	other threads:[~2015-06-17 17:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12 12:19 btrfs partition converted from ext4 becomes read-only minutes after booting: WARNING: CPU: 2 PID: 2777 at ../fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120 Robert Munteanu
2015-06-17 17:46 ` Marc MERLIN [this message]
2015-06-17 19:41   ` Marc Joliet
2015-06-18 11:05   ` Robert Munteanu
2015-06-25  4:16     ` Marc MERLIN
2015-06-25 12:08       ` Vytautas D
     [not found]         ` <CABE5tBasBsycy_+q=RZj1dpqsLTREJTA72F-ZwNLt=kLX6wXhg@mail.gmail.com>
2015-06-25 21:09           ` Marc MERLIN
2015-06-17 18:48 ` Jeff Mahoney
2015-06-18 11:08   ` Robert Munteanu
2015-06-26  1:54 ` Qu Wenruo
2015-06-26  2:08   ` Qu Wenruo
2015-07-09  3:09     ` Chris Murphy
2015-07-09 10:52       ` Vytautas D
     [not found]       ` <CAO5K3OcA1_Z4-jvv_2C0StBkOr++_vUX4kOspY8cuhnX2t3z_A@mail.gmail.com>
2015-07-09 21:38         ` Chris Murphy
2015-07-10  0:34           ` Qu Wenruo
2015-07-10  0:45             ` Chris Murphy
2015-07-10  4:45               ` Qu Wenruo
2015-07-14 23:29                 ` Chris Murphy
2015-07-26 21:47             ` Robert Munteanu
2015-07-30 13:16               ` Robert Munteanu
2015-07-31  2:08                 ` Qu Wenruo
2015-07-31 13:38                   ` Robert Munteanu
2015-08-03  0:54                     ` Qu Wenruo
2015-08-03  1:22                     ` Qu Wenruo
2015-08-03  7:45                       ` Robert Munteanu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150617174630.GM16468@merlins.org \
    --to=marc@merlins.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=robert.munteanu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).