lord-carlos

summary:block_size:262144 summary:parity_block_count:22596677 summary:parity_block_total:parity:22884504 summary:parity_block_free:parity:262631 summary:parity_block_free_min:262631 summary:disk_file_count:d1:2343 summary:disk_block_count:d1:22148953 summary:disk_fragmented_file_count:d1:2 summary:disk_excess_fragment_count:d1:2 summary:disk_zerosubsecond_file_count:d1:0 summary:disk_file_size:d1:5805817544902 summary:disk_block_allocated:d1:22148953 summary:disk_block_total:d1:22884504 summary:disk_block_free:d1:707549...

coolio I removed all the excludes, did a snapraid sync and parity stayed at 65G. As expected. Super.

'm real curious how xfs handled that "filled up-then relieved" situation. Thank you. Sure. The least I could do after all the help I got. Again, thanks for your time. Yeah if someone could help me with decision of sync vs sync -R vs sync -F that would be nice. I'm at a complete loss here.

Ayyy Excluded the tvshow.nfo file. 65GB free. But should there not be more free? More like ~170GB? New -vvv after nfo exclusion: Last block occupant state=1 d3 22596677 22596677 =x=x= Last block occupant state=0 d4 22596677 22596677 NO_file Last block occupant state=0 d2 22596677 22596677 NO_file Last block occupant state=0 d1 22596677 22596677 NO_file 11868238865 2019/07/19 12:09:49.480652591 d3 22551403 22596676 =x=x= 11556342671 2019/07/19 12:08:59.693598128 d3 22507319 22551402 =x=x= 11456708398...

Ayyy Excluded the tvshow.nfo file. 65GB free. But should there not be more free? More like ~170GB? New -vvv after nfo exclusion: ~~~ Last block occupant state=1 d3 22596677 22596677 =x=x= Last block occupant state=0 d4 22596677 22596677 NO_file Last block occupant state=0 d2 22596677 22596677 NO_file Last block occupant state=0 d1 22596677 22596677 NO_file 11868238865 2019/07/19 12:09:49.480652591 d3 22551403 22596676 =x=x= 11556342671 2019/07/19 12:08:59.693598128 d3 22507319 22551402 =x=x= 11456708398...

Withhead -120 I get some rather new data. 24969216 2019/07/12 15:45:54.658073807 d3 22600879 22600974 photos/photos/2019\ -\ XXXXX/raw/XXXXX_154554.ARW But also this: Last block occupant state=1 d3 22830267 22830267 serien/The TVSHOW/tvshow.nfo Last block occupant state=0 d4 22830267 22830267 NO_file Last block occupant state=0 d2 22830267 22830267 NO_file Last block occupant state=0 d1 22830267 22830267 NO_file 5961 2019/07/21 12:05:45.681148154 d3 22830266 22830266 serien/The\ TVSHOW/tvshow.nf...

Uhh, that spits out a list of super old data. 0 2018/07/29 16:31:07.628001632 d3 4294967295 4294967295 =x=x= 0 2018/07/29 16:31:07.628001632 d3 4294967295 4294967295 =x=x= 0 2018/07/29 16:31:07.628001632 d3 4294967295 4294967295 =x=x= 0 2018/07/29 16:31:07.544003190 d3 4294967295 4294967295 =x=x= 0 2017/10/09 21:52:38.109160785 d2 4294967295 4294967295 =x=x= 0 2017/10/09 21:52:38.109160785 d2 4294967295 4294967295 =x=x= 0 2017/01/17 19:20:01.673340991 d3 4294967295 4294967295 =x=x= 0 2017/01/17 19:20:01.673340991...

was the very last file listed by the check included among your most recent excludes? Yes, the last ~10 files of the output where added to the exclusion list. the terminal output summary:parity_block_count:22830267 summary:disk_block_count:d1:22148953 summary:disk_block_allocated:d1:22148953 summary:disk_block_count:d2:22134316 summary:disk_block_allocated:d2:22407482 summary:disk_block_count:d3:19642719 summary:disk_block_allocated:d3:22830267 summary:disk_block_count:d4:3042703 summary:disk_block_allocated:d4:3277065...