Dit deel is nog niet vertaald. Je ziet de Engelse tekst.
Wat het doet
After you change partitions, the kernel must learn the new table. fdisk and parted try this themselves; when the disk is in use, the kernel may keep the old table. partprobe DEVICE asks again, so new partitions appear in /dev without a reboot.
Zo schrijf je het
partprobe [-d] [-s] [DEVICE]...Opties 5
Meest gebruikt
Niets past bij dit filter.
Voorbeelden 10
$ als gewone gebruiker# als root (of met sudo)
1After fdisk
partprobe /dev/vdb lsblk /dev/vdbNew partitions now have device files.
2Show what it found
partprobe -s /dev/vdb /dev/vdb: gpt partitions 1 2 3Quick check.
3All disks
partprobeProbes every disk.
4When it fails
partprobe /dev/vda Error: Partition(s) 2 on /dev/vda have been written, but we have been unable to inform the kernel...The disk is busy (system disk). A reboot may be needed, or use
partx.5Alternative: partx
partx -u /dev/vdbUpdates only the changed partitions.
6Wait for udev to create the devices
partprobe /dev/vdb; udevadm settleIn scripts, before mkfs.
7Dry run
partprobe -d -s /dev/vdbTest without changing anything.
8After growing a VM disk
echo 1 > /sys/class/block/vdb/device/rescan; partprobe /dev/vdbThe kernel learns the new disk size (for SCSI/virtio with rescan support).
9Check the result with the kernel view
cat /proc/partitionsThe kernel's list of partitions.
10In an automated disk setup
parted -s /dev/vdb mklabel gpt mkpart data xfs 1MiB 100% && partprobe /dev/vdb && mkfs.xfs /dev/vdb1Each step only when the step before worked.
Niets past bij dit filter.
Exitcodes
0 :: Done. 1 :: Error.