Thanks Jussi. That is correct. The external drive was almost full with the data on which the tar was attempted. The internal/mainboard drive had free space.
I'm sorry if I have reported here what might have been more appropriately posted to the discussion boards. It is perhaps of interest to consider how from the user's point of view, the location of the data is distinct from the location of the operation: one considers when using a GUI that the command is being operated from the centre on the peripheral, when in fact the command executes as though from the peripheral on the peripheral. If it were implemented as though the former were true, the compression routine might have more scope to consider using local disc space to complete the operation. Meaningful notifications would make the situation clearer for GUI users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/698147 Title: Tar reported unspecified errors - failed to compress -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
