|
Lines 923-935
Link Here
|
| 923 |
their way out of the buffer cache onto the disk by the time |
923 |
their way out of the buffer cache onto the disk by the time |
| 924 |
of the crash, &man.fsck.8; is able to recognize this and |
924 |
of the crash, &man.fsck.8; is able to recognize this and |
| 925 |
repair the filesystem by setting the file length to |
925 |
repair the filesystem by setting the file length to |
| 926 |
0). Additionally, the implementation is clear and simple. |
926 |
0. Additionally, the implementation is clear and simple. |
| 927 |
The disadvantage is that meta-data changes are slow. An |
927 |
The disadvantage is that meta-data changes are slow. An |
| 928 |
<command>rm -r</command>, for instance, touches all the files in a |
928 |
<command>rm -r</command>, for instance, touches all the files in a |
| 929 |
directory sequentially, but each directory |
929 |
directory sequentially, but each directory |
| 930 |
change (deletion of a file) will be written synchronously |
930 |
change (deletion of a file) will be written synchronously |
| 931 |
to the disk. This includes updates to the directory itself, |
931 |
to the disk. This includes updates to the directory itself, |
| 932 |
to the i-node table, and possibly to indirect blocks |
932 |
to the inode table, and possibly to indirect blocks |
| 933 |
allocated by the file. Similar considerations apply for |
933 |
allocated by the file. Similar considerations apply for |
| 934 |
unrolling large hierarchies (<command>tar -x</command>).</para> |
934 |
unrolling large hierarchies (<command>tar -x</command>).</para> |
| 935 |
|
935 |
|
|
Lines 953-959
Link Here
|
| 953 |
will be left in an unpredictable state. There is no opportunity |
953 |
will be left in an unpredictable state. There is no opportunity |
| 954 |
to examine the state of the file system when the system |
954 |
to examine the state of the file system when the system |
| 955 |
comes up again; the data blocks of a file could already have |
955 |
comes up again; the data blocks of a file could already have |
| 956 |
been written to the disk while the updates of the i-node |
956 |
been written to the disk while the updates of the inode |
| 957 |
table or the associated directory were not. It is actually |
957 |
table or the associated directory were not. It is actually |
| 958 |
impossible to implement a <command>fsck</command> which is |
958 |
impossible to implement a <command>fsck</command> which is |
| 959 |
able to clean up the resulting chaos (because the necessary |
959 |
able to clean up the resulting chaos (because the necessary |