"17:29:44 ERROR [SystemUtil:pool-10-thread-4] com.eucalyptus.util.ExecutionException: ///usr/lib/eucalyptus/euca_rootwrap losetup /dev/loop151 error: loop: can't get info on device /dev/loop151: No such device or address
com.eucalyptus.util.ExecutionException: ///usr/lib/eucalyptus/euca_rootwrap losetup /dev/loop151 error: loop: can't get info on device /dev/loop151: No such device or address"
Carlos that error is actually not a real "error," it is unfortunately tagged as such when logging. The Storage Controller is trying to make sure that the loop device exists before trying to use it or remove it, basically the equivalent of a "stat." We can fix the way this is being reported, but it is not critical.
"17:29:44 ERROR [SystemUtil: pool-10- thread- 4] com.eucalyptus. util.ExecutionE xception: ///usr/ lib/eucalyptus/ euca_rootwrap losetup /dev/loop151 error: loop: can't get info on device /dev/loop151: No such device or address util.ExecutionE xception: ///usr/ lib/eucalyptus/ euca_rootwrap losetup /dev/loop151 error: loop: can't get info on device /dev/loop151: No such device or address"
com.eucalyptus.
Carlos that error is actually not a real "error," it is unfortunately tagged as such when logging. The Storage Controller is trying to make sure that the loop device exists before trying to use it or remove it, basically the equivalent of a "stat." We can fix the way this is being reported, but it is not critical.