Has anyone experienced issues with connecting to S3 buckets with external tool since upgrading to to 9.10.1???? Since moving to 9.10.1, S3Browser is longer able to connect.  There seems to be an issue with the url encoding causing signature verification to fail. There was no issue in 9.9.1. Has NetApp made changes in this area in 9.10.1?? ... View more

Hello Everyone,   I have an old system off support:   Model Name: FAS3240 NetApp Release 8.2.5P5 7-Mode: Thu Jan 7 04:22:14 PST 2021   Suddenly 0a has gone offline:   HA Group Notification from xxxxxxxxxxxx(Write Verification Error: Port 0a Failed) CRITICAL   Fri Jan 21 07:47:07 EST [XXXXXXXX:disk.ioMediumError:warning]: Medium error on disk 0a.13.16: op 0x28:5e53efc4:00fc sector 1582559233 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) (1728) [NETAPP X302_WVULC01TSSM NA04] S/N [WD-WCAW32566134] Fri Jan 21 07:47:07 EST [xxxxxxxxxxx:disk.ioReassignSuccess:notice]: disk 0a.13.16: sector 1582559233 was reassigned (140). [NETAPP X302_WVULC01TSSM NA04] S/N [WD-WCAW32566134] Fri Jan 21 07:47:25 EST [xxxxxxxxxx:disk.checksum.offlineAdapter:error]: Adapter 0a taken offline due to checksum verification failure on multiple disks. Fri Jan 21 07:47:25 EST [xxxxxxx:callhome.hba.failed:EMERGENCY]: Call home for Write Verification Error: Port 0a Failed Fri Jan 21 07:47:25 EST [xxxxxxxxx:sas.adapter.offlining:info]: Offlining SAS adapter 0a. Fri Jan 21 07:47:25 EST [xxxxxxxxxxx:sas.adapter.offline:info]: SAS adapter 0a is now offline. Fri Jan 21 07:47:25 EST [xxxxxxxxxx:shelf.config.tospha:info]: System has transitioned to single path HA attached storage   slot 0: SAS Host Adapter 0a (PMC-Sierra PM8001 rev. C, SAS, <OFFLINE (soft)>) Firmware rev: 01.12.09.00 Base WWN: 5:00a098:00353db:b0 Phy State: [0] Disabled [1] Disabled [2] Disabled [3] Disabled QSFP Vendor: Molex Inc. QSFP Part Number: 112-00177+A0 QSFP Type: Passive Copper 2m ID:01 QSFP Serial Number: 111620897   I think it relates to the below KB: https://kb.netapp.com/Advice_and_Troubleshooting/Data_Storage_Systems/FAS_Systems/Call_home_for_Write_Verification_Error%3A_Port_0x_Failed   I also noticed the following on the shelf attached to 0a:   Possible issue on shelf 10 consider re-seat modules: Vendor Unique Element 83-IOM3: (SAS) Element Status Status Bytes Status Descriptions 1 [IOM3 A] : NONCRITICAL 03,0C,00,00 BACKPLANE VPD FAULT, MASTER 2 [IOM3 B] : NONCRITICAL 03,04,00,00 BACKPLANE VPD FAULT Channel: 4b Shelf: 10 SES device path: local access: 4b.10.99 Module type: IOM3; monitoring is active Shelf status: non-critical condition SES Configuration, shelf 10: logical identifier=0x50050cc10201fc08 vendor identification=NETAPP product identification=DS4243 product revision level=0212 Vendor-specific information: Product Serial Number: SHJ0000000030B1 Status reads attempted: 14550397; failed: 0 Control writes attempted: 0; failed: 0 Shelf bays with disk devices installed:   My thoughts would be to replace the cable from 0a to the shelf and consider re-seating the modules.   Does anyone have any ideas for this ? ... View more

Not a question, but a contribution. Here is an excel spreadsheet containing all storage efficiency-related pieces of information. I think it might be useful to share. NetApp's OnTap releases are coming out fast, it's hard to keep an eye on everything. This might help. Not perfect. Will add more to it. Comments are welcomed.  ... View more

As stated in FabricPool, if blocks in S3 object storage got ransom read, then the block will be brought back to the performance tier, sequential read would not bring the block back, and will read directly from S3.    So, this comes to my question, should a RMAN restoration be a sequential or random read, from the SSD aggregate with attached S3 object? suppose blocks are already in S3.   As my understanding to SSD, the write could write to any new pages without data on, so, initially, all pages are new/blank,  so these write/read should be sequential, and would not reheat blocks in S3. Further, Write would not overwrite or delete if there are available new/ blank pages. When all blocks are full, then it would seek for what page can be deleted. Based on this process, after some time, the later writes can scattered to any place in the SSD drive, then later write/read will become random, and then read to blocks in S3 will be reheat, and brought back to the local tier.    Is my understanding correct? ... View more

We had a part of a vmware cluster go down this morning when a VMFS volume containing some iSCSI VMs apparently became unreachable for a period of time.   The only thing we see in the Netapp logs is:   Event: ksmf.svc.watchdog: "kSMF service thread held > 25 (sec) by application for table d_vdisk_lun" Message Name : ksmf.svc.watchdog Sequence Number : 1420474 Description : This message occurs when an application is taking too long to complete a kSMF operation. Action : (NONE)   Anyone seen this?   Would this error reflect a lockup on the Netpp side, or would this error be a side effect of the iSCSi network connectivity going away for a while? I could not find any info in Google search for this error string....   w ... View more