From: Josef Bacik <jbacik@fb.com>
To: Juan Orti Alcaine <juan.orti@miceliux.com>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Random file system corruption in 3.17 (not BTRFS related...?)
Date: Wed, 15 Oct 2014 10:30:40 -0400 [thread overview]
Message-ID: <543E8510.8020000@fb.com> (raw)
In-Reply-To: <f9840abeffb3a13578c3358a9e6cfec0@miceliux.com>
On 10/15/2014 10:05 AM, Juan Orti Alcaine wrote:
> El 2014-10-15 15:46, Josef Bacik escribió:
>> On 10/15/2014 03:08 AM, Juan Orti Alcaine wrote:
>>> 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
>>
>> Did it happen on both fs'es or just one? Thanks,
>>
>> Josef
>
> Both filesystems were corrupted. I have / in the SSD and /home in the HDDs.
>
> I didn't notice anything while working with the system, I only
> discovered the problem when booting up after the second or third reboot
> and seeing the service failing to start. Could it be something related
> to the mount/umount logic?
>
We've found it, the Fedora guys are reverting the bad patch now, we'll
get the fix sent back to stable shortly. Sorry about that.
Josef
next prev parent reply other threads:[~2014-10-15 14:30 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
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 [this message]
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=543E8510.8020000@fb.com \
--to=jbacik@fb.com \
--cc=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).