linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert White <rwhite@pobox.com>
To: Bardur Arantsson <spam@scientician.net>, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS free space handling still needs more work: Hangs again
Date: Sat, 27 Dec 2014 20:03:09 -0800	[thread overview]
Message-ID: <549F80FD.4050804@pobox.com> (raw)
In-Reply-To: <m7nkoo$15b$1@ger.gmane.org>

On 12/27/2014 05:01 PM, Bardur Arantsson wrote:
> On 2014-12-28 01:25, Robert White wrote:
>> On 12/27/2014 08:01 AM, Martin Steigerwald wrote:
>>>>  From how you write I get the impression that you think everyone else
>>> beside you is just silly and dumb. Please stop this assumption. I may not
>>> always get terms right, and I may make a mistake as with the wrong df
>>> figure. But I also highly dislike to feel treated like someone who
>>> doesn´t
>>> know a thing.
>>
>> Nope. I'm a systems theorist and I demand/require variable isolation.
>>
>> Not a question of "silly" or "dumb" but a question of "speaking with
>> sufficient precision and clarity".
>>
>> For instance you speak of "having an impression" and then decide I've
>> made an assumption.
>>
>> I define my position. Explain my terms. Give my examples.
>>
>> I also risk being utterly wrong because sometimes being completely wrong
>> gets others to cut away misconceptions and assumptions.
>>
>> It annoys some people, but it gets results.
>
> Can you please stop this bullshit posturing nonsense? It accomlishes
> nothing -- if you're right your other posts will stand for themselves
> and show that you are indeed "the shit" when it comes to these matters,
> but this post (so far, didn't read further) accomplishes nothing other
> than (possibly) convincing everyone that you're a pompous/self-important
> ass.

Really? "accomplishes nothing"?

24 hours ago:

the complaining party was talking about

- Windows XP
- Tax software
- Virtual box
- vdi files
- defragging
- balancing
- "data trees"
- system hanging

And the responding party was saying

"you are the only person reporting this as a regular occurrence" with 
the implication that the report was a duplicate or at least might not 
get much immediate attention.

Now:

The complaining party has verified the minimum, repeatable case of 
simple file allocation on a very fragmented system and the responding 
party and several others have understood and supported the bug.

That's not "accomplishing nothing", thats called engaging in diagnostics 
instead of dismissing a complaint, and sticking out the diagnostic 
process until everyone is on the same page.

I never dismissed Martin. I never disbelieved him. I went through his 
elements one at a time with examples of what I was taking away from him 
and why they didn't match expectations and experimental evidence. We 
adjusted our positions and communications.

So you can call it "bullshit posturing nonsense" but I see "taking less 
than a day to get to the bottom of a bug report that might not have 
gotten significant attention."

  reply	other threads:[~2014-12-28  4:03 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26 13:37 BTRFS free space handling still needs more work: Hangs again Martin Steigerwald
2014-12-26 14:20 ` Martin Steigerwald
2014-12-26 14:41   ` Martin Steigerwald
2014-12-27  3:33     ` Duncan
2014-12-26 15:59 ` Martin Steigerwald
2014-12-27  4:26   ` Duncan
2014-12-26 22:48 ` Robert White
2014-12-27  5:54   ` Duncan
2014-12-27  9:01   ` Martin Steigerwald
2014-12-27  9:30     ` Hugo Mills
2014-12-27 10:54       ` Martin Steigerwald
2014-12-27 11:52         ` Robert White
2014-12-27 13:16           ` Martin Steigerwald
2014-12-27 13:49             ` Robert White
2014-12-27 14:06               ` Martin Steigerwald
2014-12-27 14:00             ` Robert White
2014-12-27 14:14               ` Martin Steigerwald
2014-12-27 14:21                 ` Martin Steigerwald
2014-12-27 15:14                   ` Robert White
2014-12-27 16:01                     ` Martin Steigerwald
2014-12-28  0:25                       ` Robert White
2014-12-28  1:01                         ` Bardur Arantsson
2014-12-28  4:03                           ` Robert White [this message]
2014-12-28 12:03                             ` Martin Steigerwald
2014-12-28 17:04                               ` Patrik Lundquist
2014-12-29 10:14                                 ` Martin Steigerwald
2014-12-28 12:07                             ` Martin Steigerwald
2014-12-28 14:52                               ` Robert White
2014-12-28 15:42                                 ` Martin Steigerwald
2014-12-28 15:47                                   ` Martin Steigerwald
2014-12-29  0:27                                   ` Robert White
2014-12-29  9:14                                     ` Martin Steigerwald
2014-12-27 16:10                     ` Martin Steigerwald
2014-12-27 14:19               ` Robert White
2014-12-27 11:11       ` Martin Steigerwald
2014-12-27 12:08         ` Robert White
2014-12-27 13:55       ` Martin Steigerwald
2014-12-27 14:54         ` Robert White
2014-12-27 16:26           ` Hugo Mills
2014-12-27 17:11             ` Martin Steigerwald
2014-12-27 17:59               ` Martin Steigerwald
2014-12-28  0:06             ` Robert White
2014-12-28 11:05               ` Martin Steigerwald
2014-12-28 13:00         ` BTRFS free space handling still needs more work: Hangs again (further tests) Martin Steigerwald
2014-12-28 13:40           ` BTRFS free space handling still needs more work: Hangs again (further tests, as close as I dare) Martin Steigerwald
2014-12-28 13:56             ` BTRFS free space handling still needs more work: Hangs again (further tests, as close as I dare, current idea) Martin Steigerwald
2014-12-28 15:00               ` Martin Steigerwald
2014-12-29  9:25               ` Martin Steigerwald
2014-12-27 18:28       ` BTRFS free space handling still needs more work: Hangs again Zygo Blaxell
2014-12-27 18:40         ` Hugo Mills
2014-12-27 19:23           ` BTRFS free space handling still needs more work: Hangs again (no complete lockups, "just" tasks stuck for some time) Martin Steigerwald
2014-12-29  2:07             ` Zygo Blaxell
2014-12-29  9:32               ` Martin Steigerwald
2015-01-06 20:03                 ` Zygo Blaxell
2015-01-07 19:08                   ` Martin Steigerwald
2015-01-07 21:41                     ` Zygo Blaxell
2015-01-08  5:45                     ` Duncan
2015-01-08 10:18                       ` Martin Steigerwald
2015-01-09  8:25                         ` Duncan

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=549F80FD.4050804@pobox.com \
    --to=rwhite@pobox.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=spam@scientician.net \
    /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).