From: Craig Shelley <craig@microtron.org.uk>
To: reiserfs-list@namesys.com
Subject: Reiser4 Corruption
Date: Wed, 18 May 2005 23:12:50 +0100 [thread overview]
Message-ID: <1116454370.6332.24.camel@teratron.lan.etheus.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1873 bytes --]
I have a corruption on my root file system and fsck.reiser4 is unable to
find or fix it. The system behaves normally until certain files in my
local kernel source tree are accessed, eg during the final stages of a
kernel compile. When the corrupt files are accessed, the entire file
system becomes locked out.
I have attached a screen-shot of the error message printed out when the
problem occurs.
Kernel version: 2.6.11.6
Reiser4 patch: reiser4-for-2.6.11-3.patch.gz
fsck.reiser4 version: 1.0.4
PS: The corruption was most likely caused by a bug in a kernel driver I
am currently working on, as there was an 'off by one' error in an array
parser. I suspect the driver overwrote some file system cache, which
eventually got written to disk.
thanks,
--
Craig Shelley
EMail: craig@microtron.org.uk
Jabber: shell@jabber.earth.li
PPS: I think the problem is now cured, however there was something wrong
with the file system which fsck.reiser4 could not detect. This badness
caused further file system corruptions when writing to certain files was
attempted. I cured the problem by copying the directory tree containing
the corrupt files, to a new location. The kernel spewed out a few errors
while doing this, but the new copy can be accessed without causing
problems. I bravely deleted the old directory where the errors where
occurring, and rescanned the file system. Still no errors. The further
corruption which occurred as a result of writing to the already corrupt
files has caused a few library files being deleted. These were later
reinstalled.
Sorry about the slightly dis-jointed email, this is because the original
attachment was too big to be sent to the list, and the message was
bounced.
Keep up the good work, lets hope they let ReIsEr4 into the mainstream
kernel some time soon.
--
Craig
[-- Attachment #1.2: Reiser4-corrupt.png --]
[-- Type: image/png, Size: 51519 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-05-18 22:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 22:12 Craig Shelley [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-31 16:37 Reiser4 corruption dE
2014-10-31 17:26 ` Edward Shishkin
2014-11-01 11:16 ` dE
2014-11-01 12:47 ` Edward Shishkin
2014-11-01 16:05 ` dE
2005-06-17 15:26 reiser4 corruption mross
2005-06-17 17:08 ` Edward Shishkin
2005-06-17 17:50 ` mross
2005-06-20 10:35 ` Vladimir Saveliev
2004-09-04 18:07 Grzegorz Jaśkiewicz
2004-09-04 18:08 ` Grzegorz Jaśkiewicz
2004-09-04 18:23 ` Vince
2004-09-04 18:34 ` Grzegorz Jaśkiewicz
2004-05-22 19:36 dave
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=1116454370.6332.24.camel@teratron.lan.etheus.net \
--to=craig@microtron.org.uk \
--cc=reiserfs-list@namesys.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;
as well as URLs for NNTP newsgroup(s).