From: Dan Nilsson <zyrax@home.se>
To: reiserfs-list@namesys.com
Subject: Reoccuring corruption problem
Date: Thu, 19 Aug 2004 20:46:26 +0200 [thread overview]
Message-ID: <200408192046.27223.zyrax@home.se> (raw)
Hi!
I've been trying to cure a reoccuring file corruption problem
i have on my Gentoo box running Linux 2.6.8.1-mm1 (upgraded
from 2.6.7; made no difference).
I get corrupted directory entries behaving like this:
bash-2.05b# rm -rf dev-perl/
rm: cannot remove directory Dev-perl/': Directory not empty
bash-2.05b# cd dev-perl/
bash-2.05b# ls
Curses-uI
bash-2.05b# ls -al
ls: Curses-uI: No such file or directory
total 0
drwxr-xr-x 3 root root 80 Aug 19 20:32 .
drwxrwxrwt 8 root root 304 Aug 19 20:32 ..
Interesting to note is that "Curses-uI" is a corrupted file name,
it usually happens to the same set of files in my /usr/portage.
Typical corruptions i get:
"ruby-progressbar" becomes "ruby-pr?gressbar"
"ruby-zlib" becomes "ruby-zlyb"
If i reboot and use a rescue CD to run reiserfsck --rebuild-tree
the corrupted directories are deleted. However, if i delete my
/usr/portage and try to restore it with "emerge sync", the same
set of files (usually) will corrupt in exactly the same way.
This is how i can reproduce the problem:
1. Reboot to rescue CD.
2. Run reiserfsck --rebuild-tree until it reports no errors
3. Reboot computer (no CD)
4. Remove /usr/portage
5. emerge sync (it will fetch /usr/portage)
emerge will fail and i will be left with some corrupted directories
in the portage trees, usually the ruby-directories.
If i want to be really sure to get more corruption i just try to unpack
a kernel source tarball. It will in the same way create some corrupted
files (and usually same files every time)
From my 2.6.7 configuration:
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
Running 2.6.8.1-mm1 now with SECURITY turned off and some other settings
activated. I do not have the configuration file right here. A friend built
me that kenrel since i cannot build a kernel, unpacking the source produces
corrupted files.
I have run badblocks and memtest and they have come up with nothing.
A very strange problem, I have not read about anything similiar and I
have no clue about what might be causing it.
I made a test program creating 100000 directory entries, which i ran.
No problem deleting those directories. Argh.
Any ideas?
Thanks,
Dan Nilsson
next reply other threads:[~2004-08-19 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-19 18:46 Dan Nilsson [this message]
2004-08-19 19:42 ` Reoccuring corruption problem Sander
2004-08-21 5:43 ` Dan Nilsson
2004-08-21 7:59 ` mjt
2004-08-21 8:16 ` Sander
2004-08-24 8:21 ` Dan Nilsson
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=200408192046.27223.zyrax@home.se \
--to=zyrax@home.se \
--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 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.