Home
last modified time | relevance | path

Searched full:disks (Results 1 – 25 of 72) sorted by relevance

123

/third_party/gptfdisk/
Dcurrent.spec14 Partitioning software for GPT disks and to repair MBR disks. The gdisk,
17 some problems with MBR disks that can be created by buggy partitioning
24 Summary: An fdisk-like partitioning tool for GPT disks
27 An fdisk-like partitioning tool for GPT disks. GPT
31 and the ability to convert MBR disks to GPT format.
68 Summary: A tool for repairing certain types of damage to MBR disks
72 disks. Removes stray GPT data, fixes mis-sized extended partitions,
DREADME.md11 GUID Partition Table (GPT) disks rather than the Master Boot Record (MBR)
12 disks that fdisk modifies. As such, gdisk is an interactive text-mode
18 GPT disks rather than the MBR disks that cfdisk modifies. As such, cgdisk
26 manipulation of GPT disks using command-line options, so it's suitable
31 disks. It's intended to fix certain problems that can be created by
50 GPT-partitioned disks, cgdisk is similarly a workalike for fdisk, and
53 etc.) provide the ability to handle GPT disks, they have certain
57 * The ability to convert MBR-partitioned disks in-place to GPT format,
89 partitioning disks or changing partitioning details; sgdisk is intended for
91 multiple disks for Linux installation.
[all …]
Dcgdisk.824 disks.
42 disks (made with \fBdd\fR, for instance) or raw disk images used by
66 For data (non\-boot) disks, and for boot disks used on BIOS\-based computers
72 Boot disks for EFI\-based systems require an \fIEFI System
100 space. Such free space is not required of GPT disks, but creating it may
180 Change the sector alignment value. Disks with more logical sectors than
184 new disks, GPT fdisk attempts to align partitions on 1 MiB boundaries
185 (2048\-sectors on disks with 512-byte sectors) by default, which optimizes
186 performance for all of these disk types. On pre\-partitioned disks, GPT
188 set 8-sector alignment on disks larger than 300 GB even if lesser alignment
[all …]
DNEWS56 - Added check for too-small disks (most likely to be an issue when trying
89 partition names, so as to correct disks already affected by the preceding
105 some MBR disks.
139 from correctly handling disks over 4 TiB in size.
213 - Minor bug fix in handling of damaged disks. Also, GPT fdisk now reports
247 disks). This feature does not yet work on other platforms, on which the
252 disks, but only on 2.6.32 and later Linux kernels. The verify feature now
361 this translates to 2048 sectors on disks with 512-byte sectors, but it
362 will be something else on disks with other sector sizes.
464 valid. This is done because I've been receiving reports of some disks
[all …]
Dgdisk.844 disks (made with \fBdd\fR, for instance) or raw disk images used by
68 data in, Apple Partition Map (APM) disks, which are used on 680x0\- and
88 For data (non\-boot) disks, and for boot disks used on BIOS\-based computers
94 Boot disks for EFI\-based systems require an \fIEFI System Partition\fR
124 space. Such free space is not required of GPT disks, but creating it may
332 partitions on disks with tightly\-packed partitions; however, if free space was
449 you've added disks to a RAID array, thus creating a virtual disk with space
498 Change the sector alignment value. Disks with more logical sectors per
502 new disks, GPT fdisk attempts to align partitions on 1 MiB boundaries (2048
503 sectors on disks with 512-byte sectors) by default, which optimizes
[all …]
DREADME.Windows7 computers, and most varieties prior to Vista cannot read GPT disks. GPT
8 fdisk is a partition editor for GPT disks, and it will *AUTOMATICALLY
9 CONVERT* MBR disks to GPT form. Therefore, you should **NOT** use GPT fdisk
14 systems almost always use GPT disks and boot in EFI/UEFI mode, but
16 not apply to FixParts, though; that tool works only on MBR disks.
64 Disks are numbered starting from 0, so the preceding command launches gdisk
77 entails no risk to MBR disks, since the program never writes data back to
82 Interface (EFI) and boot from GPT disks. It's safer to edit non-boot disks,
Dsgdisk.839 disks (made with \fBdd\fR, for instance) or raw disk images used by
62 data in, Apple Partition Map (APM) disks, which are used on 680x0\- and
84 For data (non\-boot) disks, and for boot disks used on BIOS\-based computers
90 Boot disks for EFI\-based systems require an \fIEFI System Partition\fR
120 space. Such free space is not required of GPT disks, but creating it may
154 on disks with 512-byte sectors) on freshly formatted disks. This alignment
235 you've added disks to a RAID array, thus creating a virtual disk with space
266 this option is required on MBR or BSD disklabel disks if you intend to save your
267 changes, in order to prevent accidentally damaging such disks.
404 diagnosing partition table problems, particularly on disks with hybrid
[all …]
Dfixparts.cc52 // This switch() statement weeds out disks with GPT signatures and non-MBR in main()
53 // disks so we don't accidentally damage them.... in main()
76 // Do the bulk of the processing on actual MBR disks. First checks for old
Dmbrpart.h78 // Set information on partitions or disks...
102 // Adjust information on partitions or disks...
Dbsd.h17 // I *THINK* that's what's going on. I've seen them at 64 or 512 on disks
18 // with 512-byte blocks and at 2048 on disks with 2048-byte blocks. The
DREADME.OpenSource9 …modeled on Linux fdisk, but used for modifying GUID Partition Table (GPT) disks. The related FixPa…
Dbundle.json3 …modeled on Linux fdisk, but used for modifying GUID Partition Table (GPT) disks. The related FixPa…
Dmbrpart.cc121 * Set information on partitions or disks without *
216 * Get information on partitions or disks.... *
239 * Adjust information on partitions or disks.... *
Dfixparts.8136 likely to be incorrect on disks smaller than about 8 GiB except on Linux.
234 size or on smaller disks partitioned with any but very ancient software.
Dsupport.h55 // Signatures for Apple (APM) disks, multiplied by 0x100000000
Dgpt.cc361 << "but is unusual. The util-linux fdisk program often creates disks like this.\n" in Verify()
369 << "such disks, but this is a violation of the GPT specification and so may cause\n" in Verify()
412 // Format and similar disks).... in Verify()
422 << "in degraded performance on some modern (2009 and later) hard disks.\n"; in Verify()
432 cout << "\nConsult http://www.ibm.com/developerworks/linux/library/l-4kb-sector-disks/\n" in Verify()
905 // Below is unlikely to happen on real disks, but could happen if in LoadPartitions()
1075 // reading MBR disks. If the CRC is invalid, then a warning about in LoadHeader()
1191 // This test should only fail on read-only disks.... in SaveGPTData()
1330 // identical to the main partition table on healthy disks.
2085 // involving unequal-sized disks.
[all …]
/third_party/curl/packages/vms/
Dcurl_gnv_build_steps.txt103 DS10 with IDE disks, taking an hour to run the CURL configure is normal.
250 Note that if src_root: or vms_root: are NFS mounted disks, the
253 You need to copy the source files to VMS mounted disks and create
255 reference local disks. Make sure src_root1:[000000] and
273 If you are not using NFS mounted disks and do not want to have a
/third_party/ntfs-3g/
DTODO.ntfsprogs38 - manual: optimal backup if disks have bad sectors
112 - fully support disks with bad sectors (attrlist attr, unknown bad sectors)
/third_party/littlefs/.github/workflows/
Dtest.yml28 mkdir disks
29 sudo mount -t tmpfs -o size=100m tmpfs disks
30 TESTFLAGS="$TESTFLAGS --disk=disks/disk"
/third_party/ntfs-3g/src/
Dntfs-3g.8.in42 systems on internal disks may be left in an inconsistent state and changes
56 on internal disks are forced to be mounted in read-only mode.
135 file operations and prevent sleeping (notebook) disks spinning
/third_party/libbpf/src/
Dzip.c42 * Zip archive might span multiple files (disks).
56 /* Number of central directory records on all disks or 0xFFFF if ZIP64
/third_party/ntfs-3g/ntfsprogs/
Dntfsclone.8.in216 Ignore disk read errors so disks having bad sectors, e.g. dying disks, can be
/third_party/skia/third_party/externals/abseil-cpp/absl/strings/internal/
Descaping_test_common.h70 "slow disks, bad memory, misconfigured machines, flaky machines, etc." in base64_strings()
/third_party/rust/crates/libc/ci/
Drun.sh16 # It's assume that all images, when run with two disks, will run the `run.sh`
/third_party/openssl/apps/
Dvms_decc_init.c50 /* Preserve case for file names on ODS5 disks. */

123