Thanks! Started it. Much appreciate your help!!On Sunday, December 22, 2019, 03:54:53 PM CST, Scott Eno <s.eno@me.com> wrote:_If_ this is the fingerprint bug, you have to do a “sis start -s <vol>” on each volume with A-SIS emanated. This forces the dedupe process to create new fingerprint, or metadata, db’s.The aggr will then show proper space usage again.--Scott EnoSr. Storage Engineerseno@cooley.comOn Dec 22, 2019, at 3:26 PM, Iluhes <iluhes@yahoo.com> wrote:Thanks Scott, just stop start sis?What is the best way to do it? Am I really out of space?This looks like the old 7-mode bug where you need to re-initialize all your A-SIS jobs to create a new fingerprint db.On Dec 22, 2019, at 3:01 PM, Iluhes via Toasters <toasters@teaparty.net> wrote:Can someone please help me figure out what is happening with the spaceIt is showing aggr at 94% with 33TB used on 35T aggrigate, but my volumes hardly add up to 20TBI dont understand where the space is at. I am lost, is 13TBIs it counting the A-SIS space?aggr show_space -hAggregate 'aggr0'Total space WAFL reserve Snap reserve Usable space BSR NVLOG A-SIS Smtape39TB 4046GB 0KB 35TB 0KB 13TB 0KBSpace allocated to volumes in the aggregateVolume Allocated Used Guaranteevol0 469GB 16GB volumeapp3_root 251GB 2837MB volumeapp3_vol1 3040GB 2405GB volumevol1 15TB 15TB noneapp3_vol2 522GB 395GB volumeAggregate Allocated Used AvailTotal space 19TB 18TB 2244GBSnap reserve 0KB 0KB 0KBWAFL reserve 4046GB 430GB 3615GB> df -hAAggregate total used avail capacityaggr0 35TB 33TB 2248GB 94%aggr0/.snapshot 0TB 0TB 0TB ---%_______________________________________________
Toasters mailing list
Toasters@teaparty.net
http://www.teaparty.net/mailman/listinfo/toasters