Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 17 results
    • WAFL Inconsistent user data block with X306_WKOJN02TSSM or X308_WKOJN03TSSM disks
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/WAFL_Inconsistent_user_data_block_with_X308_WKOJN03TSSM_disks
      [node_name: disk_server_0: disk.ioMediumError:notice]: Medium error on disk 0a.21.18: op 0x28:82b99180:0240 sector 2193199589 SCSI:medium error - Unrecovered read error - If the disk is in a RAID grou...[node_name: disk_server_0: disk.ioMediumError:notice]: Medium error on disk 0a.21.18: op 0x28:82b99180:0240 sector 2193199589 SCSI:medium error - Unrecovered read error - If the disk is in a RAID group, the subsystem will attempt to reconstruct unreadable data (3 11 0 d4) (1831) Disk 0a.21.18 Shelf 21 Bay 18 [NETAPP X306_WKOJN02TSSM NA00] S/N [WD-WMC1P0DXXXXX] UID
    • How to identify the FlexGroup constituent from client file path
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/How_to_identify_the_FlexGroup_constituent_from_client_file_path
      Applies to ONTAP 9 FlexGroup imbalance Volume Data Set ID (DSID) NetApp XCP tool (Linux, Windows) Description FlexGroup exposes a single namespace to the end user, making client file path agnostic to ...Applies to ONTAP 9 FlexGroup imbalance Volume Data Set ID (DSID) NetApp XCP tool (Linux, Windows) Description FlexGroup exposes a single namespace to the end user, making client file path agnostic to the Flexgroup constituent. FlexGroup constituent identification of the file helps manual balancing of FlexGroup.
    • 7MTT v2.0: Detailed description of configuration transition/manual steps: SnapMirror, NameServices, and WAFL
      https://kb.netapp.com/Legacy/ONTAP/7Mode/7MTT_v2_0__Detailed_description_of_configuration_transition_manual_steps__SnapMirror_NameServices_and_WAFL
      If the Data ONTAP 7-Mode option snapmirorr.access is set to legacy and if Data ONTAP 7-Mode option snapmirror.checkip.enable is set to on, then add at least one IC LIF IP address of each node that own...If the Data ONTAP 7-Mode option snapmirorr.access is set to legacy and if Data ONTAP 7-Mode option snapmirror.checkip.enable is set to on, then add at least one IC LIF IP address of each node that owns the transitioning clustered Data ONTAP volume to the /etc/snapmirror.allow file of the Data ONTAP 7-Mode storage system.
    • Why is there no difference for field 'logical-available' in 'vol show' and 'vol show-space' when logical space reporting is enabled?
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/Why_is_there_no_difference_for_field_logical_available_in_vol_show_and_vol_show_space_when_logical_space_reporting_is_enabled
      By default, we only populate logical-available when logical reporting is enabled on the volume: ::> vol show -volume vol1 -fields logical-available fas8200-2n-ams-1::> vol show -volume vol1 -fields lo...By default, we only populate logical-available when logical reporting is enabled on the volume: ::> vol show -volume vol1 -fields logical-available fas8200-2n-ams-1::> vol show -volume vol1 -fields logical-available The vol show-space command will give back logical-available regardless if logical space reporting is enabled: ::> vol show-space -volume vol1 -fields logical-available Showing logical-available through vol show-space command is not intended and will be fixed in future releases.
    • ONTAP WAFL Hung Panic may impact SAN protocol services
      https://kb.netapp.com/on-prem/ontap/da/SAN/SAN-KBs/ONTAP_WAFL_Hung_Panic_may_impact_SAN_protocol_services
      Applies to ONTAP 9 Issue ONTAP WAFL Hung Panic may impact SAN protocol services Panic String: WAFL hung for netapp_agg0. in SK process wafl_exempt12 on release 9.10.1P1
    • E-Series  - FlexArray - WAFL hung
      https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series__-_FlexArray_-_WAFL_hung
      Applies to FlexArrray ONTAP 9.6P12 E5500 CFW 08.25.20.00 Issue Panic caused by WAFL hang Fri Oct 15 14:42:26 CEST [TEST: wafl_exempt01: sk.panic:alert]: Panic String: WAFL hung for aggregate_xxx in SK...Applies to FlexArrray ONTAP 9.6P12 E5500 CFW 08.25.20.00 Issue Panic caused by WAFL hang Fri Oct 15 14:42:26 CEST [TEST: wafl_exempt01: sk.panic:alert]: Panic String: WAFL hung for aggregate_xxx in SK process wafl_exempt01 on release 9.6P12 (C)
    • NVRAM purpose during ONTAP outage
      https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/NVRAM_purpose_during_ONTAP_outage
      This data is checked for and when found, is replayed to the local memory buffer and immediately re-processed through the WAFL and RAID layers and written to disk during the next CP. Since all write da...This data is checked for and when found, is replayed to the local memory buffer and immediately re-processed through the WAFL and RAID layers and written to disk during the next CP. Since all write data for one node is also stored in the partner controller’s NVRAM, when the takeover occurs and the downed node boots virtually, all the writes that had been acknowledged are available for it to replay to its memory buffer and process through WAFL and RAID layers and then written to disk.
    • SnapMirror alert with error "Volume not found. (entry doesn't exist)"
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_alert_with_error_Volume_not_found_entry_doesnt_exist
      Thu Jul 23 11:30:00 EDT [filer: mgwd: mgmt.snapmir.schd.trans.fail:alert]: Scheduled transfer from source volume 'vol01' to destination volume(s) 'SVM://<vol_msid>' failed with error 'Volume "SVM:vol0...Thu Jul 23 11:30:00 EDT [filer: mgwd: mgmt.snapmir.schd.trans.fail:alert]: Scheduled transfer from source volume 'vol01' to destination volume(s) 'SVM://<vol_msid>' failed with error 'Volume "SVM:vol01" not found. (entry doesn't exist)'. Job ID xxxx. Destination volume not present in VLDB and unknown in WAFL: Please try to first fix the volume with vreport for volume, and check again. To force the removal of the SnapMirror entry, run 'debug vreportfix -type snapmirror -sm-force-clean-up'
    • An error message "raid.multierr.bad.block" is reported
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/An_error_message_raid_multierr_bad_block_is_reported
      Applies to ONTAP 9 Data ONTAP 8 Issue Error in event log. Example Sun Jan 01 12:00:00 CEST [Cluster-01: raidio_thread: raid_multierr_bad_block_1:error]: ... ... raid.multierr.bad.block (WAFL INCONSIST...Applies to ONTAP 9 Data ONTAP 8 Issue Error in event log. Example Sun Jan 01 12:00:00 CEST [Cluster-01: raidio_thread: raid_multierr_bad_block_1:error]: ... ... raid.multierr.bad.block (WAFL INCONSISTENT USER DATA BLOCK) CRITICAL
    • A file with the same name or DSID already exists on disk, when creating volume with DSID number XXXX in ONTAP
      https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/A_file_with_the_same_name_or_DSID_already_exists_on_disk_when_creating_volume_with_DSID_number_XXXX_in_ONTAP
      INFORMATIONAL mgmtgwd.jobmgr.jobcomplete.failure: Job "Vol Create" [id 12055] (Create NETAPP_VOL_234c0b8d162011e89d9600a098ba3cfa_A) completed unsuccessfully: A file with the same name or DSID already...INFORMATIONAL mgmtgwd.jobmgr.jobcomplete.failure: Job "Vol Create" [id 12055] (Create NETAPP_VOL_234c0b8d162011e89d9600a098ba3cfa_A) completed unsuccessfully: A file with the same name or DSID already exists on disk, when creating volume "NETAPP_VOL_234c0b8d162011e89d9600a098ba3cfa_A" with DSID 1771. (1). Client is unable to delete volume as it does no longer appears at the cluster level in VLDB. Volume move won't progress, it cannot be paused, cancelled, or aborted due to 'volume busy'
    • Is it possible to replace small drives with bigger ones without downsizing them?
      https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Is_it_possible_to_replace_small_drives_with_bigger_ones_without_downsizing_them
      The VBNs used by each disk are "fixed" in the RAID group so, if a disk is replaced with a bigger one, the amount of VBNs will remain. The empty space in the bigger drive won't be used by WAFL for new ...The VBNs used by each disk are "fixed" in the RAID group so, if a disk is replaced with a bigger one, the amount of VBNs will remain. The empty space in the bigger drive won't be used by WAFL for new VBNs. The aggregate with mixed drives should be destroyed and recreated again with the correct ones. How does Data ONTAP select spares for aggregate creation, aggregate addition and failed disk replacement? How to reduce the number of data disks in an Aggregate / Volume / RAID group