Slow hardware: pkg: Fail to truncate file: /⋯/.pkgtmp.⋯:Operation timed out

With slow hardware

Timeouts occurred whilst pkg extracted three packages:

  • subversion
  • libreoffice
  • git-gui

Uncertain whether this type of failure is negligible (the word error did not appear), I chose to repeat the upgrade for all three:

nomad@NomadBSD:~% sudo pkg upgrade -f subversion libreoffice git-gui
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 3 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:

version-1.14.1

Number of packages to be reinstalled: 3

119 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/3] Fetching subversion-1.14.1.txz: 100%    3 MiB 832.8kB/s    00:04    
[2/3] Fetching libreoffice-7.1.0.3.txz: 100%  110 MiB 941.8kB/s    02:03    
[3/3] Fetching git-gui-2.30.1.txz: 100%    5 MiB 939.9kB/s    00:06    
Checking integrity... done (0 conflicting)
[1/3] Reinstalling subversion-1.14.1...
[1/3] Extracting subversion-1.14.1: 100%
[2/3] Reinstalling libreoffice-7.1.0.3...
[2/3] Extracting libreoffice-7.1.0.3:   2%
pkg: Fail to truncate file: /usr/local/lib/libreoffice/help/en-US/.pkgtemp.swriter.tree.u3JPUusy4iqF:Operation timed out
[2/3] Extracting libreoffice-7.1.0.3: 100%
[3/3] Reinstalling git-gui-2.30.1...
===> Creating groups.
Using existing group 'git_daemon'.
===> Creating users
Using existing user 'git_daemon'.
[3/3] Extracting git-gui-2.30.1: 100%
You may need to manually remove /usr/local/etc/git/gitweb.conf if it is no longer needed.
nomad@NomadBSD:~% 
  • a timeout occurred with only one of the three.

When a failure such as this occurs, can I treat it as negligible?

This drive is ludicrously slow. The only one that was available to me when I last installed NomadBSD (I might find one that’s faster, but not immediately) …

Hi @grahamperrin,

errors like these can occur on slow devices, but they are usually nothing to be concerned about.

1 Like

Thanks for the advice.


For completeness: during system shut down, I noticed CAM-related errors.

So, after restarting, I began tailing /var/log/messages in one tab then retried the upgrade in another tab:

nomad@NomadBSD:~% sudo pkg upgrade -f libreoffice
Password:
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
The following 3 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
	compat5x-amd64: 5.4.0.8.1_1
	localedata: 5.4_2

Installed packages to be REINSTALLED:
	libreoffice-7.1.0.3

Number of packages to be installed: 2
Number of packages to be reinstalled: 1

The process will require 17 MiB more space.
114 MiB to be downloaded.

Proceed with this action? [y/N]: y
[1/3] Fetching libreoffice-7.1.0.3.txz: 100%  110 MiB 941.8kB/s    02:03    
[2/3] Fetching compat5x-amd64-5.4.0.8.1_1.txz: 100%    4 MiB   1.0MB/s    00:04    
[3/3] Fetching localedata-5.4_2.txz: 100%   59 KiB  60.0kB/s    00:01    
Checking integrity... done (0 conflicting)
[1/3] Installing localedata-5.4_2...
[1/3] Extracting localedata-5.4_2: 100%
[2/3] Reinstalling libreoffice-7.1.0.3...
[2/3] Extracting libreoffice-7.1.0.3:  63%
pkg: Fail to create temporary file: /usr/local/lib/libreoffice/share/config/soffice.cfg/modules/swriter/ui/.pkgtemp.notebookbar_groupedbar_compact.ui.Oz0ftxvdGnm4:File exists
[2/3] Extracting libreoffice-7.1.0.3: 100%
^C
nomad@NomadBSD:~% 
  • not a failure to truncate
  • failure to create temporary file (file exists)

When I switched to the other tab I found the lines below, the error probably coinciding with the failure above:

nomad@NomadBSD:~% tail -f /var/log/messages
…
Feb 14 07:50:52 NomadBSD pkg[2419]: localedata-5.4_2 installed
Feb 14 08:41:50 NomadBSD kernel: (da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 97 06 f8 00 00 18 00 
Feb 14 08:41:50 NomadBSD kernel: (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
Feb 14 08:41:50 NomadBSD kernel: (da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain
Feb 14 09:15:43 NomadBSD kernel: re0: link state changed to DOWN
…

A handful of lines from https://bsd-hardware.info/?probe=a5ab7068dc&log=lsusb:

idProduct          0x0302 Flash Drive
bcdDevice            2.00
iManufacturer           1 Verbatim
iProduct                2 STORE N GO

I imagine that a change to a sysctl might help, however it will be saner to begin using a better drive.