checksum type of an array LUN:

-----------------------------------------All array LUNs in an aggregate must be the same checksum type

For array LUNs, Data ONTAP supports both block (BCS) checksum and zoned (ZCS) ch
ecksum types.
You specify a checksum type when you assign ownership of an array LUN to a stora
ge system (or accept the default of BCS).
Block checksums :
With block checksums, Data ONTAP reserves 12.5 percent of the space of the array
LUN is used
for checksum. Data ONTAP uses BCS by default because it provides better performa
nce in
certain workloads.
Zoned checksums
Zoned checksums have better storage capacity utilization. However, at certain wo
rkloads ZCS
LUNs have a performance impact. Random-read intensive workloads are affected the
most.
Note: Non-disruptive upgrade is not supported for aggregates configured for RAID
4. For more
information about non-disruptive upgrade, see the Data ONTAP 7-Mode Upgrade Guid
e.
aggr status -r
priv set advanced
disk remove_ownership disk-name
disk remove disk-name
priv set
disk show -v
version
disk remove disk_name
sync mirror ---> licensed product and it requirest additional cost
Note: You change the size of RAID groups on a per-aggregate basis. You cannot ch
ange the size of an individual RAID group.
Large RAID group configurations offer the following advantages:
1. More data drives available
2. Small improvement in storage system performance. Write operations are general
ly faster with larger RAID groups than with smaller RAID groups.
Small RAID group configurations offer the following advantages:
1.Shorter disk reconstruction times. In case of disk failure within a small RAID
group, data reconstruction time is usually shorter than it would be within a la
rge RAID group.
2. Decreased risk of data loss due to multiple disk failures. The probability of
data loss through double-disk failure within a RAID4 group or through triple-di
sk failure within a RAID-DP group
is lower within a small RAID group than within a large RAID group.
If two disks have failed in a RAID-DP group, the RAID group goes into double-deg
raded mode
Data ONTAP issues warnings to the console and logs if you have fewer than one ho
t

spare disk that matches the attributes of each disk in your storage system
raid.min_spare_count
Note: You cannot create aggregates that use RAID4 protection while the
raid.min_spare_count option is set to 0. If either of these requirements is no l
onger met
after this option has been set to 0, the option is automatically set back to 1.
raid.timeout
By default, if Data ONTAP encounters media errors during a RAID reconstruction,
it automaticallyinvokes an advanced mode process (wafliron) that compensates for
the media errors and enables
Data ONTAP to bypass the errors.
If the wafliron process fails or has been disabled, Data ONTAP attempts to place
the affected aggregate in restricted mode. If this attempt fails, the storage s
ystem panics. After a reboot, Data
ONTAP brings up the affected aggregate in restricted mode.
In restricted mode, you can manually invoke the wafliron process in advanced mod
e, or you can schedule downtime for your storage system to run the WAFL_check co
mmand from the Boot menu.
You can disable the wafliron process by using the raid.reconstruction.wafliron.e
nable
option. However, you are advised to leave the process enabled
By default, Data ONTAP performs a weekly RAID-level scrub starting on Sunday at
1:00 a.m. for a duration of six hours
raid.scrub.schedule
raid.scrub.duration
raid.scrub.enable
options raid.scrub.schedule 240m@tue@2,8h@sat@22
options raid.scrub.schedule " "
If you try to run a RAID-level scrub on a RAID group that is not in a normal sta
te (for example, a
group that is reconstructing or degraded), the scrub returns errors and does not
check that RAID
group. You can run a RAID-level scrub on a RAID-DP group with one failed disk.
scrubbing all aggregatges:
aggr scrub start
aggr scrub start aggr2/plex1/rg0
aggr scrub stop aggr0/plex1
aggr scrub status -v
aggr options aggr_name raidsize size
You can reduce the impact of RAID operations on system performance by decreasing
the speed of

RAID operations
raid.reconstruc.perf_impact
raid.reconstruct.perf_impact
================================================================================
===========================================================================\
Aggregates:
---------------FlexVol volumes:the logical file systems that share the physical storage resourc
es,RAID configuration, and plex structure of that common containing aggregate
Aggregate Types:
You cannot change the type of an aggregate
after it is created.
aggr status
syncmirror_local license installed and enabled
Restricted:Some operations, such as parity reconstruction, are allowed, but data
access is not allowed.
foreign:Disks that the aggregate contains were moved to the current storage syst
em from another storage system
growing:Disks are in the process of being added to the aggregate.
initializing:The aggregate is in the process of being initialized.
invalid:The aggregate contains no volumes and none can be added.Typically this h
appens only after an aborted aggr copy operation.
ironing:A WAFL consistency check is being performed on the aggregate
mirror degraded
mirrored:
To use block checksum storage when you create a new aggregate, you must have at
least the
number of block checksum spare disks or array LUNs available that you specified
in the aggr
create command.
You can add block checksum storage to either a block checksum aggregate or a zon
ed
checksum aggregate.
You cannot add zoned checksum storage to a block checksum aggregate.
The following command adds four disks to each plex of a mirrored aggregate aggr_
mir:
aggr add aggr_mir -d 5a.18 5a.19 5a.20 5a.21 -d 8b.14 8b.15 8b.16 8b.
17
Data ONTAP changes the setting for the aggregate s raidsize option to the size of
the largest
RAID group in the aggregate, except in the following situations:
If the aggregate s largest RAID group is larger than the maximum RAID4 group size,
then the
aggregate s raidsize option is set to the maximum.
If the aggregate s largest RAID group is smaller than the default RAID4 group size
, then the
aggregate s raidsize option is set to the default group size.

If the aggregate's raidsize option is already below the default value for RAID4,
it is
reduced by 1
Note: You cannot destroy a SnapLock Compliance aggregate until the retention per
iods for all
data contained in it have expired.
A FlexVol volume is a volume that is loosely coupled to its containing aggregate