Hi All, Hopefully you can help me. Quite frequently throughout the day we are getting the following event for 6 volumes. I'm not sure why we are getting it sis.changelog.full: SIS change logging metafile for volume VOLUMENAME@vserver:0a0985e1a8a is full. When searching around i've found this NetApp article "SIS.changelog.full" metafile for volume is full for a SnapMirror destination volume - NetApp Knowledge Base - but it doesn't look like this applies to us as when I run "volume efficiency show -vserver VSERVERNAME VOLUMENAME" - the status is coming back as "idle". The "Last Operation Status" is also coming back as success. Can anyone tell me why this happening and how to resolve this? Its happening every hour or so. Any help would be very much appreciated. Is it possible to explain what its actually doing / trying to do also please?
... View more
hello and sorry for my english, I always do updates on my Netapp equipment. I now in version 9.15.1P17 on all clusters ! I'd like now to upgrade to new version. I have: AFF-C250 FAS2720 FAS2820 Witch version i have to choose for upgrade ? 9.16, 9.17 or 9.18 ? i'd like same version on all clusters, easier... Can i have troubles when upgrade ? i use CIFS share, ISCSI volumes and NFS volumes for Vmware, Consistency group with mediator (business continuity), snapmirror, antiransomware thanks a lot
... View more
Good day, we want to have a role for a user that is able to expose/hide Snapshots to the clients, both at volume level and share level. We tried with these cmddirnams: volume show volume modify vserver cifs share show vserver cifs share properties but when managing at level share, I still recieve "you aren't authorized to perform this operation" Could someone help? thanks in advance
... View more
Case description: FAS2520 / Data ONTAP 7-Mode: aggr0 double degraded, replacement drives detected as SAS 15000 and not accepted as matching spares, maintenance disk stuck in testing. Current problem aggr0 is currently double degraded. The RAID group shows two FAILED data members. We have available spare disks, but the system is not using them for rebuild. A maintenance disk (0a.00.3) remains in testing status. Observed behavior From aggr status -r: Aggregate aggr0 (online, raid_dp, degraded) (block checksums) RAID group /aggr0/plex0/rg0 (double degraded, block checksums) Two data positions in the RAID group show as FAILED From aggr status -s: Current spare disks are: 0a.00.1 → SAS 15000 0a.00.8 → SAS 15000 (at one point shown as not zeroed) From aggr status -r: Existing RAID group members are shown as FSAS 7200 Maintenance disks section shows: 0a.00.3 → testing, FSAS 7200 From disk show -v: 0a.00.3 shows OWNER = FAILED Drive identification inconsistency From storage show disk -T -x: 0a.00.1 and 0a.00.8 are identified as: Model = X477_SMBPE04TA07 Rev = NA00 Type = SAS Most other data disks in the shelf are identified as: Model = X477_SMEGX04TA07 Rev = NA03 Type = FSAS We also replaced the disk in slot 0a.00.8 with another brand-new replacement drive, but the newly inserted disk was still detected as SAS / RPM 15000. What we already checked raid.disktype.enable = off raid.rpm.ata.enable = off Broken disks (empty) from aggr status -f Current spare disks are owned by the controller and use block checksum Another new replacement drive inserted into 0a.00.8 still shows as SAS 15000 Our concern It appears that the available replacement drives are not being accepted as valid matching spares for aggr0, possibly because the RAID group members are shown as FSAS 7200 while the replacement drives are detected as SAS 15000. We need help with Please confirm whether the replacement drives/FRUs are correct for this platform and RAID group. Please confirm whether there is a disk qualification / drive firmware / recognition issue causing the system to identify replacement drives as SAS instead of FSAS. Please advise the supported recovery procedure for aggr0 in the current double degraded state. Please advise how to handle maintenance disk 0a.00.3, which remains in testing and also appears as OWNER = FAILED. Commands / outputs available We can provide the outputs of: aggr status -r aggr status -s aggr status -f storage show disk -T -x storage show disk -x sysconfig -d disk show -v options raid.disktype.enable options raid.rpm.ata.enable Please advise next steps. Best regards
... View more
Recently I met that FAS2520 HDD failed issue (0a.00.1 and 0a.00.8 failed, 0a.00.3 in maintenance testing) and no available spare HDD. I order 3 new HDDs with same PN, and set spares to new 0a.00.1 and 0a.00.8 successfully. But system did not auto rebuilding. And detect 0a.00.1 and 0a.00.8 as SAS with RPM 15000 while others are FSAS with RPM7200. What is the best next plan? Thanks in advance for your advice.
... View more
