Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CAMJ=MEdS4+5Un77MU7dPxkOjA7-yAv-1tbt0vbUaZ8n4R_rrBQ@mail.gmail.com>
In-Reply-To: <CAMJ=MEdS4+5Un77MU7dPxkOjA7-yAv-1tbt0vbUaZ8n4R_rrBQ@mail.gmail.com>
From:   Ronny Meeus <ronny.meeus@gmail.com>
Date:   Mon, 20 May 2019 09:29:57 +0200
Message-ID: <CAMJ=MEcTP1Y_ZE6iqxX-MANGnzGrbzkFUs0TzBHc+KB62aEyqw@mail.gmail.com>
Subject: Re: fs/pstore question
To:     linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Op do 9 mei 2019 10:05 schreef Ronny Meeus <ronny.meeus@gmail.com>:
>
> Hello
>
> I'm using the pstore feature to log kernel crashes.
>
> What I observe is that after reboot, always 2 entries are present in the pstore:
>
> ls -l /mnt/pstore
> total 0
> -r--r--r--    1 root     root         16372 Jan  1 00:00 dmesg-ramoops-0
> -r--r--r--    1 root     root         16372 Jan  1 00:00 dmesg-ramoops-1
>
> If I do not delete the entries and force a new crash, only 2 new
> entries are available
> after the system is online again and the older entries are overwritten.
>
> The reason for this is that the write index is always initialized to 0
> during init.
> Is this intentional? I would expect that existing entries are kept
> until they are explicitly
> deleted or the storage is full. In the latter case the oldest entries
> can be replaced.
>
> Best regards,
> Ronny


Any feedback is appreciated.
Thanks