>>> Ulrich Windl schrieb am 03.02.2021 um 10:34 in Nachricht <601A6E3D.E40 :
161 :
60728>:
Lennart Poettering schrieb am 02.02.2021 um
15:59 in
> Nachricht <20210202145954.GB36677@gardel-login>:
> > On Di, 02.02.21 10:43, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
> wrote:
> >
> >>
On Thu, Feb 4, 2021 at 6:28 AM Lennart Poettering
wrote:
>
> On Mi, 03.02.21 22:32, Chris Murphy (li...@colorremedies.com) wrote:
> > It doesn't. It waits indefinitely.
> >
> > [* ] A start job is running for
> > /dev/disk/by-uuid/cf9c9518-45d4-43d6-8a0a-294994c383fa (12min 36s / no
> >
On Thu, Feb 4, 2021 at 6:49 AM Lennart Poettering
wrote:
> You want to optimize write pattersn I understand, i.e. minimize
> iops. Hence start with profiling iops, i.e. what defrag actually costs
> and then weight that agains the reduced access time when accessing the
> files. In particular on
03.02.2021 22:25, Benjamin Berg пишет:
> On Wed, 2021-02-03 at 20:47 +0300, Andrei Borzenkov wrote:
>> 03.02.2021 00:25, Benjamin Berg пишет:
>>> On Tue, 2021-02-02 at 22:50 +0300, Andrei Borzenkov wrote:
02.02.2021 17:59, Lennart Poettering пишет:
>
> Note that Requires= in almost
On Thu, 04 Feb 2021 at 13:07:33 +0100, Reindl Harald wrote:
> "Requires=a.service" combined with "Before=a.service" is contradictory -
> don't you get that?
It means what it says: whenever my service is enabled, a.service must
also be enabled, but my service has to start first (and stop last).
On Thu, 2021-02-04 at 13:07 +0100, Reindl Harald wrote:
> Am 04.02.21 um 12:46 schrieb Benjamin Berg:
> > On Wed, 2021-02-03 at 16:43 +0100, Reindl Harald wrote:
> > > seriously - explain what you expect to happen in case of
> > >
> > > Requires=a.service
> > > Before=a.service
> > >
> > >
Lennart Poettering writes:
> Well, at least on my system here there are still like 20 fragments per
> file. That's not nothin?
In a 100 mb file? It could be better, but I very much doubt you're
going to notice a difference after defragmenting that. I may be the nut
that rescued the old ext2
On Mi, 03.02.21 23:11, Chris Murphy (li...@colorremedies.com) wrote:
> On Wed, Feb 3, 2021 at 9:46 AM Lennart Poettering
> wrote:
> >
> > Performance is terrible if cow is used on journal files while we write
> > them.
>
> I've done it for a year on NVMe. The latency is so low, it doesn't
>
On Mi, 03.02.21 22:51, Chris Murphy (li...@colorremedies.com) wrote:
> > > Since systemd-journald sets nodatacow on /var/log/journal the journals
> > > don't really fragment much. I typically see 2-4 extents for the life
> > > of the journal, depending on how many times it's grown, in what looks
On Mi, 03.02.21 22:32, Chris Murphy (li...@colorremedies.com) wrote:
> On Thu, Jan 28, 2021 at 7:18 AM Lennart Poettering
> wrote:
> >
> > On Mi, 27.01.21 17:19, Chris Murphy (li...@colorremedies.com) wrote:
> >
> > > Is it possible for a udev rule to have a timeout? For example:
> > >
Thank you very much Lennart for the help. I was eager to know whether
there was any known limitation, hence this question.
Hi Andy,
I am currently building a diagnostics data collector that collects various
diagnostics data at different scheduled intervals as configured by the
user.
Am 04.02.21 um 12:46 schrieb Benjamin Berg:
On Wed, 2021-02-03 at 16:43 +0100, Reindl Harald wrote:
seriously - explain what you expect to happen in case of
Requires=a.service
Before=a.service
except some warning that it's nonsense
So, one way I used it is as ExecStartPost= equivalent
On Wed, 2021-02-03 at 16:43 +0100, Reindl Harald wrote:
> seriously - explain what you expect to happen in case of
>
> Requires=a.service
> Before=a.service
>
> except some warning that it's nonsense
So, one way I used it is as ExecStartPost= equivalent for a .target
unit. i.e. pull in a
13 matches
Mail list logo
