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: BTRFS hang with 3.16-rc5 (and also with 3.16-rc4)
Date: Fri, 25 Jul 2014 02:32:17 +0000 (UTC)	[thread overview]
Message-ID: <pan$aa09d$75e2870b$4abbbcef$7f21a37d@cox.net> (raw)
In-Reply-To: 1557956.045aK4K0qS@merkaba

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.

And claws-mail has this nice option I didn't even know could be done on 
pop3 mail servers, too.  It downloads the mail for local reading, but 
keeps it on the server for a week (configurable) before final pop3 server-
side deletion, just in case you do crash after download and lose the 
local copy.  I've not actually had to take advantage of that feature yet, 
but it's sure nice to have, just in case. =:^)

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

So fortunately, while I am a development version tester for of both kde 
and btrfs, the akonadi and semantic-desktop steaming-pile-of-.... is not 
something I have to worry about the stability of (or more precisely the 
lack thereof), while also testing a not yet fully stable btrfs at the 
same time.  Hopefully that'll continue to be the case in the claimed more 
modular kde-frameworks-5 era, because there's more than one way to ensure 
that I don't have to deal with that pile, and just as I suddenly found 
some other option for mail after using kmail since the kde2 era when it 
semantic-desktop-integrated without option, so my kde/plasma desktop, 
also since the kde2 era, can find itself going the same route locally, 
should it insist on going the same route globally.

Tho just as I did the akonadified kmail, I'll likely keep an open enough 
mind to try it.  <shrug>  Maybe it'll actually work this time, without 
eating up gigs of indexing space that has to be reset frequently due to 
something going wrong, to do it.  Time will tell...

-- 
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


  parent reply	other threads:[~2014-07-25  2:32 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 [this message]
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
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='pan$aa09d$75e2870b$4abbbcef$7f21a37d@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).