Revision tags: release/6.4.0_cvs, release/6.4.0 |
|
#
6910e995 |
| 23-Aug-2008 |
Craig Rodrigues <rodrigc@FreeBSD.org> |
Instead of passing MNT_UPDATE, MNT_SNAPSHOT, MNT_RELOAD from userspace to kernel via nmount(), pass in the strings "update", "snapshot", "reload".
We want to move away from passing MNT_ flags from u
Instead of passing MNT_UPDATE, MNT_SNAPSHOT, MNT_RELOAD from userspace to kernel via nmount(), pass in the strings "update", "snapshot", "reload".
We want to move away from passing MNT_ flags from userspace -> kernel via nmount(), and instead favor passing the string options.
show more ...
|
#
4f387965 |
| 08-Jun-2008 |
Stanislav Sedov <stas@FreeBSD.org> |
- Display '-C' option in usage().
Approved by: kib
|
#
14320f1e |
| 11-Apr-2008 |
Xin LI <delphij@FreeBSD.org> |
Add a new flag, '-C' which enables a special mode that is intended for catastrophic recovery. Currently, this mode only validates whether a cylindergroup has good signature data, and prompts the use
Add a new flag, '-C' which enables a special mode that is intended for catastrophic recovery. Currently, this mode only validates whether a cylindergroup has good signature data, and prompts the user to decide whether to clear it as a whole.
This mode is useful when there is data damage on a disk and you are working on copy of the original disk, as fsck_ffs(8) tends to abnormally exit in such case, as a last resort to recover data from the disk.
show more ...
|
#
205e074f |
| 04-Apr-2008 |
Craig Rodrigues <rodrigc@FreeBSD.org> |
Add comment about specifying "ro" mount option when doing an update mount on a read-only file system.
Requested by: yar
|
#
d8f7b008 |
| 05-Mar-2008 |
Craig Rodrigues <rodrigc@FreeBSD.org> |
For a mounted file system which is read-only, when doing the MNT_RELOAD, pass in "ro" and "update" string mount options to nmount() instead of MNT_RDONLY and MNT_UPDATE flags.
Due to the complexity
For a mounted file system which is read-only, when doing the MNT_RELOAD, pass in "ro" and "update" string mount options to nmount() instead of MNT_RDONLY and MNT_UPDATE flags.
Due to the complexity of the mount parsing code especially with respect to the root file system, passing in MNT_RDONLY and MNT_UPDATE flags would do weird things and would cause fsck to convert the root file system from a read-only mount to read-write.
To test: - boot into single user mode - show mounted file systems with: mount - root file system should be mounted read-only - fsck / - show mounted file systems with: mount - root file system should still be mounted read-only
PR: 120319 MFC after: 1 month Reported by: yar
show more ...
|
#
22a122f3 |
| 05-Mar-2008 |
Craig Rodrigues <rodrigc@FreeBSD.org> |
Remove hacks to filter out MNT_ROOTFS, since we now do that internally inside nmount() in revision 1.267 of vfs_mount.c.
|
Revision tags: release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0 |
|
#
24adb851 |
| 19-Sep-2007 |
Craig Rodrigues <rodrigc@FreeBSD.org> |
Convert fsck_ffs to nmount(). This seems to solve an intermittent problem where MNT_RELOAD fails for the root file system.
Reported and tested by: phk Approved by: re (bmah)
|
#
db3f838d |
| 10-Aug-2007 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Fix fscking gjournaled root file system: root file system is already mounted read-only, so we can't simply exit right after calling gjournal_check(), instead we need to ask about super block reload.
Fix fscking gjournaled root file system: root file system is already mounted read-only, so we can't simply exit right after calling gjournal_check(), instead we need to ask about super block reload.
Submitted by: Niki Denev <niki@totalterror.net> PR: misc/113889 Approved by: re (kensmith)
show more ...
|
Revision tags: release/6.2.0_cvs, release/6.2.0 |
|
#
aef8d244 |
| 31-Oct-2006 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Implements gjournal support. If file system has gjournal support enabled and -p flag was given perform fast file system checking (bascially only garbage collecting of orphaned objects).
Rename bread
Implements gjournal support. If file system has gjournal support enabled and -p flag was given perform fast file system checking (bascially only garbage collecting of orphaned objects).
Rename bread() to blread() and bwrite() to blwrite() as we now link to the libufs library, which also implement functions with that names.
Sponsored by: home.pl
show more ...
|
Revision tags: release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0 |
|
#
8d646af5 |
| 10-Feb-2005 |
Ruslan Ermilov <ru@FreeBSD.org> |
Sync program's usage() with manpage's SYNOPSIS.
|
Revision tags: release/4.11.0_cvs, release/4.11.0 |
|
#
d90b3ef3 |
| 12-Dec-2004 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Do not pass random bits as mount arguments.
|
Revision tags: release/5.3.0_cvs, release/5.3.0 |
|
#
af6726e6 |
| 08-Oct-2004 |
Don Lewis <truckman@FreeBSD.org> |
Eliminate linked list used to track inodes with an initial link count of zero and instead encode this information in the inode state. Pass 4 performed a linear search of this list for each inode in t
Eliminate linked list used to track inodes with an initial link count of zero and instead encode this information in the inode state. Pass 4 performed a linear search of this list for each inode in the file system, which performs poorly if the list is long.
Reviewed by: sam & keramida (an earlier version of the patch), mckusick MFC after: 1 month
show more ...
|
Revision tags: release/4.10.0_cvs, release/4.10.0 |
|
#
4c723140 |
| 09-Apr-2004 |
Mark Murray <markm@FreeBSD.org> |
Remove advertising clause from University of California Regent's license, per letter dated July 22, 1999.
Approved by: core, imp
|
#
1660ae87 |
| 28-Feb-2004 |
Scott Long <scottl@FreeBSD.org> |
In the case of a background fsck, periodically update the process title with a progress update.
|
Revision tags: release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0 |
|
#
ff76fc7f |
| 08-Oct-2003 |
Kirk McKusick <mckusick@FreeBSD.org> |
Create a .snap directory mode 770 group operator in the root of each filesystem that is checked in background. Create the snapshot in this directory rather than in the root. There are two benefits:
Create a .snap directory mode 770 group operator in the root of each filesystem that is checked in background. Create the snapshot in this directory rather than in the root. There are two benefits:
1) For terabyte-sized filesystems, the snapshot may require many minutes to build. Although the filesystem will not be suspended during most of the snapshot build, the snapshot file itself is locked during the entire snapshot build period. Thus, if it is accessed during the period that it is being built, the process trying to access it will block holding its containing directory locked. If the snapshot is in the root, the root will lock and the system will come to a halt until the snapshot finishes. By putting the snapshot in a subdirectory, it is out of the likely path of any process traversing through the root and hence much less likely to cause a lock race to the root.
2) The dump program is usually run by a non-root user running with operator group privilege. Such a user is typically not permitted to create files in the root of a filesystem. By having a directory in group operator with group write access available, such a user will be able to create a snapshot there. Having the dump program create its snapshot in a subdirectory below the root will benefit from point (1) as well.
Sponsored by: DARPA & NAI Labs.
show more ...
|
#
e4e07764 |
| 01-Aug-2003 |
Ruslan Ermilov <ru@FreeBSD.org> |
Spell "file system" correctly.
|
Revision tags: release/5.1.0_cvs, release/5.1.0 |
|
#
c69284ca |
| 03-May-2003 |
David E. O'Brien <obrien@FreeBSD.org> |
Use __FBSDID() to quiet GCC 3.3 warnings.
|
Revision tags: release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs |
|
#
ce66ddb7 |
| 21-Aug-2002 |
Tom Rhodes <trhodes@FreeBSD.org> |
s/filesystem/file system/g as discussed on -developers
|
Revision tags: release/4.6.2_cvs, release/4.6.2 |
|
#
84fc0d7e |
| 31-Jul-2002 |
Maxime Henrion <mux@FreeBSD.org> |
Fix a bunch of format string warnings which broke the sparc64 build.
Tested on: sparc64, i386
|
#
599304a4 |
| 30-Jul-2002 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Warning cleanup.
Format changes by peter
|
Revision tags: release/4.6.1, release/4.6.0_cvs |
|
#
1c85e6a3 |
| 21-Jun-2002 |
Kirk McKusick <mckusick@FreeBSD.org> |
This commit adds basic support for the UFS2 filesystem. The UFS2 filesystem expands the inode to 256 bytes to make space for 64-bit block pointers. It also adds a file-creation time field, an ability
This commit adds basic support for the UFS2 filesystem. The UFS2 filesystem expands the inode to 256 bytes to make space for 64-bit block pointers. It also adds a file-creation time field, an ability to use jumbo blocks per inode to allow extent like pointer density, and space for extended attributes (up to twice the filesystem block size worth of attributes, e.g., on a 16K filesystem, there is space for 32K of attributes). UFS2 fully supports and runs existing UFS1 filesystems. New filesystems built using newfs can be built in either UFS1 or UFS2 format using the -O option. In this commit UFS1 is the default format, so if you want to build UFS2 format filesystems, you must specify -O 2. This default will be changed to UFS2 when UFS2 proves itself to be stable. In this commit the boot code for reading UFS2 filesystems is not compiled (see /sys/boot/common/ufsread.c) as there is insufficient space in the boot block. Once the size of the boot block is increased, this code can be defined.
Things to note: the definition of SBSIZE has changed to SBLOCKSIZE. The header file <ufs/ufs/dinode.h> must be included before <ufs/ffs/fs.h> so as to get the definitions of ufs2_daddr_t and ufs_lbn_t.
Still TODO: Verify that the first level bootstraps work for all the architectures. Convert the utility ffsinfo to understand UFS2 and test growfs. Add support for the extended attribute storage. Update soft updates to ensure integrity of extended attribute storage. Switch the current extended attribute interfaces to use the extended attribute storage. Add the extent like functionality (framework is there, but is currently never used).
Sponsored by: DARPA & NAI Labs. Reviewed by: Poul-Henning Kamp <phk@freebsd.org>
show more ...
|
#
3468b317 |
| 16-May-2002 |
Tom Rhodes <trhodes@FreeBSD.org> |
more file system > filesystem
|
#
d3974088 |
| 22-Apr-2002 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Usage style sweep: spell "usage" with a small 'u'. Also change one case of blatant __progname abuse (several more remain) This commit does not touch anything in src/{contrib,crypto,gnu}/.
|
#
8e2e167c |
| 24-Mar-2002 |
Mark Murray <markm@FreeBSD.org> |
Replace __progname with the documented, more acceptable and functionally identical getprogname(3).
|
#
b70cd7ee |
| 20-Mar-2002 |
Warner Losh <imp@FreeBSD.org> |
o __P removed o ansi function prototypes o unifdef -D__STDC__ o __dead2 on usage prototype o remove now-bogus main prototype
|