Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Janek Kozicki <janek_listy@wp.pl>
To: linux-raid@vger.kernel.org
Subject: Re: Help - Urgent!!!
Date: Fri, 13 Nov 2009 10:06:38 +0100	[thread overview]
Message-ID: <20091113100638.02c174fe@atak.bl.pg.gda.pl> (raw)
In-Reply-To: <19196.63471.532066.743149@notabene.brown>

Neil Brown said:     (by the date of Fri, 13 Nov 2009 17:08:47 +1100)

> Where do those "'"s come from???

I also have those "'" on one (out of 3) md's. Maybe it's debian
specific? Or only debian etch specific? Or only debian /dev/md0
specific.... It's only on /dev/md0, like this:

backup:~# mdadm -D /dev/md0
/dev/md0:
        Version : 01.00.03
  Creation Time : Wed Oct 31 09:13:41 2007
     Raid Level : raid1
     Array Size : 979924 (957.12 MiB 1003.44 MB)
    Device Size : 979924 (957.12 MiB 1003.44 MB)
   Raid Devices : 5
  Total Devices : 5
Preferred Minor : 0
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Fri Nov 13 10:04:02 2009
          State : active
 Active Devices : 5
Working Devices : 5
 Failed Devices : 0
  Spare Devices : 0

           Name : 'backup':0
           UUID : 75b0f878:79539d6c:eef22092:f47a6e6f
         Events : 482808

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       5      22        1        1      active sync   /dev/hdc1
       2       3        1        2      active sync   /dev/hda1
       4       8       33        3      active sync   /dev/sdc1
       6       8       17        4      active sync   /dev/sdb1


> 
> What exactly is listed in mdadm.conf for /dev/md0??

nothing.

backup:~# cat /etc/mdadm/mdadm.conf 
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays

# This file was auto-generated on Tue, 23 Oct 2007 22:18:08 +0200
# by mkconf $Id: mkconf 261 2006-11-09 13:32:35Z madduck $



-- 
Janek Kozicki                                                         |

  parent reply	other threads:[~2009-11-13  9:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  4:53 Help - Urgent!!! lrhorer
2009-11-13  5:11 ` Neil Brown
2009-11-13  5:12   ` Neil Brown
2009-11-13  5:14     ` lrhorer
2009-11-13  6:08       ` Neil Brown
2009-11-13  6:22         ` lrhorer
2009-11-13  7:03           ` Neil Brown
2009-11-13 15:09             ` lrhorer
2009-11-14 21:45             ` Leslie Rhorer
2009-11-15  0:05               ` Majed B.
2009-11-15  1:05                 ` Leslie Rhorer
2009-11-13  9:06         ` Janek Kozicki [this message]
2009-11-13  9:44           ` Sujit K M
2009-11-13  5:16     ` lrhorer
     [not found] ` <200911130913.48292.lrhorer@satx.rr.com>
     [not found]   ` <19197.55846.756558.21650@notabene.brown>
2009-11-14  0:30     ` lrhorer
2009-11-14  0:34       ` Majed B.
  -- strict thread matches above, loose matches on Subject: below --
2009-11-13  4:34 Help - Urgent! Rhorer, Leslie

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=20091113100638.02c174fe@atak.bl.pg.gda.pl \
    --to=janek_listy@wp.pl \
    --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