Dit deel is nog niet vertaald. Je ziet de Engelse tekst.
Wat het doet
Old signatures confuse tools: mkfs refuses, LVM sees an old PV, the installer shows old RAID members. wipefs DEVICE lists the signatures; wipefs -a DEVICE removes them. Only the few bytes of the signatures are erased, so it is very fast — but the old data is not securely deleted.
Zo schrijf je het
wipefs [OPTION]... DEVICE...Opties 14
Meest gebruikt
Niets past bij dit filter.
Voorbeelden 10
$ als gewone gebruiker# als root (of met sudo)
1List the signatures
wipefs /dev/vdb DEVICE OFFSET TYPE UUID LABEL vdb 0x200 gpt vdb 0x27ffffe00 gpt vdb 0x1fe PMBRGPT has a backup at the end of the disk.
2Remove all signatures of a disk
wipefs -a /dev/vdbThe disk now looks empty for every tool.
3Test first
wipefs -n -a /dev/vdbShows what would be removed.
4Keep a backup of the signatures
wipefs -a -b /dev/vdb1Files like ~/wipefs-vdb1-0x00000000.bak can restore it with dd.
5Remove only one type
wipefs -a -t xfs /dev/vdb1Other signatures stay.
6Partitions first, then the disk
wipefs -a /dev/vdb[0-9]*; wipefs -a /dev/vdbClean reuse of an old disk.
7Before a new LVM PV
wipefs -a /dev/vdc; pvcreate /dev/vdcpvcreate refuses disks with old signatures.
8JSON for automation
wipefs -J /dev/vdbCheck disks in scripts.
9After wipefs: really empty?
lsblk -f /dev/vdbNo FSTYPE, no partitions.
10Secure wipe needs more (security)
blkdiscard /dev/nvme0n1wipefs leaves the data; use blkdiscard (SSD) or a full overwrite to destroy data.
Niets past bij dit filter.
Exitcodes
0 :: Done. 1 :: Error.