https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-2238 Lustre <p>What happens when a client has dirty and/or "unstable" pages in its cache, but unmount is run? I'm doing some single node testing, and it appears as though the mount does <b>not</b> wait for these pages to reach stable storage. Thus, the client unmounts with unstable pages in its cache, leaving the door open for these pages to be dropped in the case of a server failure. Replay is no longer possible because the client has already disconnected, right? This seems like a data integrity issue..?</p> LU-2238

Client "unstable" pages potentially lost on unmount (?)

Bug Minor Open Unresolved Alex Zhuravlev Prakash Surya llnl Thu, 25 Oct 2012 19:42:31 +0000 Tue, 7 Jun 2016 15:37:51 +0000 0 5 <p>Alex </p> <p>Who should look into this one?</p> <p>Peter</p> <p>After talking with Andreas and Alex, there is a possibility for data to be lost at unmount time due to RPCs being completed prior to being committed to stable when using async commits.</p> <p>The "right" fix is to send a sync call to the server and wait for that to complete, to ensure the pages are safe on disk. The issue with using a "hard" sync, is causing a "sync storm" on the servers due to a high number of clients all sending the sync at the same time, due to a coordinated unmount. Thus, a "soft" sync should be used instead, and the client will wait for last_committed to be piggy backed on a ping RPC prior to disconnecting.</p> <p>some work to be done in CLIO, I think. then a bit of code implementing "soft" sync on OSS.</p> Development End date Fri, 27 Jun 2014 19:42:31 +0000 Rank 1|hzvavb: Rank (Obsolete) 5296 Start date Thu, 25 Oct 2012 19:42:31 +0000