#7646: resource busy (file is locked) with multi-threaded file ops ----------------------------------------+----------------------------------- Reporter: StefanWehr | Owner: Type: bug | Status: new Priority: normal | Component: Runtime System Version: 7.6.2 | Keywords: Os: Unknown/Multiple | Architecture: Unknown/Multiple Failure: Incorrect result at runtime | Blockedby: Blocking: | Related: ----------------------------------------+----------------------------------- Changes (by dleuschner): * version: 7.6.1 => 7.6.2 Comment: Thank you for looking into this issue, Carter! I assume it might affect more users than we might think, because the error message is typically associated with the lazy-IO problem of first (incompletely) reading and then writing. For me it still doesn't work with appendFile. The output still is: {{{ $ ghc -threaded -rtsopts --make GhcBug.hs && ./GhcBug +RTS -N2 started worker 3 started worker 2 started worker 5 started worker 7 started worker 9 started worker 1 started worker 4 started worker 6 started worker 8 started worker 10 GhcBug: ERROR in worker 1: 1: openBinaryFile: resource busy (file is locked) ERROR in worker 1: 1: openBinaryFile: resource busy (file is locked) }}} -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/7646#comment:3 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler