Shift Summary:
Total duty cycle were 47%, 36% and 16% for three days respectively.
Mostly locks were broken due to earthquakes/ increased ground motion or saturation of different parts (like ITMX, PRM etc)
Other than some non-stationarity at low frequency, spectrogram looked clean. Most of the high SNR glitches were noticed below 300Hz
In general high SNR glitch rate was low, but increased due to seismic activity and ETMY saturation
60Hz magnetic periodic glitches are still present with SNR <15, 50Hz glitches are noticed ( alog)
Still loud glitches due to ETMY saturation are the main problem for LHO
Most of the loud events are vetoed out successfully by Hveto
Glitches caused by earthquake showed up as a very loud event (with new SNR 8.5) in BBH search on 7th September. 


Some follow up studies of the Loud glitches: It is suspected that the load glitches might be caused by the ETMY saturation or may be because of some other reason. I scanned few randomly chosen loud glitches.
 Few omega scans can be found here:
https://ldas-jobs.ligo-wa.caltech.edu/~nairwita/wdq/H1_1124466556.481/
https://ldas-jobs.ligo-wa.caltech.edu/~nairwita/wdq/H1_1124467378.953/
https://ldas-jobs.ligo-wa.caltech.edu/~nairwita/wdq/H1_1125200626.78/
https://ldas-jobs.ligo-wa.caltech.edu/~nairwita/wdq/H1_1125622097.394/

I did see the glitches in ASC_Y_TR_{A/B} channels. But not always before DARM glitches. I am mentioning these particular channels as during ER7 dust glitches were observed in these channels too.

But I have scanned all the times given in the alog by Stefan  and could not find the same pattern. 

https://ldas-jobs.ligo-wa.caltech.edu/~nairwita/wdq/H1_1126294545/
https://ldas-jobs.ligo-wa.caltech.edu/~nairwita/wdq/H1_1126434798/
https://ldas-jobs.ligo-wa.caltech.edu/~nairwita/wdq/H1_1126437892/
https://ldas-jobs.ligo-wa.caltech.edu/~nairwita/wdq/H1_1126441165/
https://ldas-jobs.ligo-wa.caltech.edu/~nairwita/wdq/H1_1126442379/

I also ran the modified Lockloss tool with the help of Nutsinee using default channel list and did not find any significant channel (other than SUS-ETMY_L3_MASTER_OUT) except the glitch happened at 1126437892. I have attached the lock loss plot for this particular loud glitch and the significant channels came out as the result of modified lockloss script are as given below (the numbers in the second column show the seconds after those channels had loud glitches):

H1:ASC-OMC_B_YAW_OUT_DQ	        0.000	
H1:ASC-OMC_B_SUM_OUT_DQ	        0.000	
H1:ASC-OMC_B_PIT_OUT_DQ	        0.000	
H1:ASC-OMC_A_YAW_OUT_DQ	        0.000	
H1:ASC-OMC_A_SUM_OUT_DQ	        0.000	
H1:SUS-ETMY_L3_MASTER_OUT_LR_DQ	0.001	
H1:SUS-ETMY_L3_MASTER_OUT_LL_DQ	0.001	
H1:SUS-ETMY_L3_MASTER_OUT_UL_DQ	0.001	
H1:ASC-OMC_A_PIT_OUT_DQ	        0.001	
H1:ASC-AS_B_RF36_Q_YAW_OUT_DQ	0.001	
H1:ASC-AS_A_DC_PIT_OUT_DQ	0.001	
H1:SUS-ETMY_L3_MASTER_OUT_UR_DQ	0.001	
H1:ASC-AS_A_DC_SUM_OUT_DQ	0.001	
H1:ASC-AS_A_RF45_Q_YAW_OUT_DQ	0.001	
H1:ASC-AS_A_RF45_Q_PIT_OUT_DQ	0.001	
H1:ASC-AS_A_RF45_I_PIT_OUT_DQ	0.001	
H1:ASC-AS_A_RF36_Q_PIT_OUT_DQ	0.001	
H1:ASC-AS_B_RF36_I_YAW_OUT_DQ	0.001	
H1:ASC-AS_B_DC_SUM_OUT_DQ	0.001	
H1:ASC-AS_A_RF45_I_YAW_OUT_DQ	0.001	
H1:ASC-AS_A_RF36_I_YAW_OUT_DQ	0.001	
H1:SUS-ITMY_L3_LOCK_P_OUT_DQ	0.004	
H1:SUS-ITMY_L3_LOCK_P_IN1_DQ	0.004	
H1:SUS-ITMY_L2_LOCK_P_OUT_DQ	0.004	
H1:SUS-ITMY_L2_LOCK_P_IN1_DQ	0.004	
H1:SUS-ITMX_L3_LOCK_P_IN1_DQ	0.004	
H1:SUS-ITMX_L3_LOCK_P_OUT_DQ	0.004	
H1:SUS-ITMX_L2_LOCK_P_OUT_DQ	0.004	
H1:SUS-ITMX_L2_LOCK_P_IN1_DQ	0.004	
H1:SUS-ITMY_L1_LOCK_P_IN1_DQ	0.007	
H1:SUS-ITMY_L1_LOCK_P_OUT_DQ	0.007	
H1:SUS-ITMX_L1_LOCK_P_OUT_DQ	0.007	
H1:SUS-ITMX_L1_LOCK_P_IN1_DQ	0.007	
H1:ASC-DHARD_P_OUT_DQ	        0.009	
H1:SUS-ITMY_M0_LOCK_P_IN1_DQ	0.011	
H1:SUS-ITMX_M0_LOCK_P_IN1_DQ	0.011	
H1:ASC-DHARD_Y_OUT_DQ           0.140

For all those five times (given in alog 21522) SUS-ETMY_L3_MASTER_OUT had glitches 0.001s after DARM had the loud glitch.(-0.001s before as written in the plot title- Thanks to Hang for noticing this).

In conclusion, it is still not clear to me if ETMY saturation is the reason behind these loud glitches or not.