From: Ying-Hung Chen <ying@yingternet.com>
To: linux-kernel@vger.kernel.org
Subject: wierd raid 1 problem
Date: Tue, 09 Sep 2003 10:59:24 -0700 [thread overview]
Message-ID: <3F5E14FC.5090001@yingternet.com> (raw)
Hi all,
I have recently encounter a weird raid 1 problem on my system. Here is
my setup:
i have two ide harddisk on a promise ide control card (PDC20262)
and here is my /etc/raidtab file
raiddev /dev/md0
raid-level 1
chunk-size 64k
persistent-superblock 1
nr-raid-disks 2
device /dev/hdd1
raid-disk 0
device /dev/hdb1
raid-disk 1
the file system is XFS. everything works most of time except from time
to time, files seem to get corrupted. I test the integrity by running
rpm --checks *.rpm continuously to verify the signature of the file.
the corrupted files seem to 'recover' itself if i leave the machine
alone for a while or umount and mount back the filesystem.
does anyone have this type of temperory file corruption problem? I
tested it against 2.4.2x kernel including the last vanilla 2.4.22 + xfs
patches, they all seem to have the same problem
Thanks,
-Ying
next reply other threads:[~2003-09-09 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 17:59 Ying-Hung Chen [this message]
2003-09-09 20:53 ` wierd raid 1 problem Alan Cox
2003-09-10 18:59 ` Tomi Orava
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=3F5E14FC.5090001@yingternet.com \
--to=ying@yingternet.com \
--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 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.