Thanks for the replies.
After some diggings, I found the writes that I was seeing was for not the real
writes, instead they are those COW writes mentioned in the following commit.
"ext4: fix fault handling when mounted with -o dax,ro
"https://github.com/torvalds/linux/commit/fd96b8da68d32a9403726db09b229f4b5ac849c7#diff-f959e50cbd17809e773ef7b89a38d3ca
I was hitting this exactly issue on DAX enabled readonly emulated PMEM devices.
(a regression from
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.11.y&id=5a3651b4a92cbc5230d67d2ce87fb3f7373c7665
)
With above fix, it's all good now.
ThanksCheng-mean
On Tuesday, September 12, 2017 2:03 AM, Simon Ruderich <[email protected]>
wrote:
On Mon, Sep 11, 2017 at 02:31:41PM -0600, Andreas Dilger wrote:
> On Sep 11, 2017, at 12:21 PM, Ross Zwisler wrote:
>>
>> On Sat, Sep 09, 2017 at 05:10:26PM +0000, Soccer Liu wrote:
>>> [snip]
>>>
>>> Based on the following Mount documentation below, I did mount this ext fs
>>> with ro and noloadAre there any other options that I could use to totally
>>> eliminate those unexpected writes?
>
> [snip]
>
> Also, ext4 journal recovery will be done on the filesystem regardless of
> whether it is mounted read-only or not.
I thought the noload option should prevent journal recovery and
thus be truly read-only. At least it worked on a read-only device
for me.
Regards
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
_______________________________________________
Linux-nvdimm mailing list
[email protected]
https://lists.01.org/mailman/listinfo/linux-nvdimm
