From: NeilBrown <neilb@suse.de>
To: freeone3000 <freeone3000@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Data Offset
Date: Sat, 2 Jun 2012 09:52:37 +1000 [thread overview]
Message-ID: <20120602095237.3822e2c2@notabene.brown> (raw)
In-Reply-To: <CAFhY2CjOECFy4bWDL6zs9rtSkVGPR9Wv=1UX9vKgmdjwMsmBYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 7384 bytes --]
On Fri, 1 Jun 2012 18:22:33 -0500 freeone3000 <freeone3000@gmail.com> wrote:
> Hello. I have an issue concerning a broken RAID of unsure pedigree.
> Examining the drives tells me the block sizes are not the same, as
> listed in the email.
>
> > I certainly won't be easy. Though if someone did find themselves in that
> > situation it might motivate me to enhance mdadm in some way to make it easily
> > fixable.
>
> I seem to be your motivation for making this situation fixable.
> Somehow I managed to get drives with an invalid block size. All worked
> fine until a drive dropped out of the RAID5. When attempting to
> replace, I can re-create the RAID, but it cannot be of the same size
> because the 1024-sector drives are "too small" when changed to
> 2048-sector, exactly as described. Are there any recovery options I
> could try, including simply editing the header?
You seem to be leaving out some important information.
The "mdadm --examine" of all the drives is good - thanks - but what exactly
if your problem, and what were you trying to do?
You appear to have a 5-device RAID5 of which one device (sde3) fell out of
the array on or shortly after 23rd May, 3 drives are working fine, and one -
sdf (not sdf3??) - is a confused spare....
What exactly did you do to sdf?
NeilBrown
>
>
> mdadm --examine of all drives in the RAID:
>
> /dev/sdb3:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 9759ad94:75e30b6b:8a726b4d:177a6eda
> Name : leyline:1 (local to host leyline)
> Creation Time : Mon Sep 12 13:19:00 2011
> Raid Level : raid5
> Raid Devices : 5
>
> Avail Dev Size : 3906525098 (1862.78 GiB 2000.14 GB)
> Array Size : 15626096640 (7451.10 GiB 8000.56 GB)
> Used Dev Size : 3906524160 (1862.78 GiB 2000.14 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : 872097fa:3ae66ab4:ed21256a:10a030c9
>
> Update Time : Fri Jun 1 03:11:54 2012
> Checksum : 6d627f7a - correct
> Events : 2127454
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 1
> Array State : AAAA. ('A' == active, '.' == missing)
>
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 9759ad94:75e30b6b:8a726b4d:177a6eda
> Name : leyline:1 (local to host leyline)
> Creation Time : Mon Sep 12 13:19:00 2011
> Raid Level : raid5
> Raid Devices : 5
>
> Avail Dev Size : 3906525098 (1862.78 GiB 2000.14 GB)
> Array Size : 15626096640 (7451.10 GiB 8000.56 GB)
> Used Dev Size : 3906524160 (1862.78 GiB 2000.14 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : 2ea285a1:a2342c24:ffec56a2:ba6fcf07
>
> Update Time : Fri Jun 1 03:11:54 2012
> Checksum : fae2ea42 - correct
> Events : 2127454
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 0
> Array State : AAAA. ('A' == active, '.' == missing)
>
> /dev/sdc3:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 9759ad94:75e30b6b:8a726b4d:177a6eda
> Name : leyline:1 (local to host leyline)
> Creation Time : Mon Sep 12 13:19:00 2011
> Raid Level : raid5
> Raid Devices : 5
>
> Avail Dev Size : 3906525098 (1862.78 GiB 2000.14 GB)
> Array Size : 15626096640 (7451.10 GiB 8000.56 GB)
> Used Dev Size : 3906524160 (1862.78 GiB 2000.14 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : 2ea285a1:a2342c24:ffec56a2:ba6fcf07
>
> Update Time : Fri Jun 1 03:11:54 2012
> Checksum : fae2ea42 - correct
> Events : 2127454
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 0
> Array State : AAAA. ('A' == active, '.' == missing)
>
>
> /dev/sdd3:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 9759ad94:75e30b6b:8a726b4d:177a6eda
> Name : leyline:1 (local to host leyline)
> Creation Time : Mon Sep 12 13:19:00 2011
> Raid Level : raid5
> Raid Devices : 5
>
> Avail Dev Size : 3906524160 (1862.78 GiB 2000.14 GB)
> Array Size : 15626096640 (7451.10 GiB 8000.56 GB)
> Data Offset : 1024 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : 8d656a1d:bbb1da37:edaf4011:1af2bbb9
>
> Update Time : Fri Jun 1 03:11:54 2012
> Checksum : ab4c6863 - correct
> Events : 2127454
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : Active device 3
> Array State : AAAA. ('A' == active, '.' == missing)
>
> /dev/sde3:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 9759ad94:75e30b6b:8a726b4d:177a6eda
> Name : leyline:1 (local to host leyline)
> Creation Time : Mon Sep 12 13:19:00 2011
> Raid Level : raid5
> Raid Devices : 5
>
> Avail Dev Size : 3906524160 (1862.78 GiB 2000.14 GB)
> Array Size : 15626096640 (7451.10 GiB 8000.56 GB)
> Data Offset : 1024 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : 37bb83bd:313c9381:cabff9d0:60bd205c
>
> Update Time : Wed May 23 03:30:50 2012
> Checksum : f72e6959 - correct
> Events : 2004256
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : spare
> Array State : AAAA. ('A' == active, '.' == missing)
>
> /dev/sdf:
> Magic : a92b4efc
> Version : 1.2
> Feature Map : 0x0
> Array UUID : 9759ad94:75e30b6b:8a726b4d:177a6eda
> Name : leyline:1 (local to host leyline)
> Creation Time : Mon Sep 12 13:19:00 2011
> Raid Level : raid5
> Raid Devices : 5
>
> Avail Dev Size : 3907027120 (1863.02 GiB 2000.40 GB)
> Array Size : 15626096640 (7451.10 GiB 8000.56 GB)
> Used Dev Size : 3906524160 (1862.78 GiB 2000.14 GB)
> Data Offset : 2048 sectors
> Super Offset : 8 sectors
> State : clean
> Device UUID : e16d4103:cd11cc3b:bb6ee12e:5ad0a6e9
>
> Update Time : Fri Jun 1 03:11:54 2012
> Checksum : e287a82a - correct
> Events : 0
>
> Layout : left-symmetric
> Chunk Size : 512K
>
> Device Role : spare
> Array State : AAAA. ('A' == active, '.' == missing)
>
> --
> James Moore
>
> --
> James Moore
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-06-01 23:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 23:22 Data Offset freeone3000
2012-06-01 23:52 ` NeilBrown [this message]
2012-06-02 0:48 ` freeone3000
2012-06-04 3:35 ` NeilBrown
2012-06-04 18:26 ` Pierre Beck
2012-06-04 22:57 ` NeilBrown
2012-06-05 5:26 ` freeone3000
2012-06-05 5:44 ` NeilBrown
[not found] ` <CAFhY2CiDTMRSV2wFCMhT9ZstUkHkJS7E0p7SP-ssfqwaquo+0w@mail.gmail.com>
[not found] ` <20120610074531.65eaed81@notabene.brown>
[not found] ` <CAFhY2CgxkjH6JvJzvQt9XT0oawntK7YoTFqnXQJGzvqthD8XpQ@mail.gmail.com>
2012-06-13 9:46 ` Pierre Beck
2012-06-13 12:49 ` Phil Turmel
2012-06-13 17:56 ` Pierre Beck
2012-06-13 18:11 ` Phil Turmel
2012-06-13 18:22 ` Pierre Beck
2012-06-13 18:49 ` Piergiorgio Sartor
2012-06-20 3:56 ` freeone3000
2012-06-20 14:09 ` Pierre Beck
2012-06-25 6:25 ` NeilBrown
2014-02-24 11:22 ` wiebittewas
2014-02-24 21:38 ` NeilBrown
-- strict thread matches above, loose matches on Subject: below --
2014-05-15 14:11 Data offset Patrik Horník
2014-05-15 22:07 ` NeilBrown
2014-05-16 0:41 ` Patrik Horník
2012-05-10 17:42 Data Offset Piergiorgio Sartor
2012-05-24 5:20 ` NeilBrown
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=20120602095237.3822e2c2@notabene.brown \
--to=neilb@suse.de \
--cc=freeone3000@gmail.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 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).