From: "Jeff Briggs" <ephemeral.elusive@gmail.com>
To: Russell Cattelan <cattelan@thebarn.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS null files
Date: Tue, 15 Aug 2006 23:14:23 +0100 [thread overview]
Message-ID: <83d59530608151514m288edcf1te3268b413b94dd2a@mail.gmail.com> (raw)
In-Reply-To: <44D66BBF.8010107@thebarn.com>
On 06/08/06, Russell Cattelan <cattelan@thebarn.com> wrote:
> Check to see if you have this change
> http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_vnodeops.c.diff?r1=1.675;r2=1.676;f=h
>
> I helps reduce the null file problem.
i do not.
> > emacs claims to fsync on write, yet still I lost data, the faq
> > suggests I should not have if this is so?
> >
> > Is this likely to be fixed soon, or should I switch file system?
>
> Any caching file system could potentially loose data, XFS just happens to
> get the file size correct so you end up with a file that is nothing but a
> hole. Other file system would probably just give you an empty file.
> Either way data in cache always has the potential for being lost.
> Running xfs in full sync mode would be safest but you loose many performance
> advantages... so it always a trade off of performance vs data integrity.
it's really ugly how the default is not safe. i didn't have my write
cache disabled, but it is now.
thanks for the responses.
prev parent reply other threads:[~2006-08-15 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-06 19:32 XFS null files Jeff Briggs
2006-08-06 21:22 ` Iustin Pop
2006-08-06 22:22 ` Russell Cattelan
2006-08-15 22:14 ` Jeff Briggs [this message]
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=83d59530608151514m288edcf1te3268b413b94dd2a@mail.gmail.com \
--to=ephemeral.elusive@gmail.com \
--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