[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: raid10 is killing me, and applications that aren't willing to wait for it to respond



On Thu, Dec 14, 2023 at 10:17:23AM +0100, Nicolas George wrote:
> tomas@tuxteam.de (12023-12-14):
> > I've skimmed some of the answers, and they correspond to your confusing
> > request. Someone mentions DNS timeouts to rule them out right away (do
> > you access your RAID over the net? Is DNS resolution involved at all?)
> 
> He quoted:
> 
> >> Error creating proxy: Error calling StartServiceByName for
> >> org.gtk.vfs.GPhoto2VolumeMonitor: Timeout was reached (g-io-error-quark, 24)
> 
> That means the issue is in the DBus monster moussaka¹.

At least this is a more polite metaphor than the one I used, thanks.

>                                                       The odds of
> finding a solution in the current circumstances are vanishingly thin.

Perhaps, perhaps not. May be the root cause is just, as Gene's hunch
seems to be, the disk latency [1] and you are killing the messenger
(which, of course, has disgustingly many tentacles).

That's why I implored Gene to muster up his analytical fu and to cut
with a sharp razor.

Cheers

[1] whoknows. Perhaps some energy saving parameter is set up in an
   insanely aggresive mode, perhaps this interacts in strange ways
   with the RAID controller...

   Then, perhaps it's just the moussaka. Then, DNS timeouts are
   plausible. As, perhaps, ChatGPT latencies are.
-- 
t

Attachment: signature.asc
Description: PGP signature


Reply to: