Skip to content

Commit 9222213

Browse files
turibeamadvance
andcommitted
Small doc updates, clarify references to "snapraid touch". (#19)
Co-authored-by: Andrea Mazzoleni <amadvance@gmail.com>
1 parent 85ca997 commit 9222213

File tree

6 files changed

+50
-47
lines changed

6 files changed

+50
-47
lines changed

INSTALL

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -7,25 +7,27 @@ code from http://www.snapraid.it and unpack it with:
77
tar xf snapraid-*.tar.gz
88
cd snapraid-*
99

10-
To configure and build run:
10+
To configure and build, run:
1111

1212
./configure
1313
make
1414

15-
To check for correctness of the application run:
15+
To run the correctness tests for the application:
1616

1717
make check
1818

19-
If it terminates with "Success", you can install the application and
20-
the documentation running as root:
19+
If this terminates with "Success", you can install the application and
20+
the documentation by running:
2121

2222
sudo make install
2323

24-
To start using SnapRAID you have to change the example configuration
25-
file snapraid.conf.example to fit your needs and copy it in /etc/snapraid.conf
24+
(The snapraid application itself does not require root privileges.)
25+
26+
To start using SnapRAID, change the example configuration
27+
file snapraid.conf.example to fit your needs and copy it to /etc/snapraid.conf
2628

2729
To get more help, see the "Getting Started" section in the snapraid manpage
28-
typing:
30+
by typing:
2931

3032
man snapraid
3133

cmdline/snapraid.c

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ void usage(void)
3838
{
3939
version();
4040

41-
printf("Usage: " PACKAGE " status|diff|sync|scrub|list|dup|up|down|smart|pool|check|fix [options]\n");
41+
printf("Usage: " PACKAGE " status|diff|sync|scrub|list|dup|up|down|touch|smart|pool|check|fix [options]\n");
4242
printf("\n");
4343
printf("Commands:\n");
4444
printf(" status Print the status of the array\n");
@@ -49,6 +49,7 @@ void usage(void)
4949
printf(" dup Find duplicate files\n");
5050
printf(" up Spin-up the array\n");
5151
printf(" down Spin-down the array\n");
52+
printf(" touch Add non-zero ns timestamps to files\n");
5253
printf(" smart SMART attributes of the array\n");
5354
printf(" pool Create or update the virtual view of the array\n");
5455
printf(" check Check the array\n");

cmdline/status.c

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -466,14 +466,14 @@ int state_status(struct snapraid_state* state)
466466
}
467467

468468
if (unscrubbed_blocks) {
469-
printf("The %u%% of the array is not scrubbed.\n", muldiv_upper(unscrubbed_blocks, 100, blockmax));
469+
printf("%u%% of the array is not scrubbed.\n", muldiv_upper(unscrubbed_blocks, 100, blockmax));
470470
} else {
471471
printf("The full array was scrubbed at least one time.\n");
472472
}
473473

474474
if (file_zerosubsecond) {
475-
printf("You have %u files with zero sub-second timestamp.\n", file_zerosubsecond);
476-
printf("Run the 'touch' command to set it to a not zero value.\n");
475+
printf("You have %u files with a zero sub-second timestamp.\n", file_zerosubsecond);
476+
printf("Run 'snapraid touch' to set their sub-second timestamps to a non-zero value.\n");
477477
} else {
478478
printf("No file has a zero sub-second timestamp.\n");
479479
}

snapraid.1

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -115,30 +115,30 @@ consider before using it.
115115
.PP
116116
The main one is that if a disk fails, and you haven\'t recently synced,
117117
you may be unable to do a complete recover.
118-
More specifically, you may be unable to recover up to the size of the
119-
amount of the changed or deleted files from the last sync operation.
118+
More specifically, you may be unable to recover up to the size of
119+
the changed or deleted files from the last sync operation.
120120
This happens even if the files changed or deleted are not in the
121-
failed disk. This is the reason because SnapRAID is better suited for
121+
failed disk. This is why SnapRAID is better suited for
122122
data that rarely change.
123123
.PP
124-
Instead the new added files don\'t prevent the recovering of the already
125-
existing files. You may only lose the just added files, if they are on
124+
On the other hand, newly added files don\'t prevent recovering already
125+
existing files. You may only lose the recently added files, if they are on
126126
the failed disk.
127127
.PP
128-
Other limitations are:
128+
Other Snapraid limitations are:
129129
.PD 0
130130
.IP \(bu
131-
You have different file\-systems for each disk.
132-
Using a RAID you have only a big file\-system.
131+
With Snapraid, you still have separate file\-systems for each disk.
132+
With RAID you get a single large file\-system.
133133
.IP \(bu
134-
It doesn\'t stripe data.
134+
Snapraid doesn\'t stripe data.
135135
With RAID you get a speed boost with striping.
136136
.IP \(bu
137-
It doesn\'t support real\-time recovery.
137+
Snapraid doesn\'t support real\-time recovery.
138138
With RAID you do not have to stop working when a disk fails.
139139
.IP \(bu
140-
It\'s able to recover damages only from a limited number of disks.
141-
With a Backup you are able to recover from a complete
140+
Snapraid is able to recover damages only from a limited number of disks.
141+
With a Backup you can recover from a complete
142142
failure of the whole disk array.
143143
.IP \(bu
144144
Only file, time\-stamps, symlinks and hardlinks are saved.

snapraid.d

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -55,26 +55,26 @@ Limitations
5555

5656
The main one is that if a disk fails, and you haven't recently synced,
5757
you may be unable to do a complete recover.
58-
More specifically, you may be unable to recover up to the size of the
59-
amount of the changed or deleted files from the last sync operation.
58+
More specifically, you may be unable to recover up to the size of
59+
the changed or deleted files from the last sync operation.
6060
This happens even if the files changed or deleted are not in the
61-
failed disk. This is the reason because SnapRAID is better suited for
61+
failed disk. This is why SnapRAID is better suited for
6262
data that rarely change.
6363

64-
Instead the new added files don't prevent the recovering of the already
65-
existing files. You may only lose the just added files, if they are on
64+
On the other hand, newly added files don't prevent recovering already
65+
existing files. You may only lose the recently added files, if they are on
6666
the failed disk.
6767

68-
Other limitations are:
68+
Other Snapraid limitations are:
6969

70-
* You have different file-systems for each disk.
71-
Using a RAID you have only a big file-system.
72-
* It doesn't stripe data.
70+
* With Snapraid, you still have separate file-systems for each disk.
71+
With RAID you get a single large file-system.
72+
* Snapraid doesn't stripe data.
7373
With RAID you get a speed boost with striping.
74-
* It doesn't support real-time recovery.
74+
* Snapraid doesn't support real-time recovery.
7575
With RAID you do not have to stop working when a disk fails.
76-
* It's able to recover damages only from a limited number of disks.
77-
With a Backup you are able to recover from a complete
76+
* Snapraid is able to recover damages only from a limited number of disks.
77+
With a Backup you can recover from a complete
7878
failure of the whole disk array.
7979
* Only file, time-stamps, symlinks and hardlinks are saved.
8080
Permissions, ownership and extended attributes are not saved.

snapraid.txt

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -65,26 +65,26 @@ consider before using it.
6565

6666
The main one is that if a disk fails, and you haven't recently synced,
6767
you may be unable to do a complete recover.
68-
More specifically, you may be unable to recover up to the size of the
69-
amount of the changed or deleted files from the last sync operation.
68+
More specifically, you may be unable to recover up to the size of
69+
the changed or deleted files from the last sync operation.
7070
This happens even if the files changed or deleted are not in the
71-
failed disk. This is the reason because SnapRAID is better suited for
71+
failed disk. This is why SnapRAID is better suited for
7272
data that rarely change.
7373

74-
Instead the new added files don't prevent the recovering of the already
75-
existing files. You may only lose the just added files, if they are on
74+
On the other hand, newly added files don't prevent recovering already
75+
existing files. You may only lose the recently added files, if they are on
7676
the failed disk.
7777

78-
Other limitations are:
78+
Other Snapraid limitations are:
7979

80-
* You have different file-systems for each disk.
81-
Using a RAID you have only a big file-system.
82-
* It doesn't stripe data.
80+
* With Snapraid, you still have separate file-systems for each disk.
81+
With RAID you get a single large file-system.
82+
* Snapraid doesn't stripe data.
8383
With RAID you get a speed boost with striping.
84-
* It doesn't support real-time recovery.
84+
* Snapraid doesn't support real-time recovery.
8585
With RAID you do not have to stop working when a disk fails.
86-
* It's able to recover damages only from a limited number of disks.
87-
With a Backup you are able to recover from a complete
86+
* Snapraid is able to recover damages only from a limited number of disks.
87+
With a Backup you can recover from a complete
8888
failure of the whole disk array.
8989
* Only file, time-stamps, symlinks and hardlinks are saved.
9090
Permissions, ownership and extended attributes are not saved.

0 commit comments

Comments
 (0)