Hey,
On 5/6/25 13:54, Windl, Ulrich wrote:
Hi,
An update: The version I’m using (SLES 15 SP6 systemd-254.24) spends most of
the time in fstat() cals, and I really wonder what’s going on there (say there
are fewer than 20 files to process):
You might want to try a newer systemd version (as V
On Do, 10.04.25 12:47, Phillip Susi (ph...@thesusis.net) wrote:
> It appears that udev calls BLKRRPRT on a block device whenever it gets
> an inotify event that some other process has closed an fd to it.
Not quite. it will issue that when a process closes the block device
after it was open for *w
On Di, 06.05.25 15:47, Lennart Poettering (lenn...@poettering.net) wrote:
> This is not new behaviour btw. It's widely documented (as above), and
> has been that way for decades.
(One more note: you can also disable the inotify thing if you like via
OPTIONS and "watch" in the udev rules file. But
It was <2025-05-05 pon 10:39>, when Kaizaad Bilimorya wrote:
> On Mon, May 5, 2025 at 10:03 AM Andrei Borzenkov
> wrote:
>
>> On Mon, May 5, 2025 at 4:58 PM Kaizaad Bilimorya
>> wrote:
>> >
>> > Hello Silvio,
>> > Thank you for your response.
>> > We're using Ansible to automate some tasks so it
Hi,
An update: The version I'm using (SLES 15 SP6 systemd-254.24) spends most of
the time in fstat() cals, and I really wonder what's going on there (say there
are fewer than 20 files to process):
A perf example:
41245567 % time seconds usecs/call callserrors syscall
41245568 -
Nobody has any thoughts on this behavior that to me at least, appears to
be a bug?
Phillip Susi writes:
> It appears that udev calls BLKRRPRT on a block device whenever it gets
> an inotify event that some other process has closed an fd to it. This
> causes all of the partitions on the disk to
Lennart Poettering writes:
> Not quite. it will issue that when a process closes the block device
> after it was open for *write*. That's a relevant
> distinction. Typically, userspace tools only open raw block devices
> only to partition/format file systems for write, and thus if we then
> rerea
Hi!
SLES Support is working on it, and that support claimed that journalctl would
output the journal line-by-line, calling fstat for each journal file for each
line to output. So for 100 journal files and 6 million lines of journal, that
number would be simply crazy. Most of all I'd wonder what
