linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS hang with 3.16-rc5 (and also with 3.16-rc4)
Date: Fri, 25 Jul 2014 12:07:20 +0200	[thread overview]
Message-ID: <17377348.Wo7egBKq1U@merkaba> (raw)
In-Reply-To: <pan$aa09d$75e2870b$4abbbcef$7f21a37d@cox.net>

Am Freitag, 25. Juli 2014, 02:32:17 schrieb Duncan:
> Martin Steigerwald posted on Thu, 24 Jul 2014 20:49:37 +0200 as excerpted:
> > It may take some time tough cause during compiling the kernel BTRFS hung
> > again, which caused loss of KDE Baloo desktop search file index and
> > parts of a mail I wrote in KMail.
> 
> Heh.  While I do run a kde(-lite) desktop, at least I don't have those
> problems to deal with.  As a gentooer I have the option to build kde
> without the semantic-desktop junk and I've taken that option, so no baloo
> or the like here.  And after the akonadified kmail lost one too many
> mails and I was going to need to reset the data store to retrieve them
> once again, I asked myself why I was putting up with it, after all, email
> is a decades old technology that should NOT be rocket-science any longer,
> and soon enough I was NOT putting up with it any longer, as I'd switched
> to claws-mail.  Actually, killing with fire kdepim and anything akonadi
> related was what allowed me to kill semantic-desktop as well instead of
> just run-time disabling it, since akonadi is part of the steaming pile.

Heh, I don´t want to make it a discussion about KDE, but I like to make a few 
points about it:

1) It was kmail save letter feature which saved me from *typing* all of the 
mail again. It still had a previous version open.

2) I didn´t see dataloss in KMail for months.

3) Since the recents developments (running stuff partly from Git) I am quite 
satisfied, IMAP performance / handling improved a lot. Even usable with our 
Exchange server now, and barely noticable with my own Dovecot IMAP setup.


It was a tough ride. It still haves rough edges. But it got a lot better to a 
point I am using it on all my systems again. I failed back to other mail 
clients at work for a moment cause IMAP access was barely usable.

There is still one data loss bug with filtering mails through CRM114 mailfilter 
spamfilter I didn´t dare to retry with most recent versions. But it may have 
been fixed already.

> Interesting this came up here just now, too, as there's a current xmodulo
> post about baloo and milou in kde4 and the carryover to kde-frameworks5
> and plasma5, too, with an ongoing discussion.
> 
> http://xmodulo.com/2014/07/kde-semantic-desktop-nepomuk-baloo.html

Baloo is a ton of a improvement. Only two thing I have with it at the moment 
is:

1) File indexing database is fragile in case of sudden write interruption… but 
here with BTRFS compressed extents corruption it may not even be at fault.

2) Sometimes krunner crashes while entering a search topic.

Other than that I have grown to love the marvellous mail address auto 
completion from all indexed mails, the almost instant full text mail search 
and the almost instant fulltext file search.

I suggest we continues this privately or on a KDE related list like kdepim-
users as its not really BTRFS related.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

  parent reply	other threads:[~2014-07-25 10:07 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 15:04 BTRFS hang with 3.16-rc5 Martin Steigerwald
2014-07-14 15:10 ` Martin Steigerwald
2014-07-14 17:51   ` Duncan
2014-07-14 22:03     ` Martin Steigerwald
2014-07-15  2:45       ` Duncan
2014-07-14 20:12   ` Chris Mason
2014-07-14 21:58     ` Martin Steigerwald
2014-07-15 13:21       ` Chris Mason
2014-07-15 15:08         ` Martin Steigerwald
2014-07-23 22:47           ` BTRFS hang with 3.16-rc5 (and also with 3.16-rc4) Martin Steigerwald
2014-07-24 14:58             ` Chris Mason
2014-07-24 16:24               ` Martin Steigerwald
2014-07-24 18:49               ` Martin Steigerwald
2014-07-24 20:04                 ` Chris Mason
2014-07-28 22:57                   ` Martin Steigerwald
2014-07-25  2:32                 ` Duncan
2014-07-25  3:06                   ` Nick Krause
     [not found]                     ` <20140725080244.GA31950@carfax.org.uk>
2014-07-25  9:13                       ` Hugo Mills
2014-07-28 13:20                         ` David Sterba
2014-07-25 10:07                   ` Martin Steigerwald [this message]
2014-07-25  4:51               ` Torbjørn
     [not found]                 ` <20140725092800.GC25859@localhost.localdomain>
2014-07-25 10:22                   ` Torbjørn
     [not found]                     ` <53D23AF1.9010704@skagestad.org>
2014-07-25 11:37                       ` Torbjørn
2014-07-25 16:14                         ` Torbjørn
2014-07-28 10:00                         ` Liu Bo
2014-07-28 11:11                           ` Torbjørn
2014-07-29 10:18                             ` Liu Bo
2014-07-29 15:07                               ` Torbjørn
2014-07-30  5:09                                 ` Liu Bo
2014-07-18  7:51         ` BTRFS hang with 3.16-rc5 Martin Steigerwald
2014-07-18 13:36           ` Chris Mason
2014-07-19 17:59             ` Martin Steigerwald
2014-07-19 18:39               ` Chris Mason
2014-07-19 19:00                 ` Martin Steigerwald

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=17377348.Wo7egBKq1U@merkaba \
    --to=martin@lichtvoll.de \
    --cc=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).