linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Got 10 csum errors according to dmesg but 0 errors according to dev stats
Date: Sun, 17 May 2015 08:57:14 +0000 (UTC)	[thread overview]
Message-ID: <pan$d8c97$deca2272$e50e1da0$5aecdcf8@cox.net> (raw)
In-Reply-To: 20150517083654.GA5425@mew

Omar Sandoval posted on Sun, 17 May 2015 01:36:54 -0700 as excerpted:

> I should have been clearer in that other thread: conversion from ext4 to
> Btrfs works, its just that the commit that caused the regression did not
> actually accomplish what it set out to do: allow converting the
> data/metadata profile of a freshly btrfs-converted ext4 filesystem.

Thank you.  Clearer now. =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2015-05-17  9:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-10 14:37 Got 10 csum errors according to dmesg but 0 errors according to dev stats Philip Seeger
2015-05-10 14:58 ` Philip Seeger
     [not found]   ` <CABR0jERqzkdTJxX_1S5WEZHDzX8=O8P7r+Bk0mesPLsR2n=w8A@mail.gmail.com>
2015-05-10 17:32     ` Philip Seeger
2015-05-11  1:41       ` Russell Coker
2015-05-12  0:14         ` Philip Seeger
2015-05-12  1:04           ` Paul Jones
2015-05-12  1:37             ` Chris Murphy
2015-05-15 18:40               ` Philip Seeger
2015-05-15 18:33             ` Philip Seeger
2015-05-17  1:53   ` Philip Seeger
2015-05-17  8:19     ` Duncan
2015-05-17  8:36       ` Omar Sandoval
2015-05-17  8:57         ` Duncan [this message]
2015-05-23 12:49       ` Philip Seeger
2015-05-23 16:52         ` Duncan
2015-05-27 20:25           ` Philip Seeger

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='pan$d8c97$deca2272$e50e1da0$5aecdcf8@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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).