From: Christoph Anton Mitterer <calestyo@scientia.net>
To: xfs@oss.sgi.com
Subject: binary NULL errors
Date: Mon, 14 Jan 2008 19:05:49 +0100 [thread overview]
Message-ID: <1200333949.3145.33.camel@fermat.scientia.net> (raw)
Hi.
I've got some questions about using XFS.
I've already used it as for all my discs about one or two years ago, but
then I've suffered several times from the binary NULLs "bug", that
happened when the system crashed or had a power loss.
I've lost more than one open files (like all my bookmarks in Firefox)
and thus I've switched back to ext3
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?
Is XFS now similar to ext3 and I won't see those binary NULLs stuff
again?
What happens now in case of a powerloss? Does XFS still make heavy use
of caching techniques?
Best wishes,
Chris,
next reply other threads:[~2008-01-14 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 18:05 Christoph Anton Mitterer [this message]
2008-01-14 23:17 ` binary NULL errors David Chinner
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=1200333949.3145.33.camel@fermat.scientia.net \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox