No persistant harm, and fixed in 7.0.2.9 and 7.1.0.3  from the 7.0 MR  and 7.1 MR release notes:  During read operations, locks were sometimes acquired out of order, preventing other necessary locks from being acquired. When locks were acquired out of order, the operation was immediately restarted and the necessary locks were successfully acquired, however, DSR failures similar to the following were logged for the initial failure:  
We received a DSR failure on one of Isilon Node  DSR failure on { 5,34,4454400:512 } of dinode:{ 1,17,528338944:512, 2,36,541905920:512, 3,33,210654720:512, 5,34,4454400:512 } owned by 1:1090:7b3f::HEAD: write failed: ENEEDLOCK  Please suggest if there any resolution needs to be performed ?  Thanks,
DSR failure on Isilon Node