Thanks for the reply Lennart.
1) mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, 28, 0) = -1 EINVAL
> (Invalid argument) is the culprit for this error???2) If YES. Is this JFFS2 MTD file system bug or
3) Is this not considered as systemd bug to support compatibility for such file system? Check first FS support writable mappings or not and if not then use other method to enable Persistence logging for systemd?
On Tue, May 21, 2019 at 5:05 PM Lennart Poettering <lennart@xxxxxxxxxxxxxx> wrote:
On Di, 21.05.19 16:45, Kay One (kayone007@xxxxxxxxx) wrote:
> Hi Lennart,
>
> Thanks for the reply.
> JFFS2 is the file system being used in my case. Also, if I would delete
> /var/log/journal directory then these errors are stopping.
> Meaning while writing to persistence storage this error is persisting all
> the time.
>
> cat /proc/cmdline
> console=ttyS0,115200 root=/dev/mtdblock2 rw rootfstype=jffs2
>
> df -Tk
> Filesystem Type 1K-blocks Used Available Use% Mounted
> on
> /dev/root *jffs2* 81792 61220 20572 75% /
> devtmpfs devtmpfs 506040 4 506036 0% /dev
> tmpfs tmpfs 514744 4 514740 0% /dev/shm
> tmpfs tmpfs 514744 13268 501476 3% /run
> tmpfs tmpfs 514744 0 514744 0%
> /sys/fs/cgroup
> tmpfs tmpfs 514744 0 514744 0% /tmp
> /dev/mtdblock1 *jffs2* 20416 6784 13632 33%
> /home/root/apps
> tmpfs tmpfs 102948 0 102948 0%
> /run/user/0
>
> Suspicious cause for this error:
> ------------------------------------------
>
>
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_SHARED, 28, 0) = -1 EINVAL
> (Invalid argument)
The journal requires a storage file system that supports writable
memory mapping. Your's (jffs2) apparently does not, it's too limited
for that.
Maybe you can work with the kernel maintainers of that file system to
add proper support for writbale mmap()?
Lennart
--
Lennart Poettering, Berlin
1)
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
