sam song wrote: =>> Hmmm... It's timeout. How long does the command take? It's a bit weird >> because 36000s but the reported command duration is 136s. How long did >> the command take actually? > > The command did actually take 136minutes25seconds. I set the timeout in app > as 36000seconds(10-hour). Right, 136m. I wonder whether it's hitting some hard timeout limit in the kernel. Hmmmm... Does the attached patch fix your problem? Thanks. -- tejun