HP P4000 9.0 HP StorageWorks P4000 SAN Solution User Guide - Page 202

Measuring disk capacity and volume size, Block systems and file systems

Page 202 highlights

Category Usable space Provisioned space Description Space available for storage after RAID has been configured. Amount of space allocated for volumes and snapshots. Measuring disk capacity and volume size All operating systems that are capable of connecting to the SAN via iSCSI interact with two disk space accounting systems-the block system and the native file system (on Windows, this is usually NTFS). Table 44 Common native file systems OS Windows Linux Netware Solaris VMWare File System Names NTFS, FAT EXT2, EXT3 NWFS UFS VMFS Block systems and file systems Operating systems see hard drives (both directly connected [DAS] and iSCSI connected [SAN]) as abstractions known as "block devices": arbitrary arrays of storage space that can be read from and written to as needed. Files on disks are handled by a different abstraction: the file system. File systems are placed on block devices. File systems are given authority over reads and writes to block devices. iSCSI does not operate at the file system level of abstraction. Instead, it presents the iSCSI SAN volume to an OS such as Microsoft Windows as a block device. Typically, then, a file system is created on top of this block device so that it can be used for storage. In contrast, an Oracle database can use an iSCSI SAN volume as a raw block device. Storing file system data on a block system The Windows file system treats the iSCSI block device as simply another hard drive. That is, the block device is treated as an array of blocks which the file system can use for storing data. As the iSCSI initiator passes writes from the file system, the SAN/iQ software simply writes those blocks into the volume on the SAN. When you look at the CMC, the used space displayed is based on how many physical blocks have been written for this volume. When you delete a file, typically the file system updates the directory information which removes that file. Then the file system notes that the blocks which that file previously occupied are now freed. Subsequently, when you query the file system about how much free space is available, the space occupied by the deleted files appears as part of the free space, since the file system knows it can overwrite that space. However, the file system does not inform the block device underneath (the SAN/iQ volume) that there is freed-up space. In fact, no mechanism exists to transmit that information. There is no SCSI command 202 Provisioning storage

  • 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
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350

Description
Category
Space available for storage after RAID has been configured.
Usable space
Amount of space allocated for volumes and snapshots.
Provisioned space
Measuring disk capacity and volume size
All operating systems that are capable of connecting to the SAN via iSCSI interact with two disk
space accounting systems
the block system and the native file system (on Windows, this is usually
NTFS).
Table 44 Common native file systems
File System Names
OS
NTFS, FAT
Windows
EXT2, EXT3
Linux
NWFS
Netware
UFS
Solaris
VMFS
VMWare
Block systems and file systems
Operating systems see hard drives (both directly connected [DAS] and iSCSI connected [SAN]) as
abstractions known as
block devices
: arbitrary arrays of storage space that can be read from and
written to as needed.
Files on disks are handled by a different abstraction: the file system. File systems are placed on block
devices. File systems are given authority over reads and writes to block devices.
iSCSI does not operate at the file system level of abstraction. Instead, it presents the iSCSI SAN volume
to an OS such as Microsoft Windows as a block device. Typically, then, a file system is created on
top of this block device so that it can be used for storage. In contrast, an Oracle database can use
an iSCSI SAN volume as a raw block device.
Storing file system data on a block system
The Windows file system treats the iSCSI block device as simply another hard drive. That is, the block
device is treated as an array of blocks which the file system can use for storing data. As the iSCSI
initiator passes writes from the file system, the SAN/iQ software simply writes those blocks into the
volume on the SAN. When you look at the CMC, the used space displayed is based on how many
physical blocks have been written for this volume.
When you delete a file, typically the file system updates the directory information which removes that
file. Then the file system notes that the blocks which that file previously occupied are now freed.
Subsequently, when you query the file system about how much free space is available, the space
occupied by the deleted files appears as part of the free space, since the file system knows it can
overwrite that space.
However, the file system does not inform the block device underneath (the SAN/iQ volume) that there
is freed-up space. In fact, no mechanism exists to transmit that information. There is no SCSI command
Provisioning storage
202