linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Arendt <admin@prnet.org>
To: Robert White <rwhite@pobox.com>, linux-btrfs@vger.kernel.org
Subject: Re: Random file system corruption in 3.17 (not BTRFS related...?)
Date: Tue, 14 Oct 2014 19:22:11 +0200	[thread overview]
Message-ID: <543D5BC3.9080008@prnet.org> (raw)
In-Reply-To: <543D555B.50708@pobox.com>

I didn't notice a corruption on other filesystems with kernel 3.17.0. 
Also I didn't experience any hangs except when trying to mount a 
corrupted btrfs but this was causing a hang within less than 10 seconds. 
It could be that your problem is unrelated and that the corruption you 
are experiencing is due to an unrelated hang followed by a hard 
powerdown. Have you been able to capture any btrfs related kernel panics ?

On 10/14/14 6:54 PM, Robert White wrote:
> 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.)
>
> -- 
> 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


  reply	other threads:[~2014-10-14 17:22 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 [this message]
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
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=543D5BC3.9080008@prnet.org \
    --to=admin@prnet.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rwhite@pobox.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).