[lkml]   [2010]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.36 io bring the system to its knees

> > That is data that was freshly touched around the time the system went down, right?
> >
> > I.e. data that was probably half-modified by user-space to begin with.
> It's data that wasn't synced out yet, yes. Which isn't the problem per
> se. With ext3/4 in ordered mode, or xfs, or btrfs the file size won't
> be incremented until the data is written. in ext3/4 in writeback mode
> (or various non-journaling filesystems) however the inode size is
> updated, and metadagta changes are logged. Besides exposing stale
> data which is a security risk in multi-user systems it also means the
> inode looks modified (by size and timestamps), but contains other data
> than actually written.

Well, afaict thats traditional unix behaviour... while it is not user
friendly, I'd not call it 'corrupted filesytem'.

(cesky, pictures)

 \ /
  Last update: 2010-11-10 20:13    [W:0.094 / U:5.728 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site