From: Juan Orti Alcaine <juan.orti@miceliux.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Random file system corruption in 3.17 (not BTRFS related...?)
Date: Wed, 15 Oct 2014 09:08:14 +0200 [thread overview]
Message-ID: <eff13bd09ee6883785a4be3ab005886b@miceliux.com> (raw)
In-Reply-To: <543D555B.50708@pobox.com>
El 2014-10-14 18:54, Robert White escribió:
> Howdy,
>
> So I run several gentoo systems and I upgraded two of them to kernel
> 3.17.0
>
> One using BTRFS for root.
> One using ext3 for root (via the ext4 driver)
>
> _Both_ systems exhibited strange behavior (long pauses and then hangs
> requiring hard-power) within several hours. Both then had random
> filesystem damage.
>
> On the BTRFS system much of my browser settings for firefox were
> trashed, particularly the cookies and saved conifigurations for
> add-ons (like which sites had scripts enabled/disabled in no-script)
> etc.
>
> On the ext3/4 system there were several corruptions including a
> pipe/special file with a large non-zero size that required I do a
> "fsck -fyD /dev/sda3" to repair. (one comment from fsck was that the
> pipe/special file "looked like a directory" or some such)
>
> So I can say that corruption is taking place, but I suspect it is
> _not_ happening in the BTRFS specific code.
>
> (ASIDE: both systems are older amd64 using built-in radeon display
> hardware.)
>
I've also experienced Btrfs corruptions with 3.17.0 (Fedora 21 alpha).
It has happened two times, each one after a clean reinstall and a wipe
of the old fs. In less than a day, both installations got corrupted and
the filesystems went readonly. When listing the contents, I saw many
directories with question marks.
My system has 4 drives and 2 fs:
- 1 SSD in single
- 3 HDD in RAID1
I do readonly snapshots every hour of all the subvolumes, so I have
hundreds of snapshots.
Now I'm back in 3.16.4 without any problems. I'm trying to reproduce my
setup in a virtual machine. If the corruption happens again, I'll send
you more data on this problem.
--
Juan Orti
https://miceliux.com
next prev parent reply other threads:[~2014-10-15 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 16:54 Random file system corruption in 3.17 (not BTRFS related...?) Robert White
2014-10-14 17:22 ` David Arendt
2014-10-14 20:06 ` Robert White
2014-10-14 22:35 ` Duncan
2014-10-15 7:08 ` Juan Orti Alcaine [this message]
2014-10-15 8:53 ` Duncan
2014-10-15 13:46 ` Josef Bacik
2014-10-15 14:05 ` Juan Orti Alcaine
2014-10-15 14:30 ` Josef Bacik
2014-10-15 14:34 ` Juan Orti Alcaine
2014-10-15 19:30 ` Rich Freeman
2014-10-15 20:20 ` Josef Bacik
2014-10-17 16:26 ` Filipe David Manana
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=eff13bd09ee6883785a4be3ab005886b@miceliux.com \
--to=juan.orti@miceliux.com \
--cc=linux-btrfs@vger.kernel.org \
/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).