From: Chris Wedgwood <cw@f00f.org>
To: Russell Cattelan <cattelan@thebarn.com>
Cc: Martin Steigerwald <Martin@Lichtvoll.de>, xfs@oss.sgi.com
Subject: Re: massively truncated files with XFS with sudden power loss on 2.6.27 and 2.6.28
Date: Mon, 29 Dec 2008 12:17:41 -0800 [thread overview]
Message-ID: <20081229201741.GA20024@puku.stupidest.org> (raw)
In-Reply-To: <49592E7D.4050208@xfs.org>
On Mon, Dec 29, 2008 at 02:09:33PM -0600, Russell Cattelan wrote:
> Still why is the file size making it to disk before the data and
> more importantly the extent transaction to the log?
well, as you know, it's logged, the data isn't
> that should have been fixed.
the window was shrunk to write out begins on close for existing files
the are opened with truncate (i think nathans did that some time
ago?)
new files won't be affected by that change
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-30 7:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 18:20 massively truncated files with XFS with sudden power loss on 2.6.27 and 2.6.28 Martin Steigerwald
2008-12-29 19:03 ` Chris Wedgwood
2008-12-29 19:08 ` Eric Sandeen
2008-12-29 20:00 ` Martin Steigerwald
2008-12-30 0:14 ` Chris Wedgwood
2008-12-29 19:09 ` Russell Cattelan
2008-12-29 19:20 ` Christoph Hellwig
2008-12-29 19:29 ` Chris Wedgwood
2008-12-29 20:09 ` Russell Cattelan
2008-12-29 20:17 ` Chris Wedgwood [this message]
2008-12-29 21:25 ` Russell Cattelan
2008-12-29 21:56 ` Eric Sandeen
2008-12-29 19:48 ` safe writing in applications (was: Re: massively truncated files with XFS with sudden power loss on 2.6.27 and 2.6.28) Martin Steigerwald
2008-12-29 19:54 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081229201741.GA20024@puku.stupidest.org \
--to=cw@f00f.org \
--cc=Martin@Lichtvoll.de \
--cc=cattelan@thebarn.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox