Very long extracting times during upgrade . . . strange?!?

[rfox]

Previous upgrades on same box (N5105) were always relatively snappy - but when I updates from 23.7.1 to 23.7.2 it took an unusually long time extracting various files ?!?

I thought the system hung a few times because it was unusually long . . .

Today, there was a small update from the Sensei package - it got stuck on "Extracting" for about 4 minutes . . . then finally completed - no errors in the logs either:

***GOT REQUEST TO UPDATE***
Currently running OPNsense 23.7.2 at Wed Aug 30 10:17:35 CEST 2023
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
SunnyValley repository is up to date.
All repositories are up to date.
Checking for upgrades (7 candidates): ....... done
Processing candidates (7 candidates): .. done
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
   os-sensei: 1.14.4 -> 1.14.5 [SunnyValley]

Number of packages to be upgraded: 1

The process will require 4 MiB more space.
68 MiB to be downloaded.
[1/1] Fetching os-sensei-1.14.5.pkg: .......... done
Checking integrity... done (0 conflicting)
[1/1] Upgrading os-sensei from 1.14.4 to 1.14.5...
[1/1] Extracting os-sensei-1.14.5: .......

Not sure if anyone else is experiencing this strange issue ?  :-\

[CJ]

Install the smart tools plugin and run a long test on your drive.

[rfox]

Install the smart tools plugin and run a long test on your drive.

Thanks CJ - Unfortunately, I'm running this on Proxmox virtualized  . . . To be quite honest, I have run this instance since 22.1 with constant updates up to 23.7.3 - without this sluggish problem - it has only been apparent from the last update from 23.1.11 to 23.7
So I doubt there is an SSD issue . . . 

[franco]

If the host didn't change we can't rule out a regression in the FreeBSD disk driver in 13.2. But it's pretty hard to pin this down so we would require FreeBSD to publish errata for it... which requires this being noticed and reported upstream... which requires a bug in the disk driver... which is not 100% a safe bet.


Cheers,
Franco

[rfox]

If the host didn't change we can't rule out a regression in the FreeBSD disk driver in 13.2. But it's pretty hard to pin this down so we would require FreeBSD to publish errata for it... which requires this being noticed and reported upstream... which requires a bug in the disk driver... which is not 100% a safe bet.


Cheers,
Franco

Sounds logical - I just wanted to report this and see if anyone else has the same issue - your call! 
Thx, Robert

[franco]

Yeah, this is probably one of the "only time will tell" cases. But I'll keep an eye out for this.


Cheers,
Franco