Home
last modified time | relevance | path

Searched full:disk (Results 1 – 25 of 252) sorted by relevance

1234567891011

/Documentation/admin-guide/
Ddevices.txt20 1 block RAM disk
21 0 = /dev/ram0 First RAM disk
22 1 = /dev/ram1 Second RAM disk
24 250 = /dev/initrd Initial RAM disk
27 /dev/initrd refers to a RAM disk which was preloaded
115 3 block First MFM, RLL and IDE hard disk/CD-ROM interface
116 0 = /dev/hda Master: whole disk (or CD-ROM)
117 64 = /dev/hdb Slave: whole disk (or CD-ROM)
119 For partitions, add to the whole disk device number:
120 0 = /dev/hd? Whole disk
[all …]
Dldm.rst2 LDM - Logical Disk Manager (Dynamic Disks)
13 1MiB journalled database at the end of the physical disk. The size of
14 partitions is limited only by disk space. The maximum number of partitions is
25 Once the LDM driver has divided up the disk, you can use the MD driver to
28 To prevent legacy applications from repartitioning the disk, the LDM creates a
29 dummy MSDOS partition containing one disk-sized partition. This is what is
33 GPT label disk. This is not supported by the Linux LDM driver yet.
39 Below we have a 50MiB disk, divided into seven partitions.
43 The missing 1MiB at the end of the disk is where the LDM database is
67 disk, but the driver will sort them.
[all …]
Diostats.rst6 more extensive disk statistics have been introduced to help measure disk
44 each snapshot of your disk statistics.
71 ultimately handed to the disk, and so it will be counted (and queued)
129 This counts flush requests executed by disk. Not tracked for partitions.
154 a disk address relative to a partition to the disk address relative to
155 the host disk happens much earlier. All merges and timings now happen
156 at the disk level rather than at both the disk and partition level as
175 Note that since the address is translated to a disk-relative one, and no
189 disk and partition statistics are consistent again. Since we still don't
205 In 2.6+, all disk statistics were removed from ``/proc/stat``. In 2.4, they
Dinitrd.rst1 Using the initial RAM disk (initrd)
8 initrd provides the capability to load a RAM disk by the boot loader.
9 This RAM disk can then be mounted as the root file system and programs
27 1) the boot loader loads the kernel and the initial RAM disk
28 2) the kernel converts initrd into a "normal" RAM disk and
58 Loads the specified file as the initial RAM disk. When using LILO, you
59 have to specify the RAM disk image file in /etc/lilo.conf, using the
64 initrd data is preserved but it is not converted to a RAM disk and
77 with the RAM disk mounted as root.
85 disk with the desired initrd content, cd to that directory, and run (as an
[all …]
/Documentation/admin-guide/blockdev/
Dramdisk.rst2 Using the RAM disk block device with Linux
10 4) An Example of Creating a Compressed RAM Disk
16 The RAM disk driver is a way to use main system memory as a block device. It
22 The RAM disk dynamically grows as more space is required. It does this by using
26 The RAM disk supports up to 16 RAM disks by default, and can be reconfigured
31 To use RAM disk support with your system, run './MAKEDEV ram' from the /dev
35 The new RAM disk also has the ability to load compressed RAM disk images,
37 rescue floppy disk.
48 This parameter tells the RAM disk driver to set up RAM disks of N k size. The
80 If you make a boot disk that has LILO, then for the above, you would use::
[all …]
Dfloppy.rst85 inverted convention for the disk change line.
131 disk. If you get a huge amount of "Over/Underrun - retrying"
176 Don't use the disk change line, but assume that the disk was
178 boxes where the disk change line is broken or unsupported.
190 Print informational messages for some operations (disk change
195 Uses a less noisy way to clear the disk change line (which
218 access high capacity disks (up to 1992K on a high density 3 1/2 disk!).
231 ftp://metalab.unc.edu/pub/Linux/utils/disk-management/
/Documentation/ABI/testing/
Dsysfs-fs-f2fs1 What: /sys/fs/f2fs/<disk>/gc_max_sleep_time
7 What: /sys/fs/f2fs/<disk>/gc_min_sleep_time
13 What: /sys/fs/f2fs/<disk>/gc_no_gc_sleep_time
19 What: /sys/fs/f2fs/<disk>/gc_idle
31 What: /sys/fs/f2fs/<disk>/reclaim_segments
41 What: /sys/fs/f2fs/<disk>/main_blkaddr
46 What: /sys/fs/f2fs/<disk>/ipu_policy
72 What: /sys/fs/f2fs/<disk>/min_ipu_util
78 What: /sys/fs/f2fs/<disk>/min_fsync_blocks
84 What: /sys/fs/f2fs/<disk>/min_seq_blocks
[all …]
Dsysfs-block-bcache1 What: /sys/block/<disk>/bcache/unregister
11 What: /sys/block/<disk>/bcache/clear_stats
17 What: /sys/block/<disk>/bcache/cache
24 What: /sys/block/<disk>/bcache/cache_hits
31 What: /sys/block/<disk>/bcache/cache_misses
37 What: /sys/block/<disk>/bcache/cache_hit_ratio
43 What: /sys/block/<disk>/bcache/sequential_cutoff
51 What: /sys/block/<disk>/bcache/bypassed
59 What: /sys/block/<disk>/bcache/writeback
68 What: /sys/block/<disk>/bcache/writeback_running
[all …]
Dsysfs-fs-ext41 What: /sys/fs/ext4/<disk>/mb_stats
10 What: /sys/fs/ext4/<disk>/mb_group_prealloc
18 What: /sys/fs/ext4/<disk>/mb_max_to_scan
25 What: /sys/fs/ext4/<disk>/mb_min_to_scan
32 What: /sys/fs/ext4/<disk>/mb_order2_req
40 What: /sys/fs/ext4/<disk>/mb_stream_req
51 What: /sys/fs/ext4/<disk>/inode_readahead_blks
59 What: /sys/fs/ext4/<disk>/delayed_allocation_blocks
67 What: /sys/fs/ext4/<disk>/lifetime_write_kbytes
75 What: /sys/fs/ext4/<disk>/session_write_kbytes
[all …]
Dsysfs-fs-xfs1 What: /sys/fs/xfs/<disk>/log/log_head_lsn
10 What: /sys/fs/xfs/<disk>/log/log_tail_lsn
18 What: /sys/fs/xfs/<disk>/log/reserve_grant_head_bytes
28 What: /sys/fs/xfs/<disk>/log/write_grant_head_bytes
Dsysfs-power16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
42 What: /sys/power/disk
46 The /sys/power/disk file controls the operating mode of the
47 suspend-to-disk mechanism. Reading from this file returns
51 'firmware' - means that the memory image will be saved to disk
65 Additionally, /sys/power/disk can be used to turn on one of the
66 two testing modes of the suspend-to-disk mechanism: 'testproc'
67 or 'test'. If the suspend-to-disk mechanism is in the
68 'testproc' mode, writing 'disk' to /sys/power/state will cause
71 the 'test' mode, writing 'disk' to /sys/power/state will cause
[all …]
/Documentation/ABI/stable/
Dsysfs-block1 What: /sys/block/<disk>/alignment_offset
10 offset from the disk's natural alignment.
13 What: /sys/block/<disk>/discard_alignment
24 What: /sys/block/<disk>/atomic_write_max_bytes
42 What: /sys/block/<disk>/atomic_write_unit_min_bytes
53 What: /sys/block/<disk>/atomic_write_unit_max_bytes
64 What: /sys/block/<disk>/atomic_write_boundary_bytes
78 What: /sys/block/<disk>/diskseq
82 The /sys/block/<disk>/diskseq files reports the disk
90 What: /sys/block/<disk>/inflight
[all …]
/Documentation/driver-api/md/
Draid5-cache.rst5 Raid 4/5/6 could include an extra disk for data cache besides normal RAID
6 disks. The role of RAID disks isn't changed with the cache disk. The cache disk
19 In both modes, all writes to the array will hit cache disk first. This means
20 the cache disk must be fast and sustainable.
34 The write-through cache will cache all data on cache disk first. After the data
35 is safe on the cache disk, the data will be flushed onto RAID disks. The
40 filesystems) after the data is safe on RAID disks, so cache disk failure
41 doesn't cause data loss. Of course cache disk failure means the array is
44 In write-through mode, the cache disk isn't required to be big. Several
51 cached on cache disk. But the main goal of 'write-back' cache is to speed up
[all …]
/Documentation/power/
Dswsusp.rst11 If you touch anything on disk between suspend and resume...
20 problems. If your disk driver does not support suspend... (IDE does),
45 echo shutdown > /sys/power/disk; echo disk > /sys/power/state
49 echo platform > /sys/power/disk; echo disk > /sys/power/state
54 echo suspend > /sys/power/disk; echo disk > /sys/power/state
57 support. For suspend and resume to work, make sure your disk drivers
59 suspend/resume with modular disk drivers, see FAQ, but you probably
123 echo 4 > /proc/acpi/sleep # for suspend to disk
128 echo 4b > /proc/acpi/sleep # for suspend to disk via s4bios
139 bringing machine down? Suspend to disk, rearrange power cables,
[all …]
Dbasic-pm-debugging.rst7 1. Testing hibernation (aka suspend to disk or STD)
12 # echo reboot > /sys/power/disk
13 # echo disk > /sys/power/state
26 # echo platform > /sys/power/disk
27 # echo disk > /sys/power/state
35 # echo shutdown > /sys/power/disk
36 # echo disk > /sys/power/state
83 # echo platform > /sys/power/disk
84 # echo disk > /sys/power/state
180 /sys/power/disk generally tells the kernel what to do after creating a
[all …]
/Documentation/admin-guide/aoe/
Dudev.txt19 SUBSYSTEM=="aoe", KERNEL=="discover", NAME="etherd/%k", GROUP="disk", MODE="0220"
20 SUBSYSTEM=="aoe", KERNEL=="err", NAME="etherd/%k", GROUP="disk", MODE="0440"
21 SUBSYSTEM=="aoe", KERNEL=="interfaces", NAME="etherd/%k", GROUP="disk", MODE="0220"
22 SUBSYSTEM=="aoe", KERNEL=="revalidate", NAME="etherd/%k", GROUP="disk", MODE="0220"
23 SUBSYSTEM=="aoe", KERNEL=="flush", NAME="etherd/%k", GROUP="disk", MODE="0220"
26 KERNEL=="etherd*", GROUP="disk"
/Documentation/filesystems/ext4/
Dallocators.rst7 generally a desirably quality of a filesystem. On a spinning disk,
9 that the head actuator and disk must perform to access a data block,
10 thus speeding up disk IO. On an SSD there of course are no moving parts,
19 speculatively allocates 8KiB of disk space to the file on the assumption
26 the filesystem defers deciding the exact placement on the disk until all
27 the dirty buffers are being written out to disk. By not committing to a
43 The fifth trick is that the disk volume is cut up into 128MB block
49 over a disk; as the top-level directory/file blobs fill up one block
Dattributes.rst7 block on the disk and referenced from inodes via ``inode.i_file_acl*``.
68 - Number of disk blocks used.
113 - Location of this attribute's value on the disk block where it is stored.
143 put into a separate disk block. If the disk block fills up, the
154 of on-disk space that the keys consume, the beginning of the key string
183 index is set to 1 and the “fubar” name is recorded on disk.
Djournal.rst10 “important” data writes on-disk as quickly as possible. Once the important
11 data transaction is fully written to the disk and flushed from the disk write
14 final locations on disk (this could involve a lot of seeking or a lot of small
18 gets written through the journal to the disk. The effect of this is to
27 metadata are written to disk through the journal. This is slower but
29 disk before the metadata are written to disk through the journal.
46 middle of the disk.
48 All fields in jbd2 are written to disk in big-endian order. This is the
314 - This journal uses v2 of the checksum on-disk format. Each journal
319 - This journal uses v3 of the checksum on-disk format. This is the same as
[all …]
Dblockgroup.rst40 across the disk in case the beginning of the disk gets trashed, though
75 large files to be continuous on disk. Backup copies of the superblock
93 descriptor structures can be stored in a single disk block. For ext4
95 includes 64 block groups, or 8 GiB of disk space. The metablock group
126 therefore the on-disk bitmap blocks are not initialized. This is
/Documentation/admin-guide/device-mapper/
Ddm-log.rst5 RAID targets to track regions of the disk that are not consistent.
6 A region (or portion of the address space) of the disk may be
23 disk drivers/md/dm-log.c
28 The "disk" log type
30 This log implementation commits the log state to disk. This way, the
54 framework - "clustered-disk" and "clustered-core". These implementations
/Documentation/networking/devlink/
Ddevlink-flash.rst52 the board, and the driver loads the rest from disk during probing.
57 disk, or automatically flash a new image from disk. The ``fw_load_policy``
61 On-disk firmware files are usually stored in ``/lib/firmware/``.
102 # Update on-disk file if necessary
104 $file = some-db-backed.download($hw_id, 'disk')
/Documentation/admin-guide/laptops/
Ddisk-shock-protection.rst2 Hard disk shock protection
23 unload disk heads. This feature is being used in modern laptops in
29 implement a generic disk head parking interface in the Linux kernel.
31 system in order to get disk shock protection working (see
46 no further disk head park request has been issued in the meantime,
100 than its libata counterpart (i.e. your disk is called /dev/hda
140 See this page for information about Linux support of the hard disk
147 This implementation of disk head parking has been inspired by a patch
/Documentation/filesystems/
Dsysv-fs.rst16 * To mount a disk or a partition, use::
40 for this FS on hard disk yet.
52 * Size of a block or zone (data allocation unit on disk)
64 * Byte ordering of "short" (16 bit entities) on disk:
73 * Byte ordering of "long" (32 bit entities) on disk:
82 * Inode on disk: "short", 0 means non-existent, the root dir ino is:
234 * Directory entry on disk
264 and not the disk driver's notion of "block".
/Documentation/block/
Dcmdline-partition.rst20 block device disk name. Embedded device uses fixed block device.
21 Its disk name is also fixed, such as: mmcblk0, mmcblk1, mmcblk0boot0.
44 eMMC disk names are "mmcblk0" and "mmcblk0boot0".

1234567891011