| To: | xfs mailing list <xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | Mystery solved? files not written for days... |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Mon, 30 Mar 2009 17:01:04 -0500 |
| User-agent: | Thunderbird 2.0.0.19 (X11/20090105) |
On LKML:
[PATCH] writeback: guard against jiffies wraparound on
inode->dirtied_when checks
When a file is continually dirtied, the check in sync_sb_inodes:
/* Was this inode dirtied after sync_sb_inodes was called? */
if (time_after(inode->dirtied_when, start))
break;
may have large windows where this trips on the first
(continually-dirtied) inode on the list when the time_after check has
wrapped, causing the nothing to be written out for that superblock,
potentially for days.
Could this be the reason for those various "hey, my file disappeared
after a crash and I hadn't written to it for *days*" reports we got now
and then, leaving us all scratching our heads?
-Eric
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH] xfstests: fix async io error handling in fsx, Felix Blyakher |
|---|---|
| Next by Date: | Re: Mystery solved? files not written for days..., Felix Blyakher |
| Previous by Thread: | Re: Regression? 2.6.27-rc3 segfault on cold boot; not on warm boot., Eric Sandeen |
| Next by Thread: | Re: Mystery solved? files not written for days..., Felix Blyakher |
| Indexes: | [Date] [Thread] [Top] [All Lists] |