Adaptec 5325301507 Administration Guide - Page 75

Volume Management Tools, To Check the Root Filesystem, To Check a Filesystem on a Volume, Function

Page 75 highlights

Volumes Volume Management Tools The SnapServer offers several tools for monitoring and controlling how storage space on a volume is used. Function Ongoing Maintenance Email Notification Volume Usage Quotas Navigation Path Navigate to the Storage > Volumes screen, from which you can create, view, edit, and delete volumes. The server can notify you when a volume is full. This allows you to increase volume size or take other actions to ensure workflows are not disrupted (Server > Email Notification). You can view the current utilization totals for each volume, from the Storage > Volumes screen. Use quotas (Storage > Quotas) to limit the amount of storage space on a volume that specific users or groups can consume. See Quotas for more information. You can view volume status from the Storage > Volumes screen. To Check the Root Filesystem Caution Checking the root filesystem requires a reboot of the server. 1 Select the Check Root Filesystem link. 2 On the page that opens, click the Check Filesystem button. 3 Click Yes when informed that a reboot will be required. 4 To view a log of the results, click the View Log button. To Check a Filesystem on a Volume Click the Check Filesystem link to check and repair the filesystem on this volume. You can configure GuardianOS to run this check on three levels: • Do not repair errors - This option will check for errors, but will not repair them. It is recommended that you do this periodically, especially following a power outage or any other unconventional outage. • Repair errors - It is recommended that you run this level if you suspect file system damage may have occurred (e.g., if a previous Do not repair errors operation reported file system errors). • Repair errors (aggressive) - It is only recommended that you run this level if you have been advised to do so by SnapServer Technical Support, or if Repair errors has failed to solve the problem and you are willing to risk loss of data. Chapter 4 Storage Configuration and Expansion 59

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250

Volumes
Chapter 4
Storage Configuration and Expansion
59
Volume Management Tools
The SnapServer offers several tools for monitoring and controlling how storage
space on a volume is used.
You can view volume status from the
Storage > Volumes
screen.
To Check the Root Filesystem
Caution
Checking the root filesystem requires a reboot of the server.
1
Select the
Check Root Filesystem
link.
2
On the page that opens, click the
Check Filesystem
button.
3
Click
Yes
when informed that a reboot will be required.
4
To view a log of the results, click the
View Log
button.
To Check a Filesystem on a Volume
Click the
Check Filesystem
link to check and repair the filesystem on this volume.
You can configure GuardianOS to run this check on three levels:
Do not repair errors
— This option will check for errors, but will not repair them.
It is recommended that you do this periodically, especially following a power
outage or any other unconventional outage.
Repair errors
— It is recommended that you run this level if you suspect file
system damage may have occurred (e.g., if a previous
Do not repair errors
operation reported file system errors).
Repair errors (aggressive)
— It is only recommended that you run this level if you
have been advised to do so by SnapServer Technical Support, or if
Repair errors
has failed to solve the problem and you are willing to risk loss of data.
Function
Navigation Path
Ongoing Maintenance
Navigate to the
Storage > Volumes
screen, from which you
can create, view, edit, and delete volumes.
Email Notification
The server can notify you when a volume is full. This allows
you to increase volume size or take other actions to ensure
workflows are not disrupted (
Server > Email Notification
).
Volume Usage
You can view the current utilization totals for each volume,
from the
Storage > Volumes
screen.
Quotas
Use quotas (
Storage > Quotas
) to limit the amount of
storage space on a volume that specific users or groups can
consume.
See Quotas for more information.