Timeline for How to remove 1 disk from a raid-5 mdadm array?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 8, 2017 at 16:04 | comment | added | Chris Davies | @derobert I now can't see where I got the 2TB→1TB reduction either. I would have expected 3TB from 4 disks, which is why I was puzzled. | |
| Sep 8, 2017 at 15:12 | comment | added | Anton S. | exact, i had a raid-5 of 4x1 Tb (3 Tb) and wanted to make it a 3x1 Tb (2 Tb) | |
| Sep 8, 2017 at 14:59 | comment | added | derobert | (Unless you're misreading the sizes from mdadm -D—that's telling you the array uses 1TB on each disk and has 2TB total available, which is what you expect for 3×1TB in RAID5) | |
| Sep 8, 2017 at 14:57 | comment | added | derobert | The filesystem superblock size is 732473472 blocks ≈ 2.8TiB and the new size is 488315648 blocks ≈ 1.9TiB so I'm not sure where you got 2→1TB. The messages show 3→2TB as expected. | |
| Sep 8, 2017 at 14:38 | comment | added | Chris Davies | @AntonS. comments are for commenting. Updates like this I'm asking you for, go into your question for everyone to find easily. (Don't forget the formatting.) Then I can delete my comments because they're no longer required. | |
| Sep 8, 2017 at 14:34 | comment | added | Anton S. | alas, this site does not allow long comments. otherwise i'd copy everything that mdadm --examine returns. | |
| Sep 8, 2017 at 14:29 | comment | added | Chris Davies | @AntonS. without the mdadm details for the remaining physical devices I can't make any other suggestions. | |
| Sep 8, 2017 at 14:28 | comment | added | Anton S. | root@darkstar:/home/anton# mdadm --examine /dev/md0 mdadm: No md superblock detected on /dev/md0. | |
| Sep 8, 2017 at 14:27 | comment | added | Anton S. | i didn't want to replace the disk, i wanted to remove it. | |
| Sep 8, 2017 at 14:24 | history | answered | Chris Davies | CC BY-SA 3.0 |