Displaying 3 results from an estimated 3 matches for "md0p2".
Did you mean:
md0p1
2020 Nov 15
5
(C8) root on mdraid
....
Calling ioctl() to re-read partition table.
Syncing disks.
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 819.5M 1 loop /run/archiso/sfs/airootfs
sda 8:0 0 232.9G 0 disk
??md0 9:0 0 232.9G 0 raid1
??md0p1 259:0 0 220G 0 part
??md0p2 259:1 0 4G 0 part
sdb 8:16 0 232.9G 0 disk
??md0 9:0 0 232.9G 0 raid1
??md0p1 259:0 0 220G 0 part
??md0p2 259:1 0 4G 0 part
sr0 11:0 1 871M 0 rom
# mkfs -t ext4 /dev/md0p1
mke2fs 1.44.5 (15-Dec-2018)
Creating filesystem with...
2016 Mar 12
4
C7 + UEFI + GPT + RAID1
...several how-to
concerning raid1 installation, I must put each partition on a different
md devices. I've asked times ago if it's more correct create the md
device, partitioning it and create fs on each partition created on md
device:
mdadm create /dev/md0 ...
fdisk /dev/md0:
md0p1 swap
md0p2 / xfs
md0p3 /home xfs
or create for each partition an md device and create the fs on mdX
device directly:
mdadm create /dev/md[012].....
mkfs.fs /dev/mdX (for each md device)
md0 swap
md1 /
md2 /home
I got as answer that the second solution is the correct solution.
I'm installing C7 15...
2012 Sep 18
8
Collecting entropy from device_attach() times.
Hi.
I experimented a bit with collecting entropy from the time it takes for
device_attach() to run (in CPU cycles). It seems that those times have
enough variation that we can use it for entropy harvesting. It happens
even before root is mounted, so pretty early.
On the machine I'm testing it, which has minimal kernel plus NIC driver
I see 75 device_attach() calls. I'm being very careful