| /openbmc/estoraged/include/ |
| H A D | filesystemInterface.hpp | 5 #include <filesystem>
12 * @brief Interface to the filesystem operations that eStoraged needs.
13 * @details This class is used to mock out the filesystem operations.
27 /** @brief Runs the mkfs command to create the filesystem.
39 * @param[in] source - device where the filesystem is located.
40 * @param[in] target - path to where the filesystem should be mounted.
43 * @param[in] data - options for specific filesystem type, can be NULL
56 * @param[in] target - path location where the filesystem is mounted.
63 /** @brief Wrapper around std::filesystem::create_directory.
70 virtual bool createDirectory(const std::filesystem::path& p) = 0;
[all …]
|
| /openbmc/linux/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
15 Filesystem daemon:
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
24 Filesystem connection:
25 A connection between the filesystem daemon and the kernel. The
26 connection exists until either the daemon dies, or the filesystem is
[all …]
|
| H A D | idmappings.rst | 6 Most filesystem developers will have encountered idmappings. They are used when
8 for permission checking. This document is aimed at filesystem developers that
157 outside of the filesystem context. This is best left to an explanation of user
173 ownership of a file is read from disk by a filesystem, the userspace id is
177 For instance, consider a file that is stored on disk by a filesystem as being
180 - If a filesystem were to be mounted in the initial user namespaces (as most
186 - If a filesystem were to be mounted with an idmapping of ``u0:k10000:r10000``
233 into a kernel id according to the idmapping associated with the filesystem.
234 Let's assume the filesystem was mounted with an idmapping of
241 according to the filesystem's idmapping as this would give the wrong owner if
[all …]
|
| H A D | overlayfs.rst | 6 Overlay Filesystem
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
[all …]
|
| H A D | ext2.rst | 5 The Second Extended Filesystem
10 Extended Filesystem. It is currently still (April 2001) the predominant
11 filesystem in use by Linux. There are also implementations available
17 Most defaults are determined by the filesystem superblock, and can be
33 errors=continue Keep going on a filesystem error.
34 errors=remount-ro Remount the filesystem read-only on an error.
88 which is decided when the filesystem is created. Smaller blocks mean
90 and also impose other limits on the size of files and the filesystem.
115 to mounting the filesystem. Since it is so important, backup copies of
116 the superblock are stored in block groups throughout the filesystem.
[all …]
|
| H A D | mount_api.rst | 4 Filesystem Mount API
11 (2) The filesystem context.
13 (3) The filesystem context operations.
15 (4) Filesystem context security.
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
61 The Filesystem context
64 The creation and reconfiguration of a superblock is governed by a filesystem
[all …]
|
| H A D | autofs.rst | 23 filesystem can even be programmatic rather than database-backed,
30 The "autofs" filesystem module is only one part of an autofs system.
39 filesystem type. Several "autofs" filesystems can be mounted and they
45 An autofs filesystem can contain 3 sorts of objects: directories,
62 directory is a mount trap only if the filesystem is mounted *direct*
66 filesystem is mounted *indirect* and they are empty.
85 filesystem can be designated as a trap. This involves two separate
94 to be called. The task of this method is to find the filesystem that
96 responsible for actually mounting the root of this filesystem on the
99 autofs doesn't find the filesystem itself but sends a message to the
[all …]
|
| H A D | qnx6.rst | 4 The QNX6 Filesystem
13 mmi_fs Mount filesystem as used for example by Audi MMI 3G system
32 size of 512, 1024, 2048 or 4096, which is decided when the filesystem is
41 The superblock contains all global information about the filesystem.
50 (or period) and building up a new (stable) filesystem structure under the
53 Each superblock holds a set of root inodes for the different filesystem
75 information (total number of filesystem blocks) or by taking the highest
80 blocksize of the filesystem.
85 Each object in the filesystem is represented by an inode. (index node)
86 The inode structure contains pointers to the filesystem blocks which contain
[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
|
| /openbmc/docs/architecture/code-update/ |
| H A D | flash-layout.md | 1 # OpenBMC Flash Layout and Filesystem Documentation
5 how the Linux filesystem is setup, filesystem layouts, overlays, boot options,
30 Before starting execution, systemd requires the root filesystem and all binaries
34 ### Root filesystem
36 For storage of the root filesystem, a read-only volume was selected. This allows
37 the majority of the filesystem content, including all executables and static
38 data files, to be stored in a read-only filesystem image. Replacing read-only
39 filesystem images allows the space used by the content to be confirmed at build
43 An effort has been made to adhere to the Filesystem Hierarchy Standard [FHS][].
50 read-only filesystem content. This applies to systems with limited attached
[all …]
|
| /openbmc/estoraged/src/test/ |
| H A D | util_test.cpp | 7 #include <filesystem>
30 EXPECT_TRUE(std::filesystem::remove(testFileName)); in TEST()
44 EXPECT_TRUE(std::filesystem::remove(testFileName)); in TEST()
57 EXPECT_TRUE(std::filesystem::remove(testFileName)); in TEST()
78 EXPECT_TRUE(std::filesystem::remove(testFileName)); in TEST()
99 EXPECT_TRUE(std::filesystem::remove(testFileName)); in TEST()
115 std::filesystem::create_directories("abc/device"); in TEST()
123 std::filesystem::create_directories("def/device"); in TEST()
126 std::filesystem::create_directories("mmcblk0/device"); in TEST()
133 std::filesystem::path deviceFile, sysfsDir; in TEST()
[all …]
|
| /openbmc/linux/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"
39 This is the next generation of the ext3 filesystem.
41 Unlike the change from ext2 filesystem to ext3 filesystem,
44 physical block numbers. The ext4 filesystem also supports delayed
50 The ext4 filesystem supports mounting an ext3 filesystem; while there
53 features in the filesystem using tune2fs, or formatting a new
[all …]
|
| /openbmc/telemetry/src/ |
| H A D | persistent_json_storage.cpp | 11 bool isAnySymlink(const std::filesystem::path& path) in isAnySymlink()
16 if (std::filesystem::is_symlink(currentPath)) in isAnySymlink()
44 std::filesystem::create_directories(path.parent_path(), ec); in store()
82 auto removed = std::filesystem::remove(path, ec); in remove()
93 std::filesystem::remove(path.parent_path(), ec); in remove()
102 if (!std::filesystem::exists(path)) in load()
128 if (!std::filesystem::exists(directory)) in list()
134 std::filesystem::recursive_directory_iterator(directory)) in list()
138 auto item = std::filesystem::relative(p.path(), directory); in list()
146 std::filesystem::path
[all …]
|
| /openbmc/telemetry/tests/src/ |
| H A D | test_persistent_json_storage.cpp | 19 ASSERT_FALSE(std::filesystem::exists(directory)); in SetUpTestSuite()
24 if (std::filesystem::exists(directory)) in TearDown()
26 std::filesystem::remove_all(directory); in TearDown()
39 std::filesystem::temp_directory_path() / "telemetry-tests");
120 setupSymlinks(const std::filesystem::path& originalFile, in setupSymlinks()
123 auto linkPath = std::filesystem::path(directory) / in setupSymlinks()
125 std::filesystem::create_directories(std::filesystem::path(directory) / in setupSymlinks()
127 std::filesystem::create_symlink(originalFile, linkPath); in setupSymlinks()
135 setupSymlinks(const std::filesystem::path& originalFile, in setupSymlinks()
138 auto linkPath = std::filesystem::path(directory) / "reportLink"; in setupSymlinks()
[all …]
|
| /openbmc/linux/fs/xfs/ |
| H A D | Kconfig | 3 tristate "XFS filesystem support"
9 XFS is a high performance journaling filesystem which originated
30 The V4 filesystem format lacks certain features that are supported
37 Administrators and users can detect a V4 filesystem by running
38 xfs_info against a filesystem mountpoint and checking for a string
40 filesystem is a V4 filesystem. If no such string is found, please
55 The ASCII case insensitivity filesystem feature only works correctly
64 Administrators and users can detect such a filesystem by running
65 xfs_info against a filesystem mountpoin
[all...] |
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | read-only-rootfs.rst | 3 Creating a Read-Only Root Filesystem
7 root filesystem's write permissions (i.e. you need a read-only root
8 filesystem). Or, perhaps you are running the device's operating system
14 Supporting a read-only root filesystem requires that the system and
15 applications do not try to write to the root filesystem. You must
18 filesystem.
20 Creating the Root Filesystem
23 To create the read-only root filesystem, simply add the
42 Post-Installation Scripts and Read-Only Root Filesystem
47 image can be run at the time when the root filesystem is created during
[all …]
|
| /openbmc/openpower-pnor-code-mgmt/ |
| H A D | image_verify.cpp | 34 Signature::Signature(const std::filesystem::path& imageDirPath, in Signature()
36 const std::filesystem::path& signedConfPath) : in Signature()
40 std::filesystem::path file(imageDirPath / MANIFEST_FILE); in Signature()
53 if (!std::filesystem::is_directory(signedConfPath)) in getAvailableKeyTypesFromSystem()
68 std::filesystem::recursive_directory_iterator(signedConfPath)) in getAvailableKeyTypesFromSystem()
85 std::filesystem::path hashpath(signedConfPath / key / HASH_FILE_NAME); in getKeyHashFileNames()
86 std::filesystem::path keyPath(signedConfPath / key / PUBLICKEY_FILE_NAME); in getKeyHashFileNames()
104 std::filesystem::path publicKeyFile(imageDirPath / PUBLICKEY_FILE_NAME); in verify()
108 std::filesystem::path file(imageDirPath); in verify()
113 std::filesystem::path sigFile(imageDirPath); in verify()
[all …]
|
| H A D | functions.hpp | 1 #include <filesystem>
28 std::function<void(const std::filesystem::path&, std::error_code&)>;
30 std::function<void(const std::filesystem::path&,
31 const std::filesystem::path&, const ErrorCallbackType&)>;
37 void writeLink(const std::filesystem::path&, const std::filesystem::path&,
39 void findLinks(const std::filesystem::path&, const std::vector<std::string>&,
48 std::filesystem::path, ErrorCallbackType, sdeventplus::Event&);
51 std::filesystem::path, sdeventplus::Event&);
|
| /openbmc/linux/Documentation/filesystems/nfs/ |
| H A D | exporting.rst | 9 All filesystem operations require a dentry (or two) as a starting
12 applications that access a filesystem via a remote filesystem protocol
19 The mechanism discussed here allows each filesystem implementation to
20 specify how to generate an opaque (outside of the filesystem) byte
26 A filesystem which supports the mapping between filehandle fragments
34 The dcache normally contains a proper prefix of any given filesystem
35 tree. This means that if any filesystem object is in the dcache, then
36 all of the ancestors of that filesystem object are also in the dcache.
44 the dcache that are not needed for normal filesystem access.
98 Filesystem Issues
[all …]
|
| /openbmc/phosphor-logging/test/openpower-pels/ |
| H A D | pel_utils.hpp | 3 #include <filesystem>
22 std::filesystem::remove_all( in TearDownTestCase()
23 std::filesystem::path{pelIDFile}.parent_path()); in TearDownTestCase()
26 static std::filesystem::path pelIDFile;
41 std::filesystem::remove_all( in TearDown()
42 std::filesystem::path{pelIDFile}.parent_path()); in TearDown()
43 std::filesystem::remove_all(repoPath); in TearDown()
44 std::filesystem::remove_all(registryPath); in TearDown()
47 static std::filesystem::path pelIDFile;
48 static std::filesystem::path repoPath;
[all …]
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | ext4.rst | 7 Ext4 is an advanced level of the ext3 filesystem which incorporates
35 - Create a new filesystem using the ext4 filesystem type:
39 Or to configure an existing ext3 filesystem to support extents:
43 If the filesystem was created with 128 byte inodes, it can be
66 the filesystem with a large journal can also be helpful for
106 case-sensitive directories in the same filesystem. It is enabled by
110 case-insensitive directories, the filesystem must have the
111 casefold feature, which stores the filesystem-wide encoding
132 filesystem, which select its preferred behavior by enabling/disabling
134 filesystem did not require strict mode, it falls back to considering the
[all …]
|
| H A D | xfs.rst | 4 The SGI XFS Filesystem
7 XFS is a high performance journaling filesystem which originated
22 When mounting an XFS filesystem, the following options are accepted.
48 by the filesystem.
55 device reclaim space freed by the filesystem. This is
75 across the entire filesystem rather than just on directories
90 to create inodes at any location in the filesystem,
108 If ``largeio`` is specified, a filesystem that was created with a
110 in ``st_blksize``. If the filesystem does not have a ``swidth``
141 An XFS filesystem has up to three parts: a data section, a log
[all …]
|
| /openbmc/openpower-pnor-code-mgmt/ubi/ |
| H A D | item_updater_ubi.cpp | 15 #include <filesystem>
67 for (const auto& iter : std::filesystem::directory_iterator(MEDIA_DIR)) in processPNORImage()
82 if (!std::filesystem::is_regular_file(pnorTOC)) in processPNORImage()
108 auto path = std::filesystem::path(SOFTWARE_OBJPATH) / id; in processPNORImage()
159 if (!std::filesystem::is_directory(roDir)) in processPNORImage()
179 auto file = std::filesystem::path(filePath) / squashFSImage; in validateSquashFSImage()
180 if (std::filesystem::is_regular_file(file)) in validateSquashFSImage()
218 if (std::filesystem::is_directory(patchDir)) in reset()
220 for (const auto& iter : std::filesystem::directory_iterator(patchDir)) in reset()
222 std::filesystem::remove_all(iter); in reset()
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/health/ |
| H A D | phosphor-health-monitor_%.bbappend | 5 SRC_URI += "file://clean-up-filesystem \
6 file://clean-up-filesystem.service \
9 STORAGE_CRIT_TGT = "clean-up-filesystem.service"
16 clean-up-filesystem.service \
22 …install -m 0644 ${UNPACKDIR}/clean-up-filesystem.service ${D}${systemd_system_unitdir}/clean-up-fi…
24 install -m 0755 ${UNPACKDIR}/clean-up-filesystem ${D}${libexecdir}/${PN}/
|
| /openbmc/openpower-pnor-code-mgmt/test/ |
| H A D | test_functions.cpp | 9 #include <filesystem>
261 std::filesystem::path workdir = mkdtemp(&tmpl[0]); in TEST()
264 std::filesystem::path linkPath = workdir / "link"; in TEST()
265 std::filesystem::path targetPath = workdir / "target"; in TEST()
269 std::filesystem::remove_all(workdir); in TEST()
276 std::filesystem::path workdir = mkdtemp(&tmpl[0]); in TEST()
284 std::filesystem::remove_all(workdir); in TEST()
291 std::filesystem::path workdir = mkdtemp(&tmpl[0]); in TEST()
293 std::filesystem::path callbackPath; in TEST()
299 std::filesystem::create_directory(targetPath); in TEST()
[all …]
|