linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pim Zandbergen <P.Zandbergen@macroscoop.nl>
To: linux-raid@vger.kernel.org
Subject: Re: freshly grown array shrinks after first reboot - major data loss
Date: Thu, 01 Sep 2011 18:12:35 +0200	[thread overview]
Message-ID: <4E5FAEF3.60501@macroscoop.nl> (raw)
In-Reply-To: <4E5FA4B5.6010407@macroscoop.nl>

On 09/01/2011 05:28 PM, Pim Zandbergen wrote:
>
>
> What should I do to find the cause?

Additional information:

Both the original 2TB drives as well as the new 3TB drives were GPT
formatted with partition type FD00

This is information about the currently shrunk array:


# mdadm --detail  /dev/md0
/dev/md0:
         Version : 0.90
   Creation Time : Wed Feb  8 23:22:15 2006
      Raid Level : raid5
      Array Size : 4696690944 (4479.11 GiB 4809.41 GB)
   Used Dev Size : 782781824 (746.52 GiB 801.57 GB)
    Raid Devices : 7
   Total Devices : 7
Preferred Minor : 0
     Persistence : Superblock is persistent

     Update Time : Tue Aug 30 21:50:50 2011
           State : clean
  Active Devices : 7
Working Devices : 7
  Failed Devices : 0
   Spare Devices : 0

          Layout : left-symmetric
      Chunk Size : 64K

            UUID : 1bf1b0e2:82d487c5:f6f36a45:766001d1
          Events : 0.3157574

     Number   Major   Minor   RaidDevice State
        0       8      161        0      active sync   /dev/sdk1
        1       8      177        1      active sync   /dev/sdl1
        2       8      193        2      active sync   /dev/sdm1
        3       8      145        3      active sync   /dev/sdj1
        4       8      209        4      active sync   /dev/sdn1
        5       8      225        5      active sync   /dev/sdo1
        6       8      129        6      active sync   /dev/sdi1


  reply	other threads:[~2011-09-01 16:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 15:28 freshly grown array shrinks after first reboot - major data loss Pim Zandbergen
2011-09-01 16:12 ` Pim Zandbergen [this message]
2011-09-01 16:16   ` Pim Zandbergen
2011-09-01 16:48     ` John Robinson
2011-09-01 17:21       ` Pim Zandbergen
2011-09-02  9:02         ` Pim Zandbergen
2011-09-02 10:33           ` Mikael Abrahamsson
2011-09-05 10:47             ` Pim Zandbergen
2011-09-01 16:31   ` Doug Ledford
2011-09-01 17:44     ` Pim Zandbergen
2011-09-01 18:17       ` Doug Ledford
2011-09-01 18:52         ` Pim Zandbergen
2011-09-01 19:41           ` Doug Ledford
2011-09-02  9:19             ` Pim Zandbergen
2011-09-02 11:06               ` John Robinson
2011-09-09 19:30                 ` Bill Davidsen
2011-09-08  1:10         ` NeilBrown
2011-09-08 13:44           ` Pim Zandbergen
2011-09-02  5:32       ` Simon Matthews
2011-09-02  8:53         ` Pim Zandbergen
2011-09-01 17:03   ` Robin Hill

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=4E5FAEF3.60501@macroscoop.nl \
    --to=p.zandbergen@macroscoop.nl \
    --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;
as well as URLs for NNTP newsgroup(s).