From: Josef Bacik <jbacik@fusionio.com>
To: "Tóth Csaba" <tsabi@tsabi.hu>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs problem
Date: Tue, 18 Dec 2012 09:08:40 -0500 [thread overview]
Message-ID: <20121218140840.GE2403@localhost.localdomain> (raw)
In-Reply-To: <50CE3AF2.6000900@tsabi.hu>
On Sun, Dec 16, 2012 at 02:19:46PM -0700, Tóth Csaba wrote:
> Dear Community,
>
> i have a linux server with a btrfs root filesystem. After some time, or
> a specific action (i don't know what exactly) it crashes. Sometimes it
> needs some day, sometimes when i make a concrete action, like subvolume
> delete, or make a new directory, etc.
>
> this is what i see from the dmesg output:
>
> [ 7595.865982] ------------[ cut here ]------------
> [ 7595.865989] WARNING: at fs/btrfs/super.c:221
> __btrfs_abort_transaction+0xc5/0xe0()
> [ 7595.865991] Hardware name: VMware Virtual Platform
> [ 7595.865992] btrfs: Transaction aborted
> [ 7595.865993] Modules linked in:
> [ 7595.865994] ipv6 iptable_filter ip_tables x_tables 8250_pnp vmwgfx
> 8250 ttm serial_core drm i2c_piix4 sr_mod ppdev parport_pc e1000
> i2c_core cdrom pcspkr parport floppy ghash_clmulni_intel microcode
> [ 7595.866006] Pid: 13959, comm: btrfs Not tainted 3.5.4-gentoo-03 #1
> [ 7595.866006] Call Trace:
> [ 7595.866010] [<ffffffff8103b589>] ? warn_slowpath_common+0x79/0xc0
> [ 7595.866012] [<ffffffff8103b685>] ? warn_slowpath_fmt+0x45/0x50
> [ 7595.866013] [<ffffffff81242f55>] ? __btrfs_abort_transaction+0xc5/0xe0
> [ 7595.866016] [<ffffffff81270e04>] ? btrfs_unlink_subvol+0x204/0x360
> [ 7595.866020] [<ffffffff8129b28e>] ? btrfs_ioctl_snap_destroy+0x39e/0x4f0
> [ 7595.866021] [<ffffffff8129d1bb>] ? btrfs_ioctl+0x81b/0x1250
> [ 7595.866024] [<ffffffff810259d2>] ? do_page_fault+0x182/0x440
> [ 7595.866027] [<ffffffff8105ef63>] ? __wake_up+0x43/0x70
> [ 7595.866030] [<ffffffff810fa1ef>] ? do_vfs_ioctl+0x8f/0x520
> [ 7595.866033] [<ffffffff810e9d10>] ? vfs_write+0x140/0x190
> [ 7595.866034] [<ffffffff810fa6c9>] ? sys_ioctl+0x49/0x80
> [ 7595.866038] [<ffffffff815e8ca6>] ? system_call_fastpath+0x1a/0x1f
> [ 7595.866039] ---[ end trace 1d7d6e7d89b14907 ]---
> [ 7595.866041] BTRFS error (device sda5) in btrfs_unlink_subvol:3176:
> error 28
> [ 7595.866042] btrfs is forced readonly
> [ 7595.866044] BTRFS error (device sda5) in
> btrfs_ioctl_snap_destroy:2038: error 28
>
>
> fwt portage # uname -a
> Linux fwt 3.5.4-gentoo-03 #1 SMP Thu Oct 4 20:13:12 CEST 2012 x86_64
> Intel(R) Xeon(R) CPU X5650 @ 2.67GHz GenuineIntel GNU/Linux
>
>
> Please if you can help me how to stabilize the file system, as i use
> this as the root filesystem.
>
> I am not in the mail list.
Can you try a newer kernel and see if you still have problems? I think 3.7.1
just got released, give that a whirl if you want to stay on a stable kernel, or
give btrfs-next a whirl if you don't mind trying something a little less stable.
Thanks,
Josef
prev parent reply other threads:[~2012-12-18 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 21:19 btrfs problem Tóth Csaba
2012-12-18 14:08 ` Josef Bacik [this message]
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=20121218140840.GE2403@localhost.localdomain \
--to=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=tsabi@tsabi.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.