| History log of /src/sbin/fsck_ffs/wapbl.c |
| Revision | | Date | Author | Comments |
| 1.6 |
| 25-Jul-2022 |
dholland | Fix misleading fsck_ffs messages about wapbl journal replay.
Apparently fsck doesn't have a way to replay it to its internal memory
only. (Someone(TM) should implement this...)
This means that if you use -n, it can't replay the journal. But the
sequence of prints is such that it looks like it did. This is quite
misleading. Add an additional specific warning.
|
| 1.5 |
| 06-Mar-2010 |
mlelstv | When clearing a log on failure, not only ask the kernel to ignore an
existing log but to remove it on next mount.
|
| 1.4 |
| 13-Sep-2009 |
bouyer | Do some basic checks of the WAPBL journal, to abort the boot before the
kernel refuse to mount a filesystem read-write (booting a system
multiuser with critical filesystems read-only is bad):
Add a check_wapbl() which will check some WAPBL values in the superblock,
and try to read the journal via wapbl_replay_start() if there is one.
pfatal() if one of these fail (abort boot if in preen mode,
as "CONTINUE" otherwise). In non-preen mode the bogus journal will
be cleared.
check_wapbl() is always called if the superblock supports WAPBL.
Even if FS_DOWAPBL is not there, there could be flags asking the
kernel to clear or create a log with bogus values which would cause the
kernel refuse to mount the filesystem.
Discussed in
http://mail-index.netbsd.org/tech-kern/2009/08/17/msg005896.html
and followups.
|
| 1.3 |
| 10-Nov-2008 |
joerg | Reduce internals of WAPBL exposed to the rest of the system.
|
| 1.2 |
| 31-Jul-2008 |
simonb | branches: 1.2.2; 1.2.4; 1.2.6; 1.2.10;
Merge the simonb-wapbl branch. From the original branch commit:
Add Wasabi System's WAPBL (Write Ahead Physical Block Logging)
journaling code. Originally written by Darrin B. Jewell while
at Wasabi and updated to -current by Antti Kantee, Andy Doran,
Greg Oster and Simon Burge.
OK'd by core@, releng@.
|
| 1.1 |
| 10-Jun-2008 |
simonb | branches: 1.1.2;
file wapbl.c was initially added on branch simonb-wapbl.
|
| 1.1.2.5 |
| 28-Jul-2008 |
simonb | Add support for creating a WAPBL log in the filesystem. Will
create an in-filesystem log on first "mount -o log" if one doesn't
exist, and will then continue to use same log in the future. See
(soon to be added) wapbl(4) for more info.
Adds a new B_CONTIG low-level allocation flag that uses hints in
"struct ffs_inode_ext" to lay out an ffs file's data contiguously.
Thanks to Greg Oster for helping with the design of this and to
Antti Kantee for code review and suggestions.
|
| 1.1.2.4 |
| 12-Jun-2008 |
martin | License police
|
| 1.1.2.3 |
| 11-Jun-2008 |
simonb | Fix some whitespace and long line niggles.
|
| 1.1.2.2 |
| 11-Jun-2008 |
simonb | Fix a couple of typos. From wizd.
|
| 1.1.2.1 |
| 10-Jun-2008 |
simonb | Initial commit of Wasabi System's WAPBL (Write Ahead Physical Block
Logging) journaling code. Originally written by Darrin B. Jewell
while at Wasabi and updated to -current by Antti Kantee, Andy Doran,
Greg Oster and Simon Burge.
Still a number of issues - look in doc/BRANCHES for "simonb-wapbl"
for more info.
|
| 1.2.10.1 |
| 21-Apr-2010 |
matt | sync to netbsd-5
|
| 1.2.6.1 |
| 03-Oct-2009 |
snj | Pull up following revision(s) (requested by bouyer in ticket #1036):
sbin/fsck_ffs/extern.h: revision 1.25 via patch
sbin/fsck_ffs/setup.c: revision 1.88 via patch
sbin/fsck_ffs/wapbl.c: revision 1.4 via patch
sbin/tunefs/tunefs.c: revision 1.41 via patch
sys/ufs/ffs/ffs_vfsops.c: revision 1.252 via patch
sys/ufs/ffs/ffs_wapbl.c: revision 1.13 via patch
Allow tunefs to clear any type of WAPBL log, not only in-filesystem
ones. Discussed in
http://mail-index.netbsd.org/tech-kern/2009/08/17/msg005896.html
and followups.
--
Do some basic checks of the WAPBL journal, to abort the boot before the
kernel refuse to mount a filesystem read-write (booting a system
multiuser with critical filesystems read-only is bad):
Add a check_wapbl() which will check some WAPBL values in the superblock,
and try to read the journal via wapbl_replay_start() if there is one.
pfatal() if one of these fail (abort boot if in preen mode,
as "CONTINUE" otherwise). In non-preen mode the bogus journal will
be cleared.
check_wapbl() is always called if the superblock supports WAPBL.
Even if FS_DOWAPBL is not there, there could be flags asking the
kernel to clear or create a log with bogus values which would cause the
kernel refuse to mount the filesystem.
Discussed in
http://mail-index.netbsd.org/tech-kern/2009/08/17/msg005896.html
and followups.
--
If the WAPBL journal can't be read (ffs_wapbl_replay_start() fails),
mount the filesystem anyway if MNT_FORCE is present.
This allows to still boot single-user a system with a corrupted
WAPBL on /, and so get a chance to run fsck to fix it.
http://mail-index.netbsd.org/tech-kern/2009/08/17/msg005896.html
and followups.
|
| 1.2.4.3 |
| 17-Jan-2009 |
mjf | Sync with HEAD.
|
| 1.2.4.2 |
| 28-Sep-2008 |
mjf | Sync with HEAD.
|
| 1.2.4.1 |
| 31-Jul-2008 |
mjf | file wapbl.c was added on branch mjf-devfs2 on 2008-09-28 11:17:11 +0000
|
| 1.2.2.2 |
| 18-Sep-2008 |
wrstuden | Sync with wrstuden-revivesa-base-2.
|
| 1.2.2.1 |
| 31-Jul-2008 |
wrstuden | file wapbl.c was added on branch wrstuden-revivesa on 2008-09-18 04:28:23 +0000
|
