From: "Shesha B. " Sreenivasamurthy <shesha@inostor.com>
To: bert hubert <ahu@ds9a.nl>
Cc: linux-mm@kvack.org,
LinuxKernel Group <linux-kernel@vger.kernel.org>,
LinuxKernel Newbies <kernelnewbies@nl.linux.org>
Subject: Re: md hangs while rebuilding
Date: 01 Oct 2004 14:50:31 -0700 [thread overview]
Message-ID: <1096667431.9342.1534.camel@arcane> (raw)
In-Reply-To: <20041001205727.GA30680@outpost.ds9a.nl>
I am sorry. :(
Here are the configurations ....
(1) The linux kernel version : 2.4.26
(2) md information
---------------------
/dev/md0 on / type ext3 (rw,data=journal)
none on /proc type proc (rw)
/dev/md2 on /var type ext3 (rw,data=journal)
/dev/md7 on /var/nas type ext3 (rw,data=journal)
/dev/md5 on /tmp type ext3 (rw,data=journal)
/dev/md6 on /var/log type ext3 (rw,data=journal)
/dev/md1 on /alt type ext3 (rw,data=journal)
/dev/md3 on /opt type ext3 (rw,data=journal)
/dev/md4 on /mnt type ext3 (rw,data=journal)
(3) Partition Information
----------------------------
All 9 disk (sda-sdi) is partitioned as follows
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 51 409657 fd Linux raid autodetect
/dev/sda2 52 102 409657+ fd Linux raid autodetect
/dev/sda3 103 111 72292+ 82 Linux swap
/dev/sda4 112 30401 243304425 5 Extended
/dev/sda5 112 137 208844+ fd Linux raid autodetect
/dev/sda6 138 176 313267 fd Linux raid autodetect
/dev/sda7 177 179 24097 fd Linux raid autodetect
/dev/sda8 180 205 208844+ fd Linux raid autodetect
/dev/sda9 206 244 313267 fd Linux raid autodetect
/dev/sda10 245 267 184747 fd Linux raid autodetect
/dev/sda11 268 30401 242051352+ 83 Linux
---------------
Please let me know if any more info is required. Any help is regarded.
-Shesha
On Fri, 2004-10-01 at 13:57, bert hubert wrote:
> On Fri, Oct 01, 2004 at 12:16:51PM -0700, Shesha B. Sreenivasamurthy wrote:
>
> > I have 9 disks raid 1. I pulled out 4 disks, and using raidhotadd I
> > triggered a rebuild on 3 of them. While rebuilding md1, the rebuilding
> > process is stuck at 0.0%. Below is a snapshot of "/proc/mdstat".
>
> Please please please tell people what kernel you run with and your exact
> configuration.
--
.-----.
/ \
{ o | o }
|
\_/
WARNING: multiple messages have this Message-ID (diff)
From: "Shesha B. " Sreenivasamurthy <shesha@inostor.com>
To: bert hubert <ahu@ds9a.nl>
Cc: linux-mm@kvack.org,
LinuxKernel Group <linux-kernel@vger.kernel.org>,
LinuxKernel Newbies <kernelnewbies@nl.linux.org>
Subject: Re: md hangs while rebuilding
Date: 01 Oct 2004 14:50:31 -0700 [thread overview]
Message-ID: <1096667431.9342.1534.camel@arcane> (raw)
In-Reply-To: <20041001205727.GA30680@outpost.ds9a.nl>
I am sorry. :(
Here are the configurations ....
(1) The linux kernel version : 2.4.26
(2) md information
---------------------
/dev/md0 on / type ext3 (rw,data=journal)
none on /proc type proc (rw)
/dev/md2 on /var type ext3 (rw,data=journal)
/dev/md7 on /var/nas type ext3 (rw,data=journal)
/dev/md5 on /tmp type ext3 (rw,data=journal)
/dev/md6 on /var/log type ext3 (rw,data=journal)
/dev/md1 on /alt type ext3 (rw,data=journal)
/dev/md3 on /opt type ext3 (rw,data=journal)
/dev/md4 on /mnt type ext3 (rw,data=journal)
(3) Partition Information
----------------------------
All 9 disk (sda-sdi) is partitioned as follows
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 51 409657 fd Linux raid autodetect
/dev/sda2 52 102 409657+ fd Linux raid autodetect
/dev/sda3 103 111 72292+ 82 Linux swap
/dev/sda4 112 30401 243304425 5 Extended
/dev/sda5 112 137 208844+ fd Linux raid autodetect
/dev/sda6 138 176 313267 fd Linux raid autodetect
/dev/sda7 177 179 24097 fd Linux raid autodetect
/dev/sda8 180 205 208844+ fd Linux raid autodetect
/dev/sda9 206 244 313267 fd Linux raid autodetect
/dev/sda10 245 267 184747 fd Linux raid autodetect
/dev/sda11 268 30401 242051352+ 83 Linux
---------------
Please let me know if any more info is required. Any help is regarded.
-Shesha
On Fri, 2004-10-01 at 13:57, bert hubert wrote:
> On Fri, Oct 01, 2004 at 12:16:51PM -0700, Shesha B. Sreenivasamurthy wrote:
>
> > I have 9 disks raid 1. I pulled out 4 disks, and using raidhotadd I
> > triggered a rebuild on 3 of them. While rebuilding md1, the rebuilding
> > process is stuck at 0.0%. Below is a snapshot of "/proc/mdstat".
>
> Please please please tell people what kernel you run with and your exact
> configuration.
--
.-----.
/ \
{ o | o }
|
\_/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-10-01 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 19:16 md hangs while rebuilding Shesha B. Sreenivasamurthy
2004-10-01 19:16 ` Shesha B. Sreenivasamurthy
2004-10-01 20:57 ` bert hubert
2004-10-01 20:57 ` bert hubert
2004-10-01 21:50 ` Shesha B. Sreenivasamurthy [this message]
2004-10-01 21:50 ` Shesha B. Sreenivasamurthy
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=1096667431.9342.1534.camel@arcane \
--to=shesha@inostor.com \
--cc=ahu@ds9a.nl \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.