Age | Commit message (Collapse) | Author |
|
|
|
Various testing for a while, okay krw@
|
|
|
|
No functional change
|
|
|
|
boolean, make it so. OK deraadt@
|
|
-1 mess as well), it is probably not wise to make other functions do the same
thing. make them return strlen(). ok uwe marco
|
|
|
|
|
|
- filesystem -> file system, for consistency
- indent sections where applicable
- mdoc, punctuation, grammar, etc. fixes
- document SIGINFO to fsck_ffs
- unify description of -n among documents
- sprinkle xrefs all around
- move parts relevant to fsck.8 from fsck_ffs.8
parts from NetBSD
ok jmc
|
|
- halting flushes the fs cache to disk, no need to run explicitly
- other minor tweaks (grammar, punctuation, etc.)
ok jmc
|
|
'looks fine' millert@, krw@. ok jmc@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
way for some future work. no function changes yet.
help testing otto@ and markus@
|
|
- use .Dl for one-liners, rather than .Bd
|
|
|
|
- some mdoc fixes
|
|
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
ignore the noninteresting ones. will allow future changes to work
with an older fsck. similar to changes in NetBSD and FreeBSD.
ok krw@
|
|
|
|
|
|
ok millert@
|
|
- eliminate trailing whitespace
- remove casts that aren't needed.
- make rcsid strings const, for -Wall compilation.
from tedu <grendel@zeitbombe.org>
|
|
|
|
|
|
|
|
Synch files that use that field.
(This argument is an internal interface specific to OpenBSD, so it won't
cause compatibility problems.)
(No bump, not an ABI change).
ok art, millert...
|
|
|
|
hand editing to make comments line up correctly. Another pass is forthcoming that handles the cases that could not be done automatically.
|
|
|
|
millert@ ok
|
|
|
|
- If the lost+found directory is created by fsck, it will do a cacheino()
which sets the inoinfo's i_parent and i_dotdot to 0, but they never get
set to ROOTINO. This means that propagate will never find lost+found and
its descendents, subdirectories will remain DSTATE (instead of DFOUND)
even though they are correctly linked in, and pass4.c will try to
clear them unsuccessfully, thinking that there is no link count from the
DSTATE directory's parent. The result is that you need to run fsck twice
and get "EXTRANEOUS HARD LINK TO DIRECTORY" error (which are unexpected
and fatal when running in preen mode). The fix is to set i_parent and
i_dotdot to "parent" after the second cacheino() call in dir.c:allocdir().
From NetBSD via FreeBSD.
- modify propagate() so it be able to start from any point in the tree.
- minor tweaks to get more generality in state propagation.
In other words fsck doesn't leave unremovable directories anymore.
costa@ ok.
|
|
|
|
|
|
|
|
From FreeBSD with little changes.
art@ ok.
|
|
FreeBSD's log:
> The ffs superblock includes a 128-byte region for use by temporary
> in-core pointers to summary information. An array in this region
> (fs_csp) could overflow on filesystems with a very large number of
> cylinder groups (~16000 on i386 with 8k blocks). When this happens,
> other fields in the superblock get corrupted, and fsck refuses to
> check the filesystem.
>
> Solve this problem by replacing the fs_csp array in 'struct fs'
> with a single pointer, and add padding to keep the length of the
> 128-byte region fixed. Update the kernel and userland utilities
> to use just this single pointer.
>
> With this change, the kernel no longer makes use of the superblock
> fields 'fs_csshift' and 'fs_csmask'. Add a comment to newfs/mkfs.c
> to indicate that these fields must be calculated for compatibility
> with older kernels.
art@ ok.
|
|
It allocates directory inode in the same cylinder group as a parent
directory in. This speedup file/directory intensive operations on
a big file systems in times.
Don't forget to recompile fsck_ffs with updated fs.h or you will get
"VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE" at
the next boot. In any case you can ignore this error safely.
Requested by deraadt@
|
|
|
|
|
|
to check if it builds.
|
|
We had this in the tree 1997, but it went away because it was too close to
release.
Ok: csapuntz@
(as a size note: It's really good to test fsck when you are torture testing
the filesystems)
|
|
|
|
|