JM プロジェクトは、主に Linux 関連のマニュアルページの日本語ページを翻訳・公開しています。
... dos, vfat, XFS, xiafs 説明 When, as is customary, the proc filesystem is mounted on /proc , you can find in the file /proc/filesystems which filesystems your kernel currently supports; see proc (5) for more details. There is also a legacy sysfs (2) system c ... (2) と mount (8) を参照のこと。 The following list provides a short description of the available or historically available filesystems in the Linux kernel. See the kernel documentation for a comprehensive description of all options and limitations. ext mini ... たものである。DOS との互換性がある。 tmpfs is a filesystem whose contents reside in virtual memory. Since the files on such filesystems typically reside in RAM, file access is extremely fast. See tmpfs (5). vfat は Microsoft Windows95 と Windows NT が使う FA ... ... dos, vfat, XFS, xiafs 説明 When, as is customary, the proc filesystem is mounted on /proc , you can find in the file /proc/filesystems which filesystems your kernel currently supports; see proc (5) for more details. There is also a legacy sysfs (2) system c ... (2) と mount (8) を参照のこと。 The following list provides a short description of the available or historically available filesystems in the Linux kernel. See the kernel documentation for a comprehensive description of all options and limitations. ext mini ... たものである。DOS との互換性がある。 tmpfs is a filesystem whose contents reside in virtual memory. Since the files on such filesystems typically reside in RAM, file access is extremely fast. See tmpfs (5). vfat は Microsoft Windows95 と Windows NT が使う FA ... ... from write-back will be reported to all file descriptors that might have written the data which triggered the error. Some filesystems (e.g., NFS) keep close track of which data came through which file descriptor, and give more precise reporting. Other file ... systems (e.g., most local filesystems) will report errors to all file descriptors that were open on the file when the error was recorded. ENOSPC Disk space was ... ... from write-back will be reported to all file descriptors that might have written the data which triggered the error. Some filesystems (e.g., NFS) keep close track of which data came through which file descriptor, and give more precise reporting. Other file ... systems (e.g., most local filesystems) will report errors to all file descriptors that were open on the file when the error was recorded. ENOSPC Disk space was ... ... oyed together with RENAME_EXCHANGE . RENAME_NOREPLACE requires support from the underlying filesystem. Support for various filesystems was added as follows: * ext4 (Linux 3.15); * btrfs, shmem, cifs (Linux 3.17); * xfs (Linux 4.0); * Support for many other ... ing whiteout entries; specifically, BSD union mount employs a separate inode type, DT_WHT , which, while supported by some filesystems available in Linux, such as CODA and XFS, is ignored by the kernel's whiteout support code, as of Linux 4.19, at least.) R ... n't be employed together with RENAME_EXCHANGE . RENAME_WHITEOUT requires support from the underlying filesystem. Among the filesystems that provide that support are tmpfs (since Linux 3.18), ext4 (since Linux 3.18), XFS (since Linux 4.1), f2fs (since Linux ... ... oyed together with RENAME_EXCHANGE . RENAME_NOREPLACE requires support from the underlying filesystem. Support for various filesystems was added as follows: * ext4 (Linux 3.15); * btrfs, shmem, cifs (Linux 3.17); * xfs (Linux 4.0); * Support for many other ... ing whiteout entries; specifically, BSD union mount employs a separate inode type, DT_WHT , which, while supported by some filesystems available in Linux, such as CODA and XFS, is ignored by the kernel's whiteout support code, as of Linux 4.19, at least.) R ... n't be employed together with RENAME_EXCHANGE . RENAME_WHITEOUT requires support from the underlying filesystem. Among the filesystems that provide that support are tmpfs (since Linux 3.18), ext4 (since Linux 3.18), XFS (since Linux 4.1), f2fs (since Linux ... ... oyed together with RENAME_EXCHANGE . RENAME_NOREPLACE requires support from the underlying filesystem. Support for various filesystems was added as follows: * ext4 (Linux 3.15); * btrfs, shmem, cifs (Linux 3.17); * xfs (Linux 4.0); * Support for many other ... ing whiteout entries; specifically, BSD union mount employs a separate inode type, DT_WHT , which, while supported by some filesystems available in Linux, such as CODA and XFS, is ignored by the kernel's whiteout support code, as of Linux 4.19, at least.) R ... n't be employed together with RENAME_EXCHANGE . RENAME_WHITEOUT requires support from the underlying filesystem. Among the filesystems that provide that support are tmpfs (since Linux 3.18), ext4 (since Linux 3.18), XFS (since Linux 4.1), f2fs (since Linux ... ... 。 さもなければ、 mount は自身でスーパーブロックをプローブして推測を行う。 このプローブに失敗すると、 mount はファイル /etc/filesystems を読み込もうとする。 さらにこのファイルがなければ /proc/filesystems を読み込もうとする。 そして、読み込んだファイルにリスト ... ルシステムがテストされる。 ただし "nodev" ラベルの付いているもの (すなわち devpts , proc , nfs ) はテストから除かれる。 /etc/filesystems が * のみの行で終わっている場合、 mount はその後に /proc/filesystems を読み込む。 auto タイプはフロッピーを一般ユーザーがマ ... t の試行をしたい場合や ext2 の前に ext3 を試行したい場合) や、 カーネルモジュールの自動ローダを利用している場合には、 /etc/filesystems ファイルを作っておくと便利である。 注意: ファイルシステムのテストには発見的手法 (適当な `合い言葉' が見つかるかどうか) が用 ... ... the file offset and the write operation are performed as a single atomic step. O_APPEND may lead to corrupted files on NFS filesystems if more than one process appends data to a file at once. This is because NFS does not support appending to a file, so the ... s set on the parent directory: if that bit is set, then BSD semantics apply; otherwise, System V semantics apply. For some filesystems, the behavior also depends on the bsdgroups and sysvgroups mount options described in mount (8). The mode argument specifi ... ァイルシステム内にアトミックにリンクを行う。 O_TMPFILE requires support by the underlying filesystem; only a subset of Linux filesystems provide that support. In the initial implementation, support was provided in the ext2, ext3, ext4, UDF, Minix, and shmem f ... ... から削除する。 mask は空であってはいけない。 空の場合はエラー EINVAL が発生する。 FAN_MARK_FLUSH Remove either all marks for filesystems, all marks for mounts, or all marks for directories and files from the fanotify group. If flags contains FAN_MARK_MOUNT , ... all marks for mounts are removed from the group. If flags contains FAN_MARK_FILESYSTEM , all marks for filesystems are removed from the group. Otherwise, all marks for directories and files are removed. No flag other than and at most one ... MOUNT . Attempting to do so will result in the error EINVAL being returned. FAN_MARK_FILESYSTEM (Linux 4.20 以降) Mark the filesystem specified by pathname . The filesystem containing pathname will be marked. All the contained files and directories of the f ... 日本語の文書やマニュアルを配布している個人/プロジェクトへのリンクです。