RE: [PATCH] exfat: do not clear VolumeDirty in writeback

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "'Yuezhang.Mo@xxxxxxxx'" <Yuezhang.Mo@xxxxxxxx>, "linkinjeon@xxxxxxxxxx" <linkinjeon@xxxxxxxxxx>, "sj1557.seo@xxxxxxxxxxx" <sj1557.seo@xxxxxxxxxxx>
Subject: RE: [PATCH] exfat: do not clear VolumeDirty in writeback
From: "Kohada.Tetsuhiro@xxxxxxxxxxxxxxxxxxxxxxxxxxx" <Kohada.Tetsuhiro@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 28 Feb 2022 07:11:34 +0000
Accept-language: ja-JP, en-US
Cc: "linux-fsdevel@xxxxxxxxxxxxxxx" <linux-fsdevel@xxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>
Deferred-delivery: Mon, 28 Feb 2022 07:14:00 +0000
In-reply-to: <HK2PR04MB38914869B1FEE326CFE11779812D9@HK2PR04MB3891.apcprd04.prod.outlook.com>
Thread-index: AQHYHKozeVmted1T5UKvjQCq+AaGCayoqY+A
Thread-topic: [PATCH] exfat: do not clear VolumeDirty in writeback

Hi, Yuezhang.

> And VolumeDirty will be set again when updating the parent directory. It means that BootSector will be written twice in
> each writeback, that will shorten the life of the device.

I have the same concern.

Follow-Ups:
- RE: [PATCH] exfat: do not clear VolumeDirty in writeback
  - From: Yuezhang.Mo@xxxxxxxx

References:
- [PATCH] exfat: do not clear VolumeDirty in writeback
  - From: Yuezhang.Mo@xxxxxxxx

Prev by Date: [PATCH v3 6/6] mm: remove range parameter from follow_invalidate_pte()
Next by Date: Re: Report 2 in ext4 and journal based on v5.17-rc1
Previous by thread: Re: [PATCH] exfat: do not clear VolumeDirty in writeback
Next by thread: RE: [PATCH] exfat: do not clear VolumeDirty in writeback
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]