Searched full:sector (Results 1 – 25 of 54) sorted by relevance
123
| /Documentation/device-mapper/ |
| D | dm-bow.txt | 23 that sector 0 is used to keep a log of the latest changes, both to indicate that
27 State 2: The transition to state 2 triggers replacing the special sector 0 with
28 the normal sector 0, and the freeing of all state information. dm_bow then
48 dm_bow maintains a type for all sectors. A sector can be any of:
57 SECTOR0 is the first sector on the device, and is used to hold the log of
60 SECTOR0_CURRENT is a sector picked from the FREE sectors, and is where reads and
61 writes from the true sector zero are redirected to. Note that like any backup
62 sector, if the sector is written to directly, it must be moved again.
64 UNCHANGED means that the sector has not been changed since we entered state 1.
67 FREE means that the sector was trimmed in state 0 and has not yet been written
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 6 per-sector tags that can be used for storing integrity information.
8 A general problem with storing integrity tags with every sector is that
9 writing the sector and the integrity tag must be atomic - i.e. in case of
10 crash, either both sector and integrity tag or none of them is written.
13 writes sector data and integrity tags into a journal, commits the journal
53 2. load the dm-integrity target with one-sector size, the kernel driver
67 2. the number of reserved sector at the beginning of the device - the
155 an attacker reading the journal could see the last sector numbers
156 that were written. From the sector numbers, the attacker can infer
161 Protect sector numbers in the journal from accidental or malicious
[all …]
|
| D | dm-crypt.rst | 78 then sectors are encrypted according to their offsets (sector 0 uses key0;
79 sector 1 uses key1 etc.). <keycount> must be a power of two.
82 The IV offset is a sector count that is added to the sector number
91 Starting sector within the device where the encrypted data begins.
138 The device requires additional <bytes> metadata per-sector stored
152 Virtual device will announce this size as a minimal IO and logical sector.
155 IV generators will use sector number counted in <sector_size> units
159 sector will be 8 (without flag) and 1 if iv_large_sectors is present.
|
| D | dm-dust.rst | 22 This emulates the "remapped sector" behavior of a drive with bad
286 specified sector (sector 0x1234, hardcoded in the source code), but
293 When a bad sector occurs on a hard disk drive, reads to that sector
296 the sector may succeed, and result in the sector becoming readable
298 sector (or after a reallocation of the sector). However, there may
303 of a bad sector at a known sector location, at a known time, based
|
| D | dm-ebs.rst | 26 Starting sector within the device;
42 Emulate 1 sector = 512 bytes logical block size on /dev/sda starting at
47 Emulate 2 sector = 1KiB logical block size on /dev/sda starting at
|
| D | kcopyd.rst | 18 block-device along with the starting sector and size of the region. The source
24 sector_t sector;
|
| D | dm-io.rst | 11 sector and size of the region::
15 sector_t sector;
|
| D | log-writes.rst | 68 <#logged entries> <highest allocated sector>
72 highest allocated sector Highest allocated sector
|
| D | writecache.rst | 9 When the device is constructed, the first sector should be zeroed or the
10 first sector should contain valid superblock from previous invocation.
|
| D | delay.rst | 19 optionally different sector offset
|
| D | linear.rst | 14 Starting sector within the device.
|
| D | striped.rst | 21 Starting sector within the device.
|
| D | dm-flakey.rst | 31 Starting sector within the device.
|
| /Documentation/devicetree/bindings/mtd/ |
| D | atmel-nand.txt | 143 - atmel,pmecc-sector-size : sector size for ECC computation. Supported values
146 for different sector size. First one is for sector size 512, the next is for
147 sector size 1024. If not specified, driver will build the table in runtime.
198 atmel,pmecc-sector-size = <512>;
|
| D | brcm,brcmnand.yaml | 134 brcm,nand-oob-sector-size:
136 integer, to denote the spare area sector size
220 brcm,nand-oob-sector-size: false
|
| D | mtd-physmap.yaml | 102 use-advanced-sector-protection:
105 Enables support for the advanced sector protection (Spansion: PPB -
|
| /Documentation/driver-api/mmc/ |
| D | mmc-dev-attrs.rst | 37 rel_sectors Reliable write sector count
51 always one 512 byte sector. For SD, "erase_size" is 512
72 (especially for SD where it is just one sector),
|
| D | mmc-tools.rst | 18 - Set the eMMC data sector size to 4KB by disabling emulation.
|
| /Documentation/block/ |
| D | data-integrity.rst | 20 checksum for each sector as well as an incrementing counter that
46 information to each sector. The data + integrity metadata is stored
97 and the block layer make things like hardware sector size and
117 Some storage devices allow each hardware sector to be tagged with a
202 sector must be set, and the bio should have all data pages
232 the sector numbers will be remapped as the request traverses the
|
| D | deadline-iosched.rst | 36 write) which are serviced in increasing sector order. To limit extra seeking,
69 rbtree front sector lookup when the io scheduler merge function is called.
|
| /Documentation/userspace-api/ioctl/ |
| D | hdio.rst | 77 start starting sector of this partition.
91 purely by sector number nowadays (lba addressing), and the
296 SECTOR
319 SECTOR If out_flags.b.sector is set
348 SECTOR
421 args[1] SECTOR
448 args[3]. SECTOR, LCYL and HCYL are undefined. For
489 args[3] SECTOR
503 args[3] SECTOR
|
| /Documentation/ABI/stable/ |
| D | sysfs-block | 349 [RO] This is the hardware sector size of the device, in bytes.
358 capable of executing requests targeting different sector ranges
361 correctly advertises the sector ranges of its actuators.
364 per access range, with each range described using the sector
365 (RO) attribute file to indicate the first sector of the range
367 number of sectors in the range starting from the first sector of
375 | `-- sector
378 `-- sector
380 The sector and nr_sectors attributes use 512B sector unit,
384 order of the range start sector, that is, the sector attribute
|
| /Documentation/driver-api/nvdimm/ |
| D | btt.rst | 19 The Block Translation Table (BTT) provides atomic sector update semantics for
20 persistent memory devices, so that applications that rely on sector writes not
25 provides atomic sector updates.
126 The BTT provides sector atomicity by making every write an "allocating write",
279 For example, the ndctl command line to setup a btt with a 4k sector size is::
281 ndctl create-namespace -f -e namespace0.0 -m sector -l 4k
|
| /Documentation/filesystems/ |
| D | udf.rst | 11 dvd+rw drives and media support true random sector writes, and so a udf
16 and read-modify-write cycles to allow the filesystem random sector writes
|
| D | zonefs.rst | 76 The super block is always written on disk at sector 0. The first zone of the
90 the device only has a single conventional zone at sector 0, the zone will not
110 increasing zone start sector on the device.
136 the file's zone write pointer position relative to the zone start sector.
199 requests with a start sector that does not correspond to a zone write pointer
213 causing all data to be dropped after the sector that caused the error.
218 vs write) and on the reason for the error (bad sector, unaligned writes or zone
485 physical sector size.
|
123