Bug 14514

Summary:	sstate_cache: files in wrong dir
Product:	[Infrastructure] Infrastructure General	Reporter:	Frans Meulenbroeks <fransmeulenbroeks>
Component:	infrastructure-general	Assignee:	Michael Halstead <mhalstead>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Undecided
Version:	unspecified
Target Milestone:	---
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Frans Meulenbroeks 2021-08-17 10:28:50 UTC

While inspecting our sstate-cache I found that of the roughly 100.000 siginfo files I had, two were present in two different directories.

This one is good:
-rwxrwxrwx 2 1000 pokyuser 152515 Aug 10 06:49 sstate-cache/e3/8e/sstate:packagegroup-core-boot:jetson_xavier_nx_devkit_emmc-sorama-linux:1.0:r17:jetson_xavier_nx_devkit_emmc:3:e38e75d208a25e2ab119169477b01a0b7a889532e42853185d6a155e0aeee5c5_package.tgz.siginfo

But the same file ended up in the f9/fc folder which is obviously wrong as the two dirs are based upon the first 4 chars of the hash 
-rwxrwxrwx 1 1000 pokyuser 152515 Aug 10 06:47 sstate-cache/f9/fc/sstate:packagegroup-core-boot:jetson_xavier_nx_devkit_emmc-sorama-linux:1.0:r17:jetson_xavier_nx_devkit_emmc:3:e38e75d208a25e2ab119169477b01a0b7a889532e42853185d6a155e0aeee5c5_package.tgz.siginfo

This one is wrong
-rwxrwxrwx 2 1000 pokyuser 1963 Jul 28 09:25 sstate-cache/a0/be/sstate:soramawebinterface-l642vx::1.0+gitAUTOINC+d1d4664093:r0::3:e4976edcbecd740ebf0d35355641d29600328bec5a569d4ef7546ff282a4fe24_fetch.tgz.siginfo

and this one is as expected
-rwxrwxrwx 1 1000 pokyuser 1963 Jul 28 06:34 sstate-cache/e4/97/sstate:soramawebinterface-l642vx::1.0+gitAUTOINC+d1d4664093:r0::3:e4976edcbecd740ebf0d35355641d29600328bec5a569d4ef7546ff282a4fe24_fetch.tgz.siginfo

it might be that there are more files in a wrong dir

I have no idea what could have caused this to happen. Maybe parallelism caused interference/overwriting of a var.

Comment 1 Frans Meulenbroeks 2021-08-17 10:54:38 UTC

accidentally entered this one twice

*** This bug has been marked as a duplicate of bug 1411 ***

Comment 2 Frans Meulenbroeks 2021-08-17 10:55:45 UTC

oops mistyped number of duplicate

*** This bug has been marked as a duplicate of bug 14511 ***