| /OK3568_Linux_fs/buildroot/fs/cpio/ |
| H A D | Config.in | 2 bool "cpio the root filesystem (for use as an initial RAM filesystem)"
4 Build a cpio archive of the root filesystem. This is typically
5 used for an initial RAM filesystem that is passed to the
14 Select compressor for cpio filesystem of the root filesystem.
15 If you use the cpio archive as an initial RAM filesystem, make
22 Do not compress the cpio filesystem.
27 Do compress the cpio filesystem with gzip.
32 Do compress the cpio filesystem with bzip2.
37 Do compress the cpio filesystem with lz4.
42 Do compress the cpio filesystem with lzma.
[all …]
|
| /OK3568_Linux_fs/buildroot/fs/ext2/ |
| H A D | Config.in | 2 bool "ext2/3/4 root filesystem"
5 Build an ext2/3/4 root filesystem
45 string "filesystem label"
53 The size of the filesystem image. If it does not have a
67 The number of blocks on the filesystem (as a percentage of the
71 filesystem.
78 any ext2/3/4 filesystem features.
86 The default is "-O ^64bit", i.e. disable 64-bit filesystem
88 versions before 2017.02 don't support this filesystem
89 option: using it may make the filesystem unreadable by
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/ |
| H A D | fuse.rst | 10 Userspace filesystem:
11 A filesystem in which data and metadata are provided by an ordinary
12 userspace process. The filesystem can be accessed normally through
16 The process(es) providing the data and metadata of the filesystem.
19 A userspace filesystem mounted by a non-privileged (non-root) user.
20 The filesystem daemon is running with the privileges of the mounting
25 A connection between the filesystem daemon and the kernel. The
26 connection exists until either the daemon dies, or the filesystem is
27 umounted. Note that detaching (or lazy umounting) the filesystem
29 the last reference to the filesystem is released.
[all …]
|
| H A D | overlayfs.rst | 10 overlay-filesystem functionality in Linux (sometimes referred to as
11 union-filesystems). An overlay-filesystem tries to present a
12 filesystem which is the result over overlaying one filesystem on top
19 The overlay filesystem approach is 'hybrid', because the objects that
20 appear in the filesystem do not always appear to belong to that filesystem.
22 from accessing the corresponding object from the original filesystem.
25 While directories will report an st_dev from the overlay-filesystem,
26 non-directory objects may report an st_dev from the lower filesystem or
27 upper filesystem that is providing the object. Similarly st_ino will
33 filesystem, all objects will report an st_dev from the overlay
[all …]
|
| H A D | ext2.rst | 10 filesystem in use by Linux. There are also implementations available
16 Most defaults are determined by the filesystem superblock, and can be
32 errors=continue Keep going on a filesystem error.
33 errors=remount-ro Remount the filesystem read-only on an error.
89 which is decided when the filesystem is created. Smaller blocks mean
91 and also impose other limits on the size of files and the filesystem.
116 to mounting the filesystem. Since it is so important, backup copies of
117 the superblock are stored in block groups throughout the filesystem.
126 number of inodes and blocks in the filesystem and how many are free,
127 how many inodes and blocks are in each block group, when the filesystem
[all …]
|
| H A D | mount_api.rst | 11 (2) The filesystem context.
13 (3) The filesystem context operations.
17 (5) VFS filesystem context API.
31 (1) Create a filesystem context.
52 The first is invoked to set up the filesystem-specific parts of a filesystem
57 Note that security initialisation is done *after* the filesystem is called so
64 The creation and reconfiguration of a superblock is governed by a filesystem
93 These are operations that can be done on a filesystem context (see
101 A pointer to the file_system_type of the filesystem that is being
108 A pointer to the file system's private data. This is where the filesystem
[all …]
|
| H A D | ocfs2-online-filecheck.rst | 12 converts the filesystem to read-only when encounters an error. This may not be
13 necessary, since turning the filesystem read-only would affect other running
17 filesystem is not corrupted further. The filesystem is not converted to
24 of a cluster filesystem by turning the filesystem read-only. The scope of
26 to all files (including system files) of the filesystem.
32 other components of the filesystem, such as but not limited to, checking if the
36 Finally, such an operation/feature should not be automated lest the filesystem
42 When there are errors in the OCFS2 filesystem, they are usually accompanied
91 On receiving the inode, the filesystem would read the inode and the
92 file metadata. In case of errors, the filesystem would fix the errors
|
| H A D | gfs2-uevents.rst | 18 uevent generated by the newly created filesystem. If the mount
25 of the filesystem respectively.
40 successful mount of the filesystem by the first node (FIRSTMOUNT=Done).
42 nodes in the cluster to mount the filesystem.
63 The OFFLINE uevent is only generated due to filesystem errors and is used
72 or at the end of a umount of the filesystem. All REMOVE uevents will
73 have been preceded by at least an ADD uevent for the same filesystem,
85 line (locktable=) or via fstab. It is used as a filesystem label
100 If a journal is in use by the filesystem (journals are not
108 into the filesystem superblock. If it exists, this will
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/include/c++/10.3.1/bits/ |
| H A D | fs_dir.h | 47 namespace filesystem in _GLIBCXX_VISIBILITY()
105 directory_entry(const filesystem::path& __p) in _GLIBCXX_VISIBILITY()
109 directory_entry(const filesystem::path& __p, error_code& __ec) in _GLIBCXX_VISIBILITY()
124 assign(const filesystem::path& __p) in _GLIBCXX_VISIBILITY()
131 assign(const filesystem::path& __p, error_code& __ec) in _GLIBCXX_VISIBILITY()
138 replace_filename(const filesystem::path& __p) in _GLIBCXX_VISIBILITY()
145 replace_filename(const filesystem::path& __p, error_code& __ec) in _GLIBCXX_VISIBILITY()
160 const filesystem::path& path() const noexcept { return _M_path; } in _GLIBCXX_VISIBILITY()
161 operator const filesystem::path& () const noexcept { return _M_path; } in _GLIBCXX_VISIBILITY()
165 { return filesystem::exists(file_status{_M_file_type()}); } in _GLIBCXX_VISIBILITY()
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/include/c++/10.3.1/bits/ |
| H A D | fs_dir.h | 47 namespace filesystem in _GLIBCXX_VISIBILITY()
105 directory_entry(const filesystem::path& __p) in _GLIBCXX_VISIBILITY()
109 directory_entry(const filesystem::path& __p, error_code& __ec) in _GLIBCXX_VISIBILITY()
124 assign(const filesystem::path& __p) in _GLIBCXX_VISIBILITY()
131 assign(const filesystem::path& __p, error_code& __ec) in _GLIBCXX_VISIBILITY()
138 replace_filename(const filesystem::path& __p) in _GLIBCXX_VISIBILITY()
145 replace_filename(const filesystem::path& __p, error_code& __ec) in _GLIBCXX_VISIBILITY()
160 const filesystem::path& path() const noexcept { return _M_path; } in _GLIBCXX_VISIBILITY()
161 operator const filesystem::path& () const noexcept { return _M_path; } in _GLIBCXX_VISIBILITY()
165 { return filesystem::exists(file_status{_M_file_type()}); } in _GLIBCXX_VISIBILITY()
[all …]
|
| /OK3568_Linux_fs/kernel/fs/ext4/ |
| H A D | Kconfig | 6 tristate "The Extended 3 (ext3) filesystem"
10 filesystem is now handled by the ext4 driver.
19 filesystem is now handled by the ext4 driver.
27 filesystem is now handled by the ext4 driver.
30 tristate "The Extended 4 (ext4) filesystem"
38 This is the next generation of the ext3 filesystem.
40 Unlike the change from ext2 filesystem to ext3 filesystem,
43 physical block numbers. The ext4 filesystem also supports delayed
49 The ext4 filesystem supports mounting an ext3 filesystem; while there
52 features in the filesystem using tune2fs, or formatting a new
[all …]
|
| /OK3568_Linux_fs/external/rk_pcba_test/pcba_minui/mtdutils/ |
| H A D | mounts.c | 29 const char *filesystem; member
50 free((char *)volume->filesystem); in free_volume_internals()
118 char filesystem[64]; in scan_mounted_volumes() local
125 device, mount_point, filesystem, flags); in scan_mounted_volumes()
130 filesystem[sizeof(filesystem)-1] = '\0'; in scan_mounted_volumes()
137 v->filesystem = strdup(filesystem); in scan_mounted_volumes()
219 return mount(volume->device, volume->mount_point, volume->filesystem, in remount_read_only()
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-filesystems/recipes-utils/exfat-utils/ |
| H A D | exfat-utils_1.3.0.bb | 1 SUMMARY = "utilities to create, check, label and dump exFAT filesystem"
2 DESCRIPTION = "Utilities to manage extended file allocation table filesystem. \
3 This package provides tools to create, check and label the filesystem. It \
5 - dumpexfat to dump properties of the filesystem \
6 - exfatfsck / fsck.exfat to report errors found on a exFAT filesystem \
7 - exfatlabel to label a exFAT filesystem \
8 - mkexfatfs / mkfs.exfat to create a exFAT filesystem. \
|
| /OK3568_Linux_fs/external/recovery/mtdutils/ |
| H A D | mounts.c | 44 free((char *)volume->filesystem); in free_volume_internals()
112 char filesystem[64]; in scan_mounted_volumes() local
119 device, mount_point, filesystem, flags); in scan_mounted_volumes()
124 filesystem[sizeof(filesystem) - 1] = '\0'; in scan_mounted_volumes()
131 v->filesystem = strdup(filesystem); in scan_mounted_volumes()
213 return mount(volume->device, volume->mount_point, volume->filesystem, in remount_read_only()
|
| /OK3568_Linux_fs/buildroot/support/misc/ |
| H A D | target-dir-warning.txt | 4 This directory does *not* contain the root filesystem that you can use
8 filesystem.
11 your root filesystem over NFS or copy the contents of this directory
12 to a SD card or USB key, thinking it will work as the root filesystem
15 Instead, if you need a usable root filesystem, please select one of
16 the filesystem image formats available in the Buildroot configuration
18 sub-menu. If you want to get a filesystem image that you can easily
20 please use the "tar the root filesystem" option. It will generate a
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | customize-rootfs.txt | 5 === Customizing the generated target filesystem
8 there are a few other ways to customize the resulting target filesystem.
10 The two recommended methods, which can co-exist, are root filesystem
13 Root filesystem overlays (+BR2_ROOTFS_OVERLAY+)::
15 A filesystem overlay is a tree of files that is copied directly
16 over the target filesystem after it has been built. To enable this
44 target filesystem. You should, however, use this feature with care.
53 working directory. The path to the target filesystem is passed as the
73 Below three more methods of customizing the target filesystem are
76 Direct modification of the target filesystem::
[all …]
|
| /OK3568_Linux_fs/u-boot/drivers/bootcount/ |
| H A D | Kconfig | 17 bool "Boot counter on EXT filesystem"
20 filesystem.
25 string "Interface on which to find boot counter EXT filesystem"
29 Set the interface to use when locating the filesystem to use for the
33 string "Partition of the boot counter EXT filesystem"
37 Set the partition to use when locating the filesystem to use for the
41 string "Path and filename of the EXT filesystem based boot counter"
|
| /OK3568_Linux_fs/u-boot/fs/fat/ |
| H A D | Kconfig | 2 bool "Enable FAT filesystem support"
5 (FAT) filesystem. FAT filesystem is a legacy, lightweight filesystem.
10 bool "Enable FAT filesystem write support"
14 existing FAT filesystem partition.
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-networking/recipes-connectivity/rdist/rdist-6.1.5/ |
| H A D | rdist-6.1.5-stat64.patch | 25 -static long min_freespace = 0; /* Minimium free space on a filesystem */
26 -static long min_freefiles = 0; /* Minimium free # files on a filesystem */
27 +static fsblkcnt_t min_freespace = 0; /* Minimium free space on a filesystem */
28 +static fsfilcnt_t min_freefiles = 0; /* Minimium free # files on a filesystem */
73 - "%s: Not enough free space on filesystem: min %d free %d",
74 + "%s: Not enough free space on filesystem: min %lld free %lld",
81 - "%s: Not enough free files on filesystem: min %d free %d",
82 + "%s: Not enough free files on filesystem: min %lld free %lld",
|
| /OK3568_Linux_fs/buildroot/fs/f2fs/ |
| H A D | Config.in | 2 bool "f2fs root filesystem"
5 Build a f2fs root filesystem. If you enable this option, you
11 string "filesystem label"
14 string "filesystem size"
17 The size of the filesystem image in bytes.
54 string "filesystem features"
56 List of features that the F2FS filesystem should support
|
| /OK3568_Linux_fs/buildroot/fs/ubifs/ |
| H A D | Config.in | 2 bool "ubifs root filesystem"
4 Build a ubifs root filesystem
64 Do not compress the ubifs filesystem.
69 Do compress the ubifs filesystem with gzip.
74 Do compress the ubifs filesystem with bzip2.
79 Do compress the ubifs filesystem with lzma.
84 Do compress the ubifs filesystem with lzop.
89 Do compress the ubifs filesystem with xz.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/include/c++/10.3.1/experimental/bits/ |
| H A D | fs_dir.h | 47 namespace filesystem in _GLIBCXX_VISIBILITY()
94 explicit directory_entry(const filesystem::path& __p) : _M_path(__p) { } in _GLIBCXX_VISIBILITY()
101 void assign(const filesystem::path& __p) { _M_path = __p; } in _GLIBCXX_VISIBILITY()
104 replace_filename(const filesystem::path& __p) in _GLIBCXX_VISIBILITY()
108 const filesystem::path& path() const noexcept { return _M_path; } in _GLIBCXX_VISIBILITY()
109 operator const filesystem::path&() const noexcept { return _M_path; } in _GLIBCXX_VISIBILITY()
113 { return filesystem::status(_M_path); } in _GLIBCXX_VISIBILITY()
117 { return filesystem::status(_M_path, __ec); } in _GLIBCXX_VISIBILITY()
121 { return filesystem::symlink_status(_M_path); } in _GLIBCXX_VISIBILITY()
125 { return filesystem::symlink_status(_M_path, __ec); } in _GLIBCXX_VISIBILITY()
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/include/c++/10.3.1/experimental/bits/ |
| H A D | fs_dir.h | 47 namespace filesystem in _GLIBCXX_VISIBILITY()
94 explicit directory_entry(const filesystem::path& __p) : _M_path(__p) { } in _GLIBCXX_VISIBILITY()
101 void assign(const filesystem::path& __p) { _M_path = __p; } in _GLIBCXX_VISIBILITY()
104 replace_filename(const filesystem::path& __p) in _GLIBCXX_VISIBILITY()
108 const filesystem::path& path() const noexcept { return _M_path; } in _GLIBCXX_VISIBILITY()
109 operator const filesystem::path&() const noexcept { return _M_path; } in _GLIBCXX_VISIBILITY()
113 { return filesystem::status(_M_path); } in _GLIBCXX_VISIBILITY()
117 { return filesystem::status(_M_path, __ec); } in _GLIBCXX_VISIBILITY()
121 { return filesystem::symlink_status(_M_path); } in _GLIBCXX_VISIBILITY()
125 { return filesystem::symlink_status(_M_path, __ec); } in _GLIBCXX_VISIBILITY()
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/ext4/ |
| H A D | mmp.rst | 7 filesystem against multiple hosts trying to use the filesystem
8 simultaneously. When a filesystem is opened (for mounting, or fsck,
15 filesystem is active on another machine and the open fails. If the MMP
19 While the filesystem is live, the kernel sets up a timer to re-check the
23 filesystem, and node A remounts the filesystem read-only. If the
57 - Hostname of the node that opened the filesystem.
61 - Block device name of the filesystem.
|
| /OK3568_Linux_fs/buildroot/package/docker-engine/ |
| H A D | Config.in | 25 bool "btrfs filesystem driver"
30 Build the btrfs filesystem driver for Docker.
33 bool "devicemapper filesystem driver"
39 Build the devicemapper filesystem driver for Docker.
42 bool "vfs filesystem driver"
49 Build the vfs filesystem driver for Docker.
|