[lkml]   [2018]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: POSIX violation by writeback error
On Tue, Sep 04, 2018 at 02:32:28PM +0800, 焦晓冬 wrote:
> Hi,
> After reading several writeback error handling articles from LWN, I
> begin to be upset about writeback error handling.
> Jlayton's patch is simple but wonderful idea towards correct error
> reporting. It seems one crucial thing is still here to be fixed. Does
> anyone have some idea?
> The crucial thing may be that a read() after a successful
> open()-write()-close() may return old data.
> That may happen where an async writeback error occurs after close()
> and the inode/mapping get evicted before read().

Suppose I have 1Gb of RAM. Suppose I open a file, write 0.5Gb to it
and then close it. Then I repeat this 9 times.

Now, when writing those files to storage fails, there is 5Gb of data
to remember and only 1Gb of RAM.

I can choose any part of that 5Gb and try to read it.

Please make a suggestion about where we should store that data?

In the easy case, where the data easily fits in RAM, you COULD write a
solution. But when the hardware fails, the SYSTEM will not be able to
follow the posix rules.


** ** ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.

 \ /
  Last update: 2018-09-04 09:54    [W:0.061 / U:3.304 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site