Search results
From Linux Raid Wiki
- |- padding:5px;padding-top:0.5em;font-size: 95%; Arrays can be built on top of entire disks or on partitions.30 KB (4,964 words) - 00:24, 28 September 2020
- |- padding:5px;padding-top:0.5em;font-size: 95%; * There is no redundancy in this level. If one disk fails, you will most likely lose all your data. You may be ab17 KB (2,944 words) - 15:42, 1 April 2019
- |- padding:5px;padding-top:0.5em;font-size: 95%; ...all operations that change the size of an array, such as changing the raid level, changing the number of active devices, etc.29 KB (4,716 words) - 10:31, 7 May 2018
- |- padding:5px;padding-top:0.5em;font-size: 95%; mdadm --create --auto=mdp --verbose /dev/md_d0 --level=mirror --raid-devices=2 /dev/sda /dev/sdb5 KB (805 words) - 11:38, 4 April 2011
- |- padding:5px;padding-top:0.5em;font-size: 95%; single drive failure. The wrong choice of raid level, for example. And it is common6 KB (1,048 words) - 22:42, 3 October 2016
- |- padding:5px;padding-top:0.5em;font-size: 95%; mdadm --create /dev/md/root --level raid1 --raid-disks 2 missing /dev/sdb115 KB (2,626 words) - 20:52, 20 September 2016
- |- padding:5px;padding-top:0.5em;font-size: 95%; ...e grown to use the new disks. After the new disk was partitioned, the RAID level 1/4/5/6 array can be grown for example using this command (assuming that be9 KB (1,457 words) - 20:54, 20 September 2016
- |- padding:5px;padding-top:0.5em;font-size: 95%; ...w the raid array, it will recover it for you, but what it needs is for the level below to provide integrity and not corrupted data.2 KB (303 words) - 20:18, 30 November 2019
- |- padding:5px;padding-top:0.5em;font-size: 95%; ...storage as block devices. It is also quite happy to layer block devices on top of each other. The devices we need to consider are disk drives, raid arrays7 KB (1,299 words) - 20:17, 10 May 2020
- |- padding:5px;padding-top:0.5em;font-size: 95%; Raid Level : raid523 KB (3,293 words) - 11:07, 5 May 2011
- |- padding:5px;padding-top:0.5em;font-size: 95%; raid-level 18 KB (1,197 words) - 20:41, 20 September 2016
- |- padding:5px;padding-top:0.5em;font-size: 95%; [[Overview#FAULTY|FAULTY RAID level]] - don't get confused - this is a5 KB (842 words) - 21:49, 26 September 2016
- |- padding:5px;padding-top:0.5em;font-size: 95%; 305664 blocks super 1.2 level 6, 512k chunk, algorithm 2 [5/3] [_UU_U]7 KB (1,100 words) - 22:01, 18 November 2016
- |- padding:5px;padding-top:0.5em;font-size: 95%; ...ble at present. That said, btrfs applies redundancy at a far finer-grained level than can be done by lvm or md-raid lying underneath the file system. The cu9 KB (1,607 words) - 20:21, 30 November 2019
- |- padding:5px;padding-top:0.5em;font-size: 95%; Top of the list is a --replace that can't read a failing drive. This is a sensi7 KB (1,250 words) - 21:09, 6 May 2018
- |- padding:5px;padding-top:0.5em;font-size: 95%; mdadm --create /dev/md/root --level=1 --raid-devices=2 /dev/sdb3 missing7 KB (1,240 words) - 22:54, 16 November 2016