Check that lseek(2) succeeds and puts us where we expect. [1]

While we're here, fix a long-standing bug in the handling of write(2)
errors: The API changed from "return # of bytes written" to "return
status code" almost 4 years ago, so instead of returning (-1) we need
to return ARCHIVE_FATAL.

Found by: Coverity Prevent [1]