| #
76e911db
|
| 20-Jul-2025 |
Rick Macklem <rmacklem@FreeBSD.org> |
statfs.2: Fix named_attribute man section
This is a content change.
Fixes: 964d0fd62431 ("statfs.2: Update man page for the MNT_NAMEDATTR flag")
|
| #
964d0fd6
|
| 11-Apr-2025 |
Rick Macklem <rmacklem@FreeBSD.org> |
statfs.2: Update man page for the MNT_NAMEDATTR flag
This patch updates the man page for the MNT_NAMEDATTR flag.
Another man page that explains named attributes will be introduced in a future commi
statfs.2: Update man page for the MNT_NAMEDATTR flag
This patch updates the man page for the MNT_NAMEDATTR flag.
Another man page that explains named attributes will be introduced in a future commit.
This is a content change.
Reviewed by: manpages (zaiee) Fixes: 2ec2ba7e232d ("vfs: Add VFS/syscall support for Solaris style extended attributes") Differential Revision: https://reviews.freebsd.org/D49719
show more ...
|
| #
e951247a
|
| 20-Feb-2025 |
Konstantin Belousov <kib@FreeBSD.org> |
statfs.2: document missing user-visible MNT flags
Sponsored by: The FreeBSD Foundation MFC after: 3 days
|
| #
0738cd97
|
| 20-Feb-2025 |
Konstantin Belousov <kib@FreeBSD.org> |
statfs.2: order MNT flags alphabetically
Sponsored by: The FreeBSD Foundation MFC after: 3 days
|
| #
13b92ae9
|
| 20-Feb-2025 |
Konstantin Belousov <kib@FreeBSD.org> |
statfs.2: remove dead comment
Sponsored by: The FreeBSD Foundation MFC after: 3 days
|
| #
270542d9
|
| 20-Feb-2025 |
Konstantin Belousov <kib@FreeBSD.org> |
statfs.2: uncomment and describe MNT_IGNORE
Sponsored by: The FreeBSD Foundation MFC after: 3 days
|
| #
2878d99d
|
| 12-Sep-2024 |
Graham Percival <gperciva@tarsnap.com> |
manuals: Misc macro typos
These were reported by `mandoc -T lint` as ERROR: skipping unknown macro When these pages were rendered with `man`, the "unknown macro" meant that the entire line was o
manuals: Misc macro typos
These were reported by `mandoc -T lint` as ERROR: skipping unknown macro When these pages were rendered with `man`, the "unknown macro" meant that the entire line was omitted from the output.
Obvious typos in: lib/libsys/swapon.2 lib/libsys/procctl.2 share/man/man9/firmware.9
lib/libcasper/services/cap_net/cap_net.3: 'mode' describes a function argument.
lib/libsys/statfs.2: there's no .Tm command ("trademark?"), and .Tn ("tradename") is deprecated, so remove the macro entirely.
usr.sbin/mfiutil/mfiutil.8: man was interpreting '/dev/' as a macro (which it didn't recognize).
share/man/man4/qat.4: same issue as above, but with '0'. In this case, given the context of the previous line, rewriting as "Value '0'" seemed more appropriate.
usr.sbin/mlx5tool/mlx5tool.8: typo in .Xr
Signed-off-by: Graham Percival <gperciva@tarsnap.com> Sponsored by: Tarsnap Backup Inc. Reviewed by: concussious, imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1417
show more ...
|
| #
1a720cbe
|
| 15-May-2024 |
Alexander Ziaee <concussious@runbox.com> |
man filesystems: fix xrefs after move to section 4
Reviewed by: des, imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1077
|
| #
8269e767
|
| 14-Nov-2023 |
Brooks Davis <brooks@FreeBSD.org> |
libsys: relocate implementations and manpages
Remove core system call implementations and documentation to lib/libsys and lib/libsys/<arch> from lib/libc/sys and lib/libc/<arch>/<sys>. Update paths
libsys: relocate implementations and manpages
Remove core system call implementations and documentation to lib/libsys and lib/libsys/<arch> from lib/libc/sys and lib/libc/<arch>/<sys>. Update paths to allow libc to find them in their new home.
Reviewed by: kib, emaste, imp Pull Request: https://github.com/freebsd/freebsd-src/pull/908
show more ...
|
| #
dc36d6f9
|
| 23-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
lib: Remove ancient SCCS tags.
Remove ancient SCCS tags from the tree, automated scripting, with two minor fixup to keep things compiling. All the common forms in the tree were removed with a perl s
lib: Remove ancient SCCS tags.
Remove ancient SCCS tags from the tree, automated scripting, with two minor fixup to keep things compiling. All the common forms in the tree were removed with a perl script.
Sponsored by: Netflix
show more ...
|
| #
b2c76c41
|
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line nroff pattern
Remove /^\.\\"\s*\$FreeBSD\$$\n/
|
| #
9d33a9d9
|
| 29-Mar-2023 |
Stefan Eßer <se@FreeBSD.org> |
Fix typo in statfs man page
There are FAT12 and FAT16 file systems, but FAT13 of was an unintentional invention of mine ...
Reported by: Ravi Pokala <rpokala@freebsd.org> MFC after: 1 month
|
| #
c33db74b
|
| 29-Mar-2023 |
Stefan Eßer <se@FreeBSD.org> |
fs/msdosfs: add tracking of free root directory entries
This update implements tallying of free directory entries during create, delete, or rename operations on FAT12 and FAT16 file systems.
Prior
fs/msdosfs: add tracking of free root directory entries
This update implements tallying of free directory entries during create, delete, or rename operations on FAT12 and FAT16 file systems.
Prior to this change, the total number of root directory entries was reported as number of inodes, but 0 as the number of free inodes, causing system health monitoring software to warn about a suspected disk full issue.
The FAT12 and FAT16 file systems provide a limited number of root directory entries, e.g. 512 on typical hard disk formats. The valid range of values is 1 to 65535, but the msdosfs code will effectively round up "odd" values to the next multiple of 16 (e.g. 513 would allow for 528 root directory entries).
This update implements tracking of directory entries during create, delete, or rename operations, with initial values determined by scanning the directory when the file system is mounted.
Total and free directory entries are reported in the f_files and f_ffree elements of struct statfs, despite differences in semantics of these values:
- There is no limit on the number of files and directories that can be created on a FAT file system. Only the root directory of FAT12 and FAT16 file systems is limited, any number of files can still be created in sub-directories, even when 0 free "inodes" are reported.
- A single file can require 1 to 21 directory entries, depending on the character set, structure, and length of the name. The DOS 8.3 style file name takes up 1 entry, and if the name does not comply with the syntax of a DOS 8.3 file name, 1 additional entry is used for each 13 characters of the file name. Since all these entries have to be contiguous, it is possible that a file or directory with a long name can not be created, despite a sufficient total number of free directory entries.
- Renaming a file can require more directory entries than currently allocated to store its long name, which may prevent an in-place update of the name if more entries are needed. This may cause a rename operation to fail if no contiguous range of free entries for the new name can be found.
- The volume label is stored in a directory entry. An empty FAT file system with a volume label will therefore show 1 used "inode" in df.
- The perceentage of free inodes shown in df or monitoring tools does only represent the state of the root directory of a FAT12 or FAT16 file system. Neither does a reported value of 0% free inodes does prevent files from being created in sub-directories, nor does a value of 50% free inodes guarantee that even a single file with a "long" name can be created in the root directory (if every other directory entry is occupied and there are no 2 contiguous entries).
The statfs(2) and df(1) man pages have been updated with a notice regarding the possibly different semantics of values reported as total and free inodes for non-Unix file systems.
PR: 270053 Reported by: Ben Woods <woodsb02@freebsd.org> Approved by: mckusick MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D38987
show more ...
|
| #
e42b0964
|
| 30-Mar-2020 |
John Baldwin <jhb@FreeBSD.org> |
Document EINTEGRITY errors for many system calls.
EINTEGRITY was previously documented as a UFS-specific error for mount(2). This documents EINTEGRITY as a filesystem-independent error that may be
Document EINTEGRITY errors for many system calls.
EINTEGRITY was previously documented as a UFS-specific error for mount(2). This documents EINTEGRITY as a filesystem-independent error that may be reported by the backing store of a filesystem.
While here, document EIO as a filesystem-independent error for both mount(2) and posix_fadvise(2). EIO was previously only documented for UFS for mount(2).
Reviewed by: mckusick Suggested by: mckusick MFC after: 2 weeks Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D24168
show more ...
|
| #
dd821112
|
| 22-Nov-2017 |
Warner Losh <imp@FreeBSD.org> |
Add a reference to getfsstat in statfs.
Sponsored by: Netflix
|
| #
69921123
|
| 23-May-2017 |
Konstantin Belousov <kib@FreeBSD.org> |
Commit the 64-bit inode project.
Extend the ino_t, dev_t, nlink_t types to 64-bit ints. Modify struct dirent layout to add d_off, increase the size of d_fileno to 64-bits, increase the size of d_na
Commit the 64-bit inode project.
Extend the ino_t, dev_t, nlink_t types to 64-bit ints. Modify struct dirent layout to add d_off, increase the size of d_fileno to 64-bits, increase the size of d_namlen to 16-bits, and change the required alignment. Increase struct statfs f_mntfromname[] and f_mntonname[] array length MNAMELEN to 1024.
ABI breakage is mitigated by providing compatibility using versioned symbols, ingenious use of the existing padding in structures, and by employing other tricks. Unfortunately, not everything can be fixed, especially outside the base system. For instance, third-party APIs which pass struct stat around are broken in backward and forward incompatible ways.
Kinfo sysctl MIBs ABI is changed in backward-compatible way, but there is no general mechanism to handle other sysctl MIBS which return structures where the layout has changed. It was considered that the breakage is either in the management interfaces, where we usually allow ABI slip, or is not important.
Struct xvnode changed layout, no compat shims are provided.
For struct xtty, dev_t tty device member was reduced to uint32_t. It was decided that keeping ABI compat in this case is more useful than reporting 64-bit dev_t, for the sake of pstat.
Update note: strictly follow the instructions in UPDATING. Build and install the new kernel with COMPAT_FREEBSD11 option enabled, then reboot, and only then install new world.
Credits: The 64-bit inode project, also known as ino64, started life many years ago as a project by Gleb Kurtsou (gleb). Kirk McKusick (mckusick) then picked up and updated the patch, and acted as a flag-waver. Feedback, suggestions, and discussions were carried by Ed Maste (emaste), John Baldwin (jhb), Jilles Tjoelker (jilles), and Rick Macklem (rmacklem). Kris Moore (kris) performed an initial ports investigation followed by an exp-run by Antoine Brodin (antoine). Essential and all-embracing testing was done by Peter Holm (pho). The heavy lifting of coordinating all these efforts and bringing the project to completion were done by Konstantin Belousov (kib).
Sponsored by: The FreeBSD Foundation (emaste, kib) Differential revision: https://reviews.freebsd.org/D10439
show more ...
|
| #
fbbd9655
|
| 28-Feb-2017 |
Warner Losh <imp@FreeBSD.org> |
Renumber copyright clause 4
Renumber cluase 4 to 3, per what everybody else did when BSD granted them permission to remove clause 3. My insistance on keeping the same numbering for legal reasons is
Renumber copyright clause 4
Renumber cluase 4 to 3, per what everybody else did when BSD granted them permission to remove clause 3. My insistance on keeping the same numbering for legal reasons is too pedantic, so give up on that point.
Submitted by: Jan Schaumann <jschauma@stevens.edu> Pull Request: https://github.com/freebsd/freebsd/pull/96
show more ...
|
| #
c879ae35
|
| 09-Jan-2007 |
Warner Losh <imp@FreeBSD.org> |
Per Regents of the University of Calfornia letter, remove advertising clause.
# If I've done so improperly on a file, please let me know.
|
| #
a722f8df
|
| 01-Nov-2006 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Document MNT_GJOURNAL option.
|
| #
3b4c9742
|
| 10-Jan-2006 |
Greg Lehey <grog@FreeBSD.org> |
Add references to fhopen, fhstat, getfh, lgetfh and fhstatfs.
Pointed out by: Antony Curtis <antony@mysql.com>
|
| #
e354922c
|
| 29-Nov-2004 |
Ruslan Ermilov <ru@FreeBSD.org> |
MNT_NODEV is deprecated.
|
| #
ef6dea14
|
| 20-Jul-2004 |
Christian S.J. Peron <csjp@FreeBSD.org> |
Back out previous commit. Even though statfs(2) can take a regular file as an argument, it may still fail for the same reasons that open(2) can.
Pointed out by: Jilles Tjoelker Apporived by: bmileki
Back out previous commit. Even though statfs(2) can take a regular file as an argument, it may still fail for the same reasons that open(2) can.
Pointed out by: Jilles Tjoelker Apporived by: bmilekic (mentor)
show more ...
|
| #
5b154abc
|
| 20-Jul-2004 |
Christian S.J. Peron <csjp@FreeBSD.org> |
Remove reference to ENOTDIR in the documented errors for statfs(2). This is false, if the pathname specified is a regular file, then the information for the file system that the file lives on will be
Remove reference to ENOTDIR in the documented errors for statfs(2). This is false, if the pathname specified is a regular file, then the information for the file system that the file lives on will be returned.
Approved by: bmilekic (mentor)
show more ...
|
| #
33992dc0
|
| 30-Jun-2004 |
Ruslan Ermilov <ru@FreeBSD.org> |
Markup, grammar, and spelling fixes.
|
| #
607e2cc1
|
| 16-Nov-2003 |
Tim J. Robbins <tjr@FreeBSD.org> |
Resync. struct statfs and flag definitions with sys/mount.h.
|