rsync: [generator] failed to set permissions on "/media/ziomario/isoarm/aosp/vendor-rw/bin/expand": Operation not supported (95)

Bug #1919186 reported by Marietto
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rsync (Ubuntu)
New
Undecided
Unassigned

Bug Description

Hello.

I'm trying to create an AOSP image that I want to virtualize on the Nvidia Jetson Nano with qemu-kvm. To to this,I have tried to clone the repo from this page :

https://github.com/antmicro/kvm-aosp-jetson-nano

According with the tutorial,these are the commands that I have issued before to get the error :

root@ziomario-Z390-AORUS-PRO:/media/ziomario/isoarm/aosp# make clean
20:05:41 Entire build directory removed.

root@ziomario-Z390-AORUS-PRO:/media/ziomario/isoarm/aosp# source build/envsetup.sh

root@ziomario-Z390-AORUS-PRO:/media/ziomario/isoarm/aosp# lunch aosp_arm64-eng

[W][2021-03-13T20:07:13+0100][8990] void cmdline::logParams(nsjconf_t *)():250 Process will be UID/EUID=0 in the global user namespace, and will have user root-level access to files
[W][2021-03-13T20:07:13+0100][8990] void cmdline::logParams(nsjconf_t *)():260 Process will be GID/EGID=0 in the global user namespace, and will have group root-level access to files

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=10
TARGET_PRODUCT=aosp_arm64
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv8-a
TARGET_2ND_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.8.0-44-generic-x86_64-Ubuntu-20.10
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200605.002.A1
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=external/mesa3d
============================================

....................

[ 99% 108863/109867] R8: out/target/common/obj/APPS/Shell_intermediates/dex/classes.dex
Warning: Library class android.os.BugreportManager$DumpstateListener extends program class android.os.IDumpstateListener$Stub
Warning: Library class android.os.BugreportManager$DumpstateListener extends program class android.os.IDumpstateListener$Stub
[ 99% 109639/109867] //frameworks/base/packages/SystemUI:SystemUI-core kotlinc [common]
frameworks/base/packages/SystemUI/src/com/android/systemui/statusbar/PulseExpansionHandler.kt:121:38: warning: 'get(Class<T!>!): T!' is deprecated. Deprecated in Java
        mFalsingManager = Dependency.get(FalsingManager::class.java)
                                     ^
[ 99% 109808/109867] Target Java: out/target/common/obj/APPS/Dialer_intermediates/classes-full-debug.jar
Note: Generating a Provider for com.android.dialer.glidephotomanager.impl.GlidePhotoManagerImpl. Prefer to run the dagger processor over that class instead.
Note: [1] Wrote GeneratedAppGlideModule with: []
[ 99% 109824/109867] //art/build/apex:art-check-debug-apex-gen generate art-check-debug-apex-gen.dummy
--bitness=auto, trying to autodetect. This may be incorrect!
  Detected multilib
[ 99% 109863/109867] build check-all-partition-sizes
The sum of sizes of [system vendor] is within BOARD_SUPER_PARTITION_SIZE:
1314865152+34615296 == 1349480448 <= 3229614080 == 3229614080
The sum of sizes of [system vendor] is within BOARD_EMULATOR_DYNAMIC_PARTITIONS_SIZE:
1314865152+34615296 == 1349480448 <= 3221225472 == 3221225472
The sum of sizes of [emulator_dynamic_partitions] is within BOARD_SUPER_PARTITION_SIZE:
3221225472 == 3221225472 <= 3229614080 == 3229614080
[ 99% 109864/109867] Creating out/target/product/generic_arm64/VerifiedBootParams.textproto
digest is bf855b60e10e311542852c09bdf3bbdf2f343a66c133c6bf15c2e1463abde60d
output is Algorithm: SHA256_RSA4096
"Algorithm: SHA256_RSA4096"
hash algorithm is sha256
vbmeta size 4352
[ 99% 109865/109867] Target super fs image for debug: out/target/product/generic_arm64/super.img
2021-03-13 22:17:20 - build_super_image.py - INFO : Building super image from info dict...
2021-03-13 22:17:20 - common.py - INFO : Running: "lpmake --metadata-size 65536 --super-name super --metadata-slots 2 --device super:3229614080 --group emulator_dynamic_partitions:3221225472 --partition system:readonly:1314865152:emulator_dynamic_partitions --image system=out/target/product/generic_arm64/system.img --partition vendor:readonly:34615296:emulator_dynamic_partitions --image vendor=out/target/product/generic_arm64/vendor.img --output out/target/product/generic_arm64/super.img"
2021-03-13 22:17:21 - common.py - INFO : lpmake I 03-13 22:17:20 585863 585863 builder.cpp:937] [liblp]Partition system will resize from 0 bytes to 1314865152 bytes
lpmake I 03-13 22:17:20 585863 585863 builder.cpp:937] [liblp]Partition vendor will resize from 0 bytes to 34615296 bytes
Invalid sparse file format at header magic
Invalid sparse file format at header magic
2021-03-13 22:17:21 - build_super_image.py - INFO : Done writing image out/target/product/generic_arm64/super.img
[100% 109867/109867] Create system-qemu.img now
1+0 records in
2048+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.00183724 s, 571 MB/s
0+1 records in
1+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.000774785 s, 1.4 GB/s
3080+0 records in
3080+0 records out
3229614080 bytes (3.2 GB, 3.0 GiB) copied, 23.0579 s, 140 MB/s
1+0 records in
1+0 records out
1048576 bytes (1.0 MB, 1.0 MiB) copied, 0.000521017 s, 2.0 GB/s
Creating new GPT entries.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
Setting name!
partNum is 0
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
Setting name!
partNum is 1
REALLY setting name!
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot.
The operation has completed successfully.
out/host/linux-x86/bin/sgdisk --clear out/target/product/generic_arm64/system-qemu.img
[W][2021-03-13T20:13:12+0100][19132] void cmdline::logParams(nsjconf_t *)():250 Process will be UID/EUID=0 in the global user namespace, and will have user root-level access to files
[W][2021-03-13T20:13:12+0100][19132] void cmdline::logParams(nsjconf_t *)():260 Process will be GID/EGID=0 in the global user namespace, and will have group root-level access to files

#### build completed successfully (02:06:56 (hh:mm:ss)) ####

going forward with the commands,this is what happened :

root@ziomario-Z390-AORUS-PRO:/media/ziomario/isoarm/aosp# sudo mount system-rw.img
system-rw

root@ziomario-Z390-AORUS-PRO:/media/ziomario/isoarm/aosp# sudo mount out/target/product/generic_arm64/system.img system-ro -o ro

you can see the error reported by this command :

root@ziomario-Z390-AORUS-PRO:/media/ziomario/isoarm/aosp# sudo rsync -avxHAX system-r{o,w}/
sending incremental file list

here :

https://pastebin.com/1XydcaM4

and you can see the error reported by this command :

rsync -avxHAX vendor-r{o,w}/

here :

https://pastebin.com/HkTJnaNE

Marietto (marietto2008)
description: updated
description: updated
summary: - rsync: [generator] failed to set permissions : Operation not supported
- (95)
+ remove me.
Revision history for this message
Marietto (marietto2008) wrote :

this is not a bug. It was a file permission problem.

description: updated
summary: - remove me.
+ rsync: [generator] failed to set permissions on
+ "/media/ziomario/isoarm/aosp/vendor-rw/bin/expand": Operation not
+ supported (95)
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

IIRC the discussions that happened on this topic already asked for the target file system.
I see you mount the image there
  root@ziomario-Z390-AORUS-PRO:/media/ziomario/isoarm/aosp# sudo mount system-rw.img system-rw

ut fromt he log it is unclear what Filesystem that is, and the rsync command asks it to retain ownership/permissions which some filesystems can't store.

Hence after mounting your image, could you check as what this is effectively mounted?
Maybe for a start just post:
 $ mount | grep system

Once you know that you very likely will be able to break it down to a much simpler case.
For example take "one file" with "this set of ownership/permissions" and copy it from "e.g. ext4" to an image that is "unknown filesystem".
Which would be much much easier than having everyone try to setup aosp and such.

Revision history for this message
Marietto (marietto2008) wrote :

luckily copying the repo in my desktop instead of a different disk make disappeared the rsync errors.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.