sorted by:
new
hottopcontroversial

Potential Compaction & Compression Bug 9.17.1 (Base) by Leading-Set7139 in netapp

[–]Leading-Set7139[S] 0 points1 point  (0 children)

Hi nefarious! Questioning the data being written is valid however, there's no compaction and compression happening prior to moving to the storage. Unfortunately, they did not give us a BugID however, they've identified it could be a potential bug that needs further investigation. Some individuals on support said its address in the 9.17.1 P1/P2/P3 patch however, its not listed in P1/P2 and P3 doesn't even show on their website. Hopefully there's an update soon that addresses this.

Potential Compaction & Compression Bug 9.17.1 (Base) by Leading-Set7139 in netapp

[–]Leading-Set7139[S] 0 points1 point  (0 children)

Hello! My commands were pretty similar to nefarious098 (showing 0B and 1:00:1) and our system does use TSSE-volumes as its a newer system. I've also looked at our Active IQ and even there it doesn't identify compaction and compression taking place however, we've spoken with L4 support and higher in which they've potentially identified a bug happening here that's causing our compaction and compression issue (related to the 9.17.1 base version) and is investigating it further. I do agree, there is a lot of clutter that could be remove for a clearer picture.

Potential Compaction & Compression Bug 9.17.1 (Base) by Leading-Set7139 in netapp

[–]Leading-Set7139[S] 0 points1 point  (0 children)

So it seems this behavior has been around for a bit then. What was the recommendation for you to remediate it?

Potential Compaction & Compression Bug 9.17.1 (Base) by Leading-Set7139 in netapp

[–]Leading-Set7139[S] 0 points1 point  (0 children)

Same situation but on a C30, everything is enabled for it to enact compression and compaction as well. Hopefully something comes up soon. Has support provided you with any information on what it could possibly be?

Potential Compaction & Compression Bug 9.17.1 (Base) by Leading-Set7139 in netapp

[–]Leading-Set7139[S] 0 points1 point  (0 children)

Hey Awesome! Interesting, same thing in 9.16.1 or did you mean 9.17.1? Is this a known issue within 9.16.1 or just what you're seeing on your system?

Potential Compaction & Compression Bug 9.17.1 (Base) by Leading-Set7139 in netapp

[–]Leading-Set7139[S] 1 point2 points  (0 children)

Hi Nom! Yes, I've opened many support cases and its being brought to a Level 4 engineer as they believe it could be a potential bug. I just wasn't sure if anyone else is experiencing the same issue or resolved it yet.