From: Tyler <tyler@dtbb.net>
To: Linux RAID <linux-raid@vger.kernel.org>
Cc: Neil Brown <neilb@cse.unsw.edu.au>
Subject: Any chance you can look at this Superblock v1 bug Neil?
Date: Sat, 23 Jul 2005 15:28:15 -0700 [thread overview]
Message-ID: <42E2C47F.409@dtbb.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
[Fwd: bug report: mdadm-devel-2 , superblock version 1]
I believe I've now tryed this with a patched mdadm devel-2, and a
2.6.13-rc3-mm1 kernel (which as a few recent md patches), with the same
results.
Thanks,
Tyler.
[-- Attachment #2: bug report: mdadm-devel-2 , superblock version 1 --]
[-- Type: message/rfc822, Size: 7036 bytes --]
From: Tyler <pml@dtbb.net>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-raid@vger.kernel.org
Subject: bug report: mdadm-devel-2 , superblock version 1
Date: Sun, 17 Jul 2005 19:09:05 -0700
Message-ID: <42DB0F41.7030806@dtbb.net>
# uname -a
Linux server 2.6.12.3 #3 SMP Sun Jul 17 14:38:12 CEST 2005 i686 GNU/Linux
# ./mdadm -V
mdadm - v2.0-devel-2 - DEVELOPMENT VERSION NOT FOR REGULAR USE - 7 July 2005
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -S /dev/md1
** stop the current array
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -C /dev/md1 -l 5
--raid-devices 3 -e 1 /dev/sda2 /dev/sdb2 /dev/sdc2
mdadm: /dev/sda2 appears to be part of a raid array:
level=5 devices=3 ctime=Mon Jul 18 03:22:05 2005
mdadm: /dev/sdb2 appears to be part of a raid array:
level=5 devices=3 ctime=Mon Jul 18 03:22:05 2005
mdadm: /dev/sdc2 appears to be part of a raid array:
level=5 devices=3 ctime=Mon Jul 18 03:22:05 2005
Continue creating array? y
mdadm: array /dev/md1 started.
** create and start new array using 3 drives, superblock version 1
root@server:~/dev/mdadm-2.0-devel-2# cat /proc/mdstat
Personalities : [raid5]
md1 : active raid5 sdc2[3] sdb2[1] sda2[0]
128384 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
unused devices: <none>
** mdstat mostly okay, except sdc2 is listed as device3 instead of
device2 (from 0,1,2)
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -D /dev/md1
/dev/md1:
Version : 01.00.01
Creation Time : Mon Jul 18 03:56:40 2005
Raid Level : raid5
Array Size : 128384 (125.40 MiB 131.47 MB)
Device Size : 64192 (62.70 MiB 65.73 MB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Mon Jul 18 03:56:42 2005
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : 1baa875e87:9ec208b2:7f5e6a27:db1f5e
Events : 1
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/.static/dev/sda2
1 8 18 1 active sync /dev/.static/dev/sdb2
2 0 0 - removed
3 8 34 2 active sync /dev/.static/dev/sdc2
** reports version 01.00.01 superblock, but reports as if there were 4
devices used
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -S /dev/md1
** stop the array
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -A /dev/md1
Segmentation fault
** try to assemble the array
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -D /dev/md1
mdadm: md device /dev/md1 does not appear to be active.
** check if its active at all
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -A /dev/md1 /dev/sda2
/dev/sdb2 /dev/sdc2
mdadm: device 1 in /dev/md1 has wrong state in superblock, but /dev/sdb2
seems ok
mdadm: device 2 in /dev/md1 has wrong state in superblock, but /dev/sdc2
seems ok
mdadm: /dev/md1 has been started with 3 drives.
** try restarting it with drive details, and it starts
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -D /dev/md1
/dev/md1:
Version : 00.90.01
Creation Time : Mon Jul 18 02:53:55 2005
Raid Level : raid5
Array Size : 128384 (125.40 MiB 131.47 MB)
Device Size : 64192 (62.70 MiB 65.73 MB)
Raid Devices : 3
Total Devices : 3
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Mon Jul 18 02:53:57 2005
State : clean
Active Devices : 3
Working Devices : 3
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
UUID : e798f37d:baf98c2f:e714b50c:8d1018b1
Events : 0.2
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/.static/dev/sda2
1 8 18 1 active sync /dev/.static/dev/sdb2
2 8 34 2 active sync /dev/.static/dev/sdc2
** magically, we now have a v00.90.01 superblock, it reports the proper
list of drives
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -S /dev/md1
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -A /dev/md1
Segmentation fault
** try to stop and restart again, doesn't work
root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -E /dev/sda2
/dev/sda2:
Magic : a92b4efc
Version : 01.00
Array UUID : 1baa875e87:9ec208b2:7f5e6a27:db1f5e
Name :
Creation Time : Mon Jul 18 03:56:40 2005
Raid Level : raid5
Raid Devices : 3
Device Size : 128504 (62.76 MiB 65.79 MB)
Super Offset : 128504 sectors
State : clean
Device UUID : 1baa875e87:9ec208b2:7f5e6a27:db1f5e
Update Time : Mon Jul 18 03:56:42 2005
Checksum : 903062ed - correct
Events : 1
Layout : left-symmetric
Chunk Size : 64K
Array State : Uuu 1 failed
** the drives themselves still report a version 1 superblock... wierd
-
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 #3: Re: bug report: mdadm-devel-2 , superblock version 1 --]
[-- Type: message/rfc822, Size: 7751 bytes --]
From: Tyler <pml@dtbb.net>
To: linux-raid@vger.kernel.org
Cc: Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: bug report: mdadm-devel-2 , superblock version 1
Date: Sun, 17 Jul 2005 19:19:36 -0700
Message-ID: <42DB11B8.1090501@dtbb.net>
As a side note, do I need any kernel patches to use the version 1
superblocks Neil? That may be what i'm missing.. as the kernel in use
currently is a vanilla 2.6.12.3. I'm not trying to use bitmaps or
anything else at the moment.
Tyler.
Tyler wrote:
> # uname -a
> Linux server 2.6.12.3 #3 SMP Sun Jul 17 14:38:12 CEST 2005 i686 GNU/Linux
> # ./mdadm -V
> mdadm - v2.0-devel-2 - DEVELOPMENT VERSION NOT FOR REGULAR USE - 7
> July 2005
>
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -S /dev/md1
>
> ** stop the current array
>
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -C /dev/md1 -l 5
> --raid-devices 3 -e 1 /dev/sda2 /dev/sdb2 /dev/sdc2
> mdadm: /dev/sda2 appears to be part of a raid array:
> level=5 devices=3 ctime=Mon Jul 18 03:22:05 2005
> mdadm: /dev/sdb2 appears to be part of a raid array:
> level=5 devices=3 ctime=Mon Jul 18 03:22:05 2005
> mdadm: /dev/sdc2 appears to be part of a raid array:
> level=5 devices=3 ctime=Mon Jul 18 03:22:05 2005
> Continue creating array? y
> mdadm: array /dev/md1 started.
>
> ** create and start new array using 3 drives, superblock version 1
>
> root@server:~/dev/mdadm-2.0-devel-2# cat /proc/mdstat
> Personalities : [raid5]
> md1 : active raid5 sdc2[3] sdb2[1] sda2[0]
> 128384 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
>
> unused devices: <none>
>
> ** mdstat mostly okay, except sdc2 is listed as device3 instead of
> device2 (from 0,1,2)
>
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -D /dev/md1
> /dev/md1:
> Version : 01.00.01
> Creation Time : Mon Jul 18 03:56:40 2005
> Raid Level : raid5
> Array Size : 128384 (125.40 MiB 131.47 MB)
> Device Size : 64192 (62.70 MiB 65.73 MB)
> Raid Devices : 3
> Total Devices : 3
> Preferred Minor : 1
> Persistence : Superblock is persistent
>
> Update Time : Mon Jul 18 03:56:42 2005
> State : clean
> Active Devices : 3
> Working Devices : 3
> Failed Devices : 0
> Spare Devices : 0
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> UUID : 1baa875e87:9ec208b2:7f5e6a27:db1f5e
> Events : 1
>
> Number Major Minor RaidDevice State
> 0 8 2 0 active sync
> /dev/.static/dev/sda2
> 1 8 18 1 active sync
> /dev/.static/dev/sdb2
> 2 0 0 - removed
>
> 3 8 34 2 active sync
> /dev/.static/dev/sdc2
>
> ** reports version 01.00.01 superblock, but reports as if there were 4
> devices used
>
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -S /dev/md1
>
> ** stop the array
>
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -A /dev/md1
> Segmentation fault
>
> ** try to assemble the array
>
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -D /dev/md1
> mdadm: md device /dev/md1 does not appear to be active.
>
> ** check if its active at all
>
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -A /dev/md1 /dev/sda2
> /dev/sdb2 /dev/sdc2
> mdadm: device 1 in /dev/md1 has wrong state in superblock, but
> /dev/sdb2 seems ok
> mdadm: device 2 in /dev/md1 has wrong state in superblock, but
> /dev/sdc2 seems ok
> mdadm: /dev/md1 has been started with 3 drives.
>
> ** try restarting it with drive details, and it starts
>
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -D /dev/md1
> /dev/md1:
> Version : 00.90.01
> Creation Time : Mon Jul 18 02:53:55 2005
> Raid Level : raid5
> Array Size : 128384 (125.40 MiB 131.47 MB)
> Device Size : 64192 (62.70 MiB 65.73 MB)
> Raid Devices : 3
> Total Devices : 3
> Preferred Minor : 1
> Persistence : Superblock is persistent
>
> Update Time : Mon Jul 18 02:53:57 2005
> State : clean
> Active Devices : 3
> Working Devices : 3
> Failed Devices : 0
> Spare Devices : 0
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> UUID : e798f37d:baf98c2f:e714b50c:8d1018b1
> Events : 0.2
>
> Number Major Minor RaidDevice State
> 0 8 2 0 active sync
> /dev/.static/dev/sda2
> 1 8 18 1 active sync
> /dev/.static/dev/sdb2
> 2 8 34 2 active sync
> /dev/.static/dev/sdc2
>
> ** magically, we now have a v00.90.01 superblock, it reports the
> proper list of drives
>
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -S /dev/md1
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -A /dev/md1
> Segmentation fault
>
> ** try to stop and restart again, doesn't work
>
> root@server:~/dev/mdadm-2.0-devel-2# ./mdadm -E /dev/sda2
> /dev/sda2:
> Magic : a92b4efc
> Version : 01.00
> Array UUID : 1baa875e87:9ec208b2:7f5e6a27:db1f5e
> Name :
> Creation Time : Mon Jul 18 03:56:40 2005
> Raid Level : raid5
> Raid Devices : 3
>
> Device Size : 128504 (62.76 MiB 65.79 MB)
> Super Offset : 128504 sectors
> State : clean
> Device UUID : 1baa875e87:9ec208b2:7f5e6a27:db1f5e
> Update Time : Mon Jul 18 03:56:42 2005
> Checksum : 903062ed - correct
> Events : 1
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> Array State : Uuu 1 failed
>
> ** the drives themselves still report a version 1 superblock... wierd
> -
> 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
>
-
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
next reply other threads:[~2005-07-23 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 22:28 Tyler [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-23 22:30 Any chance you can look at this Superblock v1 bug Neil? Tyler
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=42E2C47F.409@dtbb.net \
--to=tyler@dtbb.net \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).