All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: corruption: yet another one after deleting a ro snapshot
Date: Tue, 17 Jan 2017 11:39:06 +0100	[thread overview]
Message-ID: <7A13A2CF-9D6F-40D7-9688-2A2460825428@scientia.net> (raw)
In-Reply-To: <5c66c74f-3c6d-b296-32ea-9263848ea16f@cn.fujitsu.com>

Am 17. Januar 2017 09:53:19 MEZ schrieb Qu Wenruo <quwenruo@cn.fujitsu.com>:
>Just lowmem false alert, as extent-tree dump shows complete fine
>result.
>
>I'll CC you and adds your reported-by tag when there is any update on 
>this case.

Fine, just one thing left right more from my side on this issue:
Do you want me to leave the fs untouched until I could verify a lowmem mode fix?
Or is it ok to go on using it (and running backups on it)? 

Cheers,
Chris.

  reply	other threads:[~2017-01-17 10:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12  1:07 corruption: yet another one after deleting a ro snapshot Christoph Anton Mitterer
2017-01-12  1:13 ` Christoph Anton Mitterer
2017-01-12  1:25 ` Qu Wenruo
2017-01-12  2:28   ` Christoph Anton Mitterer
2017-01-12  2:38     ` Qu Wenruo
2017-01-15 17:04       ` Christoph Anton Mitterer
2017-01-16  1:38         ` Qu Wenruo
2017-01-16  2:56           ` Christoph Anton Mitterer
2017-01-16  3:16             ` Qu Wenruo
2017-01-16  4:53               ` Christoph Anton Mitterer
2017-01-16  5:47                 ` Qu Wenruo
2017-01-16 22:07                   ` Christoph Anton Mitterer
2017-01-17  8:53                     ` Qu Wenruo
2017-01-17 10:39                       ` Christoph Anton Mitterer [this message]
2017-01-18  0:41                         ` Qu Wenruo
2017-01-18  1:20                           ` Christoph Anton Mitterer
2017-01-12 10:27 Giuseppe Della Bianca
2017-01-16 11:06 Giuseppe Della Bianca

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=7A13A2CF-9D6F-40D7-9688-2A2460825428@scientia.net \
    --to=calestyo@scientia.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.