From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: frustrations with handling of crash reports
Date: Thu, 19 Jun 2014 15:19:02 +0000 (UTC) [thread overview]
Message-ID: <pan$1427c$773511fe$35aaf2b9$f30ec4e1@cox.net> (raw)
In-Reply-To: pan$ac73e$751c79cd$27db22ed$aa34b841@cox.net
Duncan posted on Thu, 19 Jun 2014 15:06:00 +0000 as excerpted:
> Scrub detects (and potentially fixes) exactly one sort of problem (tho
> that one can definitely cause others), and that's not it.
Hmm. Last phrase was ambiguous.
What I meant was, that problem (your problem) is not the sort of problem
scrub detects and potentially fixes.
NOT: that's not /all/ of what scrub does. (... Which wouldn't make sense
in context, but that's how I initially tried to read it when I reread
what I posted, thus confusing myself, and if even *I* get confused
reading my own writing...! =:^( )
--
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
next prev parent reply other threads:[~2014-06-19 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 13:49 3.15-rc5 deadlocked a 2nd time after I was copying photos from an sdcard + common code path that deadlocks all btrfs filesystems Marc MERLIN
2014-06-17 6:29 ` Satoru Takeuchi
2014-06-17 14:40 ` Marc MERLIN
2014-06-17 14:59 ` frustrations with handling of crash reports Marc MERLIN
2014-06-17 18:27 ` Marc MERLIN
2014-06-18 13:23 ` Konstantinos Skarlatos
2014-06-18 21:22 ` Duncan
2014-06-19 8:56 ` Konstantinos Skarlatos
2014-06-19 15:06 ` Duncan
2014-06-19 15:19 ` Duncan [this message]
2014-06-19 17:37 ` Chris Murphy
2014-06-19 15:13 ` Marc MERLIN
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$1427c$773511fe$35aaf2b9$f30ec4e1@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).