Hello team,   I open this query to see if you can help me. In a situation in which there is a server with 14 disks (1TB each) that form a DDP with 2 parity disks and 1 preservation capacity disk, theoretically 11TB of total storage would be available. By default, an alert is added with a threshold of 85% occupancy.   Bearing this information in mind, is it necessary to have some additional % available to avoid a performance loss or could 100% of the remaining space be used? Thank you very much. Regards ... View more

Hello People Customer wants to use SAS ports to be able to export a volume to HP machines in Direct Attach. What is the best practice? How do I enable the SAS protocol? What is the best configuration? DDP or RAID6?   Thank's in advance Alessandro ... View more

Hi, we have a controller pair (out of support since EoApril, unfortunately) which went into an LJ lockdown. AFAICS that comes from a logical failure of the Config Database. That condition started in timely vicinity of a disk replacement. The storage is organized in disk pools ("declustered arrays"). I did not notify the issue immediately as I was replacing more disks in other storage systems. I do also not completely recall whether the LJ lockdown was the initial state after the failure set on; I realized it only after resetting the controllers. However, they were unreachable via their admin IFs before the reset. The meaning of the LJ code is "The controller has insufficient memory to support the current configuration". We tried resetting the system in different variants (resetting one controller while the other kept running, resetting one controller with the respective other one removed, all with the newly inserted disk in or removed, respectively. We also tried running lemClearLockdown. The controllers always run into the same lockdown. I suspect the database has gotten some (invalid) entry which confuses the CRUSH setup, which can also be derived from the boot messages visible at the serial console which include: 05/25/22-11:53:06 (tRAID): WARN: Error threshold exceeded: "Client_Crush_Invalid_Memory_Config" 05/25/22-11:53:06 (tRAID): WARN: LEM:Client threshold Exceeded 05/25/22-11:53:06 (tRAID): NOTE: LEM: checkError(); Error threshold exceeded;SUSPENDED_LOCKDOWN; 05/25/22-11:53:06 (tRAID): WARN: sodLockdownCheck: sodSequence update: SuspLockdown 05/25/22-11:53:06 (tRAID): NOTE: Inter-Controller Communication Channels Opened 05/25/22-11:53:06 (tRAID): WARN: Error threshold exceeded: "Client_Crush_Invalid_Memory_Config" 05/25/22-11:53:06 (tRAID): WARN: Client reported lockdown: "Client_Crush_Invalid_Memory_Config" 05/25/22-11:53:06 (tRAID): NOTE: Flashing tray summary fault LED The memory of the controllers has of course not been changed by us. While we do have data backups, the controller pair contributes to the storage of file systems with about 11 PB, and if ever possible we would not want to restore from tape as that would probably take very long. We'd rather want to fix the supposed issue with the database. We found stored database exports from both controllers which were very likely initiated by the StorageManager (located in /var/opt/SM/monitor/dbcapture/, last ones from Jan 12 this year). I have to find out whether disks were replaced after that; if not (except for the recent one) I hope removing that lastly installed disk and replaying the config from January could do the trick. However, I do not know how to transfer and activate an exported database dump via the serial line. If there are other/better ways to overcome our problem, I'd be glad to learn about them. BTW: we are also trying to get Netapp involved, but as we purchased these systems as OEM we are not yet there. Sincerely ufa ... View more

Does NetApp  EF300SASExpansion support file-level storage? or is it strictly block-level storage? I am unable to find options for configuring the NAS volumes on array UI   ... View more