* journal disk become the first of --detail list after fail/remove one disk [not found] <1597878292.11264554.1470307437177.JavaMail.zimbra@redhat.com> @ 2016-08-04 10:52 ` Yi Zhang 2016-08-04 11:34 ` Adam Goryachev 0 siblings, 1 reply; 3+ messages in thread From: Yi Zhang @ 2016-08-04 10:52 UTC (permalink / raw) To: linux-raid; +Cc: songliubraving, shli, Jes.Sorensen Hi folks patch[1] has move journal to end of --detail list, but I found after fail/remove the one of the disk, the journal disk change to be the fisrt one, detailed steps pls refer[2] [1] commit 6fe4c6160399c94a15eda6092371e0ac9a38a4bc Author: Song Liu <songliubraving@fb.com> Date: Mon Dec 21 11:23:41 2015 -0800 move journal to end of --detail list [2] Reproduce steps # uname -r 4.7.0 # mdadm --version mdadm - v3.4-63-g52209d6 - 21st July 2016 # mdadm --create --run /dev/md0 --level 4 --metadata 1.2 --raid-devices 7 /dev/loop1 /dev/loop2 /dev/loop3 /dev/loop4 /dev/loop5 /dev/loop6 /dev/loop7 --write-journal /dev/loop0 --bitmap=internal --bitmap-chunk=64M --chunk 512 mdadm: array /dev/md0 started. # mdadm --wait /dev/md0 # mdadm -D /dev/md0 /dev/md0: Version : 1.2 Creation Time : Thu Aug 4 18:42:19 2016 Raid Level : raid4 Array Size : 3139584 (2.99 GiB 3.21 GB) Used Dev Size : 523264 (511.00 MiB 535.82 MB) Raid Devices : 7 Total Devices : 8 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Thu Aug 4 18:42:34 2016 State : clean Active Devices : 7 Working Devices : 8 Failed Devices : 0 Spare Devices : 1 Chunk Size : 512K Name : dhcp-12-125.nay.redhat.com:0 (local to host dhcp-12-125.nay.redhat.com) UUID : 29a267c2:04e91998:639e6eef:64ddbab0 Events : 20 Number Major Minor RaidDevice State 0 7 1 0 active sync /dev/loop1 1 7 2 1 active sync /dev/loop2 2 7 3 2 active sync /dev/loop3 3 7 4 3 active sync /dev/loop4 4 7 5 4 active sync /dev/loop5 5 7 6 5 active sync /dev/loop6 8 7 7 6 active sync /dev/loop7 7 7 0 - journal /dev/loop0 # mdadm /dev/md0 -f /dev/loop1 mdadm: set /dev/loop1 faulty in /dev/md0 # mdadm -D /dev/md0 /dev/md0: Version : 1.2 Creation Time : Thu Aug 4 18:42:19 2016 Raid Level : raid4 Array Size : 3139584 (2.99 GiB 3.21 GB) Used Dev Size : 523264 (511.00 MiB 535.82 MB) Raid Devices : 7 Total Devices : 8 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Thu Aug 4 18:43:07 2016 State : clean, degraded Active Devices : 6 Working Devices : 7 Failed Devices : 1 Spare Devices : 1 Chunk Size : 512K Name : dhcp-12-125.nay.redhat.com:0 (local to host dhcp-12-125.nay.redhat.com) UUID : 29a267c2:04e91998:639e6eef:64ddbab0 Events : 22 Number Major Minor RaidDevice State 7 7 0 - journal /dev/loop0 1 7 2 1 active sync /dev/loop2 2 7 3 2 active sync /dev/loop3 3 7 4 3 active sync /dev/loop4 4 7 5 4 active sync /dev/loop5 5 7 6 5 active sync /dev/loop6 8 7 7 6 active sync /dev/loop7 0 7 1 - faulty /dev/loop1 # mdadm /dev/md0 -r /dev/loop1 mdadm: hot removed /dev/loop1 from /dev/md0 # mdadm -D /dev/md0 /dev/md0: Version : 1.2 Creation Time : Thu Aug 4 18:42:19 2016 Raid Level : raid4 Array Size : 3139584 (2.99 GiB 3.21 GB) Used Dev Size : 523264 (511.00 MiB 535.82 MB) Raid Devices : 7 Total Devices : 7 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Thu Aug 4 18:43:22 2016 State : clean, degraded Active Devices : 6 Working Devices : 7 Failed Devices : 0 Spare Devices : 1 Chunk Size : 512K Name : dhcp-12-125.nay.redhat.com:0 (local to host dhcp-12-125.nay.redhat.com) UUID : 29a267c2:04e91998:639e6eef:64ddbab0 Events : 23 Number Major Minor RaidDevice State 7 7 0 - journal /dev/loop0 1 7 2 1 active sync /dev/loop2 2 7 3 2 active sync /dev/loop3 3 7 4 3 active sync /dev/loop4 4 7 5 4 active sync /dev/loop5 5 7 6 5 active sync /dev/loop6 8 7 7 6 active sync /dev/loop7 Best Regards, Yi Zhang ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: journal disk become the first of --detail list after fail/remove one disk 2016-08-04 10:52 ` journal disk become the first of --detail list after fail/remove one disk Yi Zhang @ 2016-08-04 11:34 ` Adam Goryachev 2016-08-05 8:49 ` Guoqing Jiang 0 siblings, 1 reply; 3+ messages in thread From: Adam Goryachev @ 2016-08-04 11:34 UTC (permalink / raw) To: Yi Zhang, linux-raid; +Cc: songliubraving, shli, Jes.Sorensen On 4/08/2016 20:52, Yi Zhang wrote: > # mdadm -D /dev/md0 > /dev/md0: > Version : 1.2 > Creation Time : Thu Aug 4 18:42:19 2016 > Raid Level : raid4 > Array Size : 3139584 (2.99 GiB 3.21 GB) > Used Dev Size : 523264 (511.00 MiB 535.82 MB) > Raid Devices : 7 > Total Devices : 7 > Persistence : Superblock is persistent > > Intent Bitmap : Internal > > Update Time : Thu Aug 4 18:43:22 2016 > State : clean, degraded > Active Devices : 6 > Working Devices : 7 > Failed Devices : 0 > Spare Devices : 1 > > Chunk Size : 512K > > Name : dhcp-12-125.nay.redhat.com:0 (local to host dhcp-12-125.nay.redhat.com) > UUID : 29a267c2:04e91998:639e6eef:64ddbab0 > Events : 23 > > Number Major Minor RaidDevice State > 7 7 0 - journal /dev/loop0 > 1 7 2 1 active sync /dev/loop2 > 2 7 3 2 active sync /dev/loop3 > 3 7 4 3 active sync /dev/loop4 > 4 7 5 4 active sync /dev/loop5 > 5 7 6 5 active sync /dev/loop6 > 8 7 7 6 active sync /dev/loop7 > I'm not really sure about the journal/your report, but also why does the above show 1 spare device? I would expect spare should mean that there is a device available to take over automatically if one of the active devices becomes faulty, but that doesn't seem to be the case. Should a journal device be counted as Active & Working (or faulty) instead of Spare? Regards, Adam ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: journal disk become the first of --detail list after fail/remove one disk 2016-08-04 11:34 ` Adam Goryachev @ 2016-08-05 8:49 ` Guoqing Jiang 0 siblings, 0 replies; 3+ messages in thread From: Guoqing Jiang @ 2016-08-05 8:49 UTC (permalink / raw) To: Adam Goryachev, Yi Zhang, linux-raid; +Cc: songliubraving, shli, Jes.Sorensen On 08/04/2016 07:34 AM, Adam Goryachev wrote: > > > On 4/08/2016 20:52, Yi Zhang wrote: >> # mdadm -D /dev/md0 >> /dev/md0: >> Version : 1.2 >> Creation Time : Thu Aug 4 18:42:19 2016 >> Raid Level : raid4 >> Array Size : 3139584 (2.99 GiB 3.21 GB) >> Used Dev Size : 523264 (511.00 MiB 535.82 MB) >> Raid Devices : 7 >> Total Devices : 7 >> Persistence : Superblock is persistent >> >> Intent Bitmap : Internal >> >> Update Time : Thu Aug 4 18:43:22 2016 >> State : clean, degraded >> Active Devices : 6 >> Working Devices : 7 >> Failed Devices : 0 >> Spare Devices : 1 >> >> Chunk Size : 512K >> >> Name : dhcp-12-125.nay.redhat.com:0 (local to host >> dhcp-12-125.nay.redhat.com) >> UUID : 29a267c2:04e91998:639e6eef:64ddbab0 >> Events : 23 >> >> Number Major Minor RaidDevice State >> 7 7 0 - journal /dev/loop0 >> 1 7 2 1 active sync /dev/loop2 >> 2 7 3 2 active sync /dev/loop3 >> 3 7 4 3 active sync /dev/loop4 >> 4 7 5 4 active sync /dev/loop5 >> 5 7 6 5 active sync /dev/loop6 >> 8 7 7 6 active sync /dev/loop7 >> > > I'm not really sure about the journal/your report, but also why does > the above show 1 spare device? I would expect spare should mean that > there is a device available to take over automatically if one of the > active devices becomes faulty, but that doesn't seem to be the case. > Should a journal device be counted as Active & Working (or faulty) > instead of Spare? Agree, or maybe "Journal Devices" can be added for it (but both kernel and mdadm need to modify md_u.h I think). Regards, Guoqing ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-08-05 8:49 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1597878292.11264554.1470307437177.JavaMail.zimbra@redhat.com>
2016-08-04 10:52 ` journal disk become the first of --detail list after fail/remove one disk Yi Zhang
2016-08-04 11:34 ` Adam Goryachev
2016-08-05 8:49 ` Guoqing Jiang
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.