All of lore.kernel.org
 help / color / mirror / Atom feed
From: Victor <linux-raid@vitoni.de>
To: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: missing superblock on RAID5
Date: Mon, 13 Oct 2003 23:09:37 +0200	[thread overview]
Message-ID: <3F8B1491.57BCF640@vitoni.de> (raw)
In-Reply-To: 3F8B039F.2070403@fantinibakery.com

Actually I have 2 arrays and both have a device more than they should.


# mdadm --detail /dev/md1
/dev/md1:
        Version : 00.90.00
  Creation Time : Wed Jul 30 21:49:33 2003
     Raid Level : raid5
     Array Size : 18474496 (17.62 GiB 18.92 GB)
    Device Size : 9237248 (8.81 GiB 9.46 GB)
   Raid Devices : 3
  Total Devices : 4
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Wed Oct  8 23:53:50 2003
          State : dirty, no-errors
 Active Devices : 3
Working Devices : 3
 Failed Devices : 1
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

    Number   Major   Minor   RaidDevice State
       0       3        3        0      active sync
/dev/ide/host0/bus0/target0/lun0/part3
       1      33        2        1      active sync
/dev/ide/host2/bus0/target0/lun0/part2
       2      34        2        2      active sync
/dev/ide/host2/bus1/target0/lun0/part2
           UUID : 7aa04659:9100ac93:b3808182:f11c0b78
         Events : 0.36



rob wrote:

> that does look strange.  But I've been using software raid for just a
> couple weeks, so don't know a lot about it.
>
> here is same command on our computer. i have only 2 devices.  looks
> like
> something is up with yours.  do you have another md device you can
> check
> the command on?
>
>
> root@fbc5:~ #  mdadm --detail /dev/md0
> /dev/md0:
>         Version : 00.90.00
>   Creation Time : Tue Sep 30 15:22:45 2003
>      Raid Level : raid1
>      Array Size : 8337600 (7.95 GiB 8.54 GB)
>     Device Size : 8337600 (7.95 GiB 8.54 GB)
>    Raid Devices : 2
>   Total Devices : 2
> Preferred Minor : 0
>     Persistence : Superblock is persistent
>
>     Update Time : Fri Oct 10 08:37:34 2003
>           State : dirty, no-errors
>  Active Devices : 2
> Working Devices : 2
>  Failed Devices : 0
>   Spare Devices : 0
>
>     Number   Major   Minor   RaidDevice State
>        0       8        6        0      active sync
> /dev/scsi/host0/bus0/target1/lun0/part6
>        1       8       22        1      active sync
> /dev/scsi/host0/bus0/target3/lun0/part6
>            UUID : 131c021d:7bc1e937:1bea7923:d7eed283
>          Events : 0.54
>



  reply	other threads:[~2003-10-13 21:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-13 15:59 missing superblock on RAID5 Victor
     [not found] ` <3F8AD02C.8080606@fantinibakery.com>
2003-10-13 17:47   ` Victor
2003-10-13 19:57     ` rob
2003-10-13 21:09       ` Victor [this message]
2003-10-13 23:27         ` rob
2003-10-13 23:44           ` Victor
2003-10-14  0:18             ` rob

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=3F8B1491.57BCF640@vitoni.de \
    --to=linux-raid@vitoni.de \
    --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.