This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: mt and tar fail on LTO-5 drives
- From: bartels <bartels at mailme dot ath dot cx>
- To: cygwin at cygwin dot com
- Date: Mon, 19 Aug 2013 21:10:55 +0200
- Subject: Re: mt and tar fail on LTO-5 drives
- References: <520FC274 dot 3040001 at mailme dot ath dot cx> <20130819101917 dot GC18757 at calimero dot vinschen dot de> <52124601 dot 5000409 at mailme dot ath dot cx> <20130819171203 dot GC31248 at calimero dot vinschen dot de>
On 08/19/2013 07:12 PM, Corinna Vinschen wrote:
It would be interesting to see the OS error codes. If you run tar under
strace, the trace output should contain a line like
[...] write: Win32 error XXXX
or
[...] close: Win32 error XXXX
The value of XXXX is what I'm curious about.
Here is the error:
15692 21364024 [main] tar 5700 mtinfo_drive::error: write: Win32 error 1100
I suppose there is nothing for cygwin to do, other
than adding some items to the 'density' list:
{0x44, "Ultrium LTO-3"},
mt already knows LTO-3 and 4.
Which version is that? I have mt V2.3.2 and do not see it in the code.
- Bartels
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple