All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Zimmerman <czimmer@mclaneco.com>
To: linux-raid@vger.kernel.org
Subject: Perhaps this has been answered before...
Date: 21 Aug 2002 11:18:42 -0500	[thread overview]
Message-ID: <1029946722.31116.64.camel@zimmerman> (raw)

[-- Attachment #1: Type: text/plain, Size: 2503 bytes --]

I am new to the list, so forgive me if this is a FAQ: 

I have a Slack system running a patched 2.2.17 kernel with raidtools
0.90 that is running RAID 1 on 2 internal 20 GB IDE drives (one on each
bus).  Periodically, and now happening more frequently, the machine will
partially freeze.  I cannot login into the machine, but the IP address
still answers.  

Here is my fstab: 

/dev/md0       swap        swap        defaults   0   0 
/dev/md1       /        ext2        defaults   1   1 
/dev/md2       /var        ext2        defaults   1   1 
/dev/md3       /home        ext2        defaults   1   1 
none             /dev/pts  devpts     gid=5,mode=620  0   0 
none             /proc    proc        defaults   0   0 


Here is my raidtab: 

raiddev /dev/md0 
        raid-level              1 
        nr-raid-disks           2 
        nr-spare-disks          0 
        persistent-superblock   1 
        chunk-size              4 

        device                  /dev/hda1 
        raid-disk               0 
        device                  /dev/hdb1 
        raid-disk               1 
#       failed-disk             1 
# 
# 
raiddev /dev/md1 
        raid-level              1 
        nr-raid-disks           2 
        nr-spare-disks          0 
        persistent-superblock   1 
        chunk-size              4 

        device                  /dev/hda2 
        raid-disk             0 
        device                  /dev/hdb2 
        raid-disk               1 
# 
# 
raiddev /dev/md2 
        raid-level              1 
        nr-raid-disks           2 
        nr-spare-disks          0 
        persistent-superblock   1 
        chunk-size              4 

        device                  /dev/hda3 
        raid-disk             0 
        device                  /dev/hdb3 
        raid-disk               1 
# 
# 
raiddev /dev/md3 
        raid-level              1 
        nr-raid-disks           2 
        nr-spare-disks          0 
        persistent-superblock   1 
        chunk-size              4 

        device                  /dev/hda4 
        raid-disk             0 
        device                  /dev/hdb4 
        raid-disk               1 

I suspect that "maybe" my swap on md0 is causing the problem, but that
is a guess since I have nothing in the logs up to the time the machine
failed that indicates a problem.  Does anything jump out at you? 

Chris Zimmerman 




[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2002-08-21 16:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-21 16:18 Chris Zimmerman [this message]
2002-08-21 17:31 ` Perhaps this has been answered before Mikael Johansson
2002-08-21 17:41   ` Mads Peter Bach
2002-08-21 18:07     ` Chris Zimmerman
2002-08-21 18:16       ` Mads Peter Bach
2002-08-21 23:53     ` Jakob Oestergaard
2002-08-22 14:47       ` Chris Zimmerman

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=1029946722.31116.64.camel@zimmerman \
    --to=czimmer@mclaneco.com \
    --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 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.