From: David Chinner <dgc@sgi.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: xfs@oss.sgi.com
Subject: Re: binary NULL errors
Date: Tue, 15 Jan 2008 10:17:51 +1100 [thread overview]
Message-ID: <20080114231751.GV155259@sgi.com> (raw)
In-Reply-To: <1200333949.3145.33.camel@fermat.scientia.net>
On Mon, Jan 14, 2008 at 07:05:49PM +0100, Christoph Anton Mitterer wrote:
> In the FAQ at http://oss.sgi.com/projects/xfs/faq.html it says:
> Update: This issue has been addressed with a CVS fix on the 29th March
> 2007 and merged into mainline on 8th May 2007 for 2.6.22-rc1.
>
> What does this exactly mean and what has been fixed/addressed?
It means exactly what it says - that the problem has been fixed if
you use 2.6.22 or more recent. If you want details, start looking
here:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ba87ea699ebd9dd577bf055ebc4a98200e337542
> Is XFS now similar to ext3 and I won't see those binary NULLs stuff
> again?
Yes, It will behave the same as ext3 - either you'll have a good
file or you'll see a zero length file (because the application
doesn't overwrite safely).
> What happens now in case of a powerloss?
Same thing as always happens on power loss - you lose whatever
is in memory. We're just more careful about how we update stuff
on disk now.
> Does XFS still make heavy use
> of caching techniques?
Yes, just like every other linux filesystem ;)
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2008-01-14 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 18:05 binary NULL errors Christoph Anton Mitterer
2008-01-14 23:17 ` David Chinner [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=20080114231751.GV155259@sgi.com \
--to=dgc@sgi.com \
--cc=calestyo@scientia.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.