Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: dcg <diegocg@gmail.com>
To: Chris Mason <clm@fb.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Reproducible corruption issue in stable, with possible patch unmerged?
Date: Mon, 09 Nov 2015 20:52:27 +0100	[thread overview]
Message-ID: <1577930.BqffQ3G4ml@archlinux> (raw)
In-Reply-To: <20151107201727.GB26661@ret.masoncoding.com>

Saturday 07 November 2015 15:17:27 Chris Mason escribió:
> > error output. The patch doesn't seem to have been merged:
> Good catch.  Can you describe your configuration?

pool of 3 spinning disks, configured with raid0 for data and raid1
for metadata

Total devices 3 FS bytes used 749.78GiB
        devid    1 size 1.81TiB used 254.00GiB path /dev/sdc1
        devid    2 size 465.76GiB used 253.01GiB path /dev/sdb1
        devid    3 size 463.76GiB used 252.01GiB path /dev/sda3

x86-64 system, 4 cores, 16 GB RAM

      reply	other threads:[~2015-11-09 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 15:36 Reproducible corruption issue in stable, with possible patch unmerged? Diego Call.
2015-11-07 20:17 ` Chris Mason
2015-11-09 19:52   ` dcg [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=1577930.BqffQ3G4ml@archlinux \
    --to=diegocg@gmail.com \
    --cc=clm@fb.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