From: "Stephan Kessler" <root@warpy.yomeganet.biz>
To: linux-raid@vger.kernel.org
Subject: Strange behavior: Badblocks go away ;)
Date: Thu, 19 Feb 2004 06:39:46 +0100 [thread overview]
Message-ID: <000001c3f6aa$c94632c0$4db0fea9@kessler.local> (raw)
Hi,
Corresponding to that:
http://marc.theaimsgroup.com/?l=linux-raid&m=107684467010898&w=2
I have had some badblocks and wanted to fix them. The only real Problem
was if an
"e2fsck -f -n -l bblist /dev/md0"
On a mounted RAID Device will make damage to a file system. If anyone
knows an answer to this, i would be real happy :)
Anyways why i open a new thread:
Yesterday the PowerSupply in the computercenter, where my server stands,
was broken and my server was unwillingly rebooted. Because it was a
power failure, the raid had to resync. After that i took a look in the
syslog (kern.log), and there wasn't any hint on badblocks (like an
uncorrectable error on /dev/hda1 etc.) So it seems that the badblocks
went away....
I'm happy but i still want to know where they are, and if they come back
;)
Any hint is useful! :D
Greetings,
Stephan
reply other threads:[~2004-02-19 5:39 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='000001c3f6aa$c94632c0$4db0fea9@kessler.local' \
--to=root@warpy.yomeganet.biz \
--cc=linux-raid@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