From: Paolo Ornati <ornati@fastwebnet.it>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: scary fcache trouble - silent data corruption(?)
Date: Wed, 28 Jun 2006 10:14:59 +0200 [thread overview]
Message-ID: <20060628101459.1375a27a@localhost> (raw)
Hi, It's always me :)
This time I had a problem that scared me a bit...
Yesterday I've tested fcache for a while.
I have primed system boot + preferred applications startup, and then
I've used the system for a while.
Today I launch my mail-client (Sylpheed-Claws) and the Setup Wizard
dialog appears :-O! (usually it appears when it isn't configured)
After a bit of reserch I've found that an XML config file
(.sylpheed-claws/folderlist.xml) was corrupted.
But it wasn't corrupted randomly, it was "replaced" with a peace of the
firefox cookies file :-X!
Now, Firefox and Sylpheed-Claws are 2 of the few application I've
primed... so my suspect is that there's some subtle BUG in fcache, or
maybe it's elsewhere since it is an experimental kernel after all...
Luckily Sylpheed-Claws makes backup copy of every config file :)
The size of the corrupted file is almost identical to the backup one
(so it is probably equal to the size of the original one).
Even if there is really a BUG in fcache so that it can supply wrong
data I don't know how it got written to the real filesystem (since the
corruption persisted booting without fcache). Maybe Sylpheed-Claws have
read the file and then rewritten to it... I don't know.
Every time something like this happens I ask myself why I test
experimental things on my main PC...
I think this time I was lucky :)
--
Paolo Ornati
Linux 2.6.17-ga39727f2-dirty on x86_64
reply other threads:[~2006-06-28 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060628101459.1375a27a@localhost \
--to=ornati@fastwebnet.it \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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