Annotated edit history of
JFS version 5, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 1 |
PerryLorier |
1 |
[Acronym] for __J__ournalling __F__ile __S__ystem. |
| |
|
2 |
|
| |
|
3 |
The idea behind a journalling file system is that you write out what changes you are about to make to the file system in a special area (called a "Journal"), then every so often you go and "commit" all the changes (actually go and do them). This actually tends to improve performance in the case where you are frequently updating the same data, for example for databases. |
| |
|
4 |
|
| |
|
5 |
If a crash occurs due to a power outage or other event, then when the machine starts up it looks at the journal, and verifies that the journal is correct, if it is correct it actions all the journal entries, and if it is invalid, then it ignores them. |
| |
|
6 |
|
| 3 |
JohnMcPherson |
7 |
This means that the file system will always be in a consistent state, either before the journal was written, or after the journal was written. |
| 2 |
PerryLorier |
8 |
---- |
| |
|
9 |
[JFS] is also the name of [IBM]'s Journalling File System. Original eh? This hasn't been merged into the main linux tree, and I've not heard anything about it (other than, I presume, it's journalling) |
| 4 |
CraigBox |
10 |
|
| |
|
11 |
----- |
| |
|
12 |
CategoryFileSystem%%% |
| 5 |
CraigBox |
13 |
CategoryJournallingFileSystem%%% |
| |
|
14 |
CategoryBtreeFileSystem |
