Re: Tar error code
- From: Martin Gregorie <martin@xxxxxxxxxxxxxxxxxxx>
- Date: Sun, 22 Apr 2007 04:05:06 +0100
Nix wrote:
Yes, that's what the documentation says and the absence of any diagnostic info is why I suspected a tar bug.
Failure in write() should cause tar to print info saying how far it
wrote and then abort().
I'm surprised to see tar getting hit with an EPIPE here, though. AreNope. Tar is writing to an absolute pathname based on the USB drive's mount point. So, no pipes involved unless the USB connection magic approximates some sort of pipe.
you writing a archive to stdout and then redirecting it to the
filesystem, or something like that? I'd expect to see EINVAL or EFBIG
or ENOSPC or even ERANGE, but not EPIPE, at least if tar were writing
directly to the FAT fs.
Don't use VFAT, or split your tarballs before 4Gb.No problem. The drive shall be reformatted as ext3 now I know I can do that without breaking anything.
--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |
.
- Follow-Ups:
- Re: Tar error code
- From: Ewan Mac Mahon
- Re: Tar error code
- References:
- Tar error code
- From: Martin Gregorie
- Re: Tar error code
- From: Nix
- Tar error code
- Prev by Date: Re: Radio prog about oss
- Next by Date: Re: Radio prog about oss
- Previous by thread: Re: Tar error code
- Next by thread: Re: Tar error code
- Index(es):
Relevant Pages
|
|