Re: beefy15 and beefy21 builds stuck in fetch/runaway for electron35, each after failed umount for Device Busy

Reply: Tatsuki Makino : "Re: beefy15 and beefy21 builds stuck in fetch/runaway for electron35, each after failed umount for Device Busy"
In reply to: Mark Millard : "beefy15 and beefy21 builds stuck in fetch/runaway for electron35, each after failed umount for Device Busy"
Go to: [ bottom of page ] [ top of archives ] [ this month ]

From: Mark Millard <marklmi_at_yahoo.com>
Date: Sun, 10 Aug 2025 14:16:34 UTC

On Aug 10, 2025, at 07:09, Mark Millard <marklmi@yahoo.com> wrote:

> This is despite showing Remaining as: 0
> 
> 
> FYI:
> 
> 
> ===>  Cleaning for electron35-35.7.2_1
> umount: unmount of /usr/local/poudriere/data/.m/135i386-default/12/wrkdirs failed: Device busy
> 
> (34:09:54+)

For reference:

https://pkg-status.freebsd.org/beefy15/build.html?mastername=135i386-default&build=d4c2b214226f



> ===>  Cleaning for electron35-35.7.2_1
> umount: unmount of /usr/local/poudriere/data/.m/142i386-default/39/wrkdirs failed: Device busy
> 
> (70:15:15+)

For reference:

https://pkg-status.freebsd.org/beefy21/build.html?mastername=142i386-default&build=d4c2b214226f



> Side note for personal bulk -Ca port-package builds with poudriere-devel:
> 
> I see these sorts umount failures for builds of
> lang/dotnet (e.g., 9.0.6) ( but not lang/dotnet8 ).
> Also: gatk.


===
Mark Millard
marklmi at yahoo.com