root@Z390-AORUS-PRO:/home/ziomario/Scrivania/antmicro/aosp_images# tune2fs
-l /home/ziomario/Scrivania/antmicro/aosp_images/system-rw.img
tune2fs 1.45.6 (20-Mar-2020)
Filesystem volume name: /
Last mounted on:
/home/ziomario/Scrivania/antmicro/aosp_images/system-rw
Filesystem UUID: b7ee4a86-92bc-4530-a645-7e825127fb90
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype needs_recovery extent 64bit flex_bg sparse_super large_file
huge_file dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 196608
Block count: 786432
Reserved block count: 39321
Free blocks: 755396
Free inodes: 196597
First block: 0
Block size: 4096
Fragment size: 4096
Group descriptor size: 64
Reserved GDT blocks: 383
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Tue Apr 6 14:18:55 2021
Last mount time: Tue Apr 6 14:19:15 2021
Last write time: Tue Apr 6 14:19:15 2021
Mount count: 1
Maximum mount count: -1
Last checked: Tue Apr 6 14:18:55 2021
Check interval: 0 (<none>)
Lifetime writes: 1733 kB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: be3ec3f4-13ef-48f7-87bd-0b6e50e80127
Journal backup: inode blocks
Il giorno mar 6 apr 2021 alle ore 16:34 Mario Marietto <
marietto2...@gmail.com> ha scritto:
> root@Z390-AORUS-PRO:/home/ziomario/Scrivania/antmicro/aosp_images#
> tune2fs -l /dev/sda1
>
> tune2fs 1.45.6 (20-Mar-2020)
> Filesystem volume name: <none>
> Last mounted on: /
> Filesystem UUID: 84d024e0-c8c7-42c0-ad3e-c3e0c1cacdb7
> Filesystem magic number: 0xEF53
> Filesystem revision #: 1 (dynamic)
> Filesystem features: has_journal ext_attr resize_inode dir_index
> filetype needs_recovery extent 64bit flex_bg sparse_super large_file
> huge_file dir_nlink extra_isize m
> etadata_csum
> Filesystem flags: signed_directory_hash
> Default mount options: user_xattr acl
> Filesystem state: clean
> Errors behavior: Continue
> Filesystem OS type: Linux
> Inode count: 30531584
> Block count: 122095703
> Reserved block count: 6104784
> Free blocks: 16457913
> Free inodes: 27534246
> First block: 0
> Block size: 4096
> Fragment size: 4096
> Group descriptor size: 64
> Reserved GDT blocks: 1024
> Blocks per group: 32768
> Fragments per group: 32768
> Inodes per group: 8192
> Inode blocks per group: 512
> Flex block group size: 16
> Filesystem created: Mon Aug 3 22:23:38 2020
> Last mount time: Tue Apr 6 10:46:45 2021
> Last write time: Tue Apr 6 10:46:44 2021
> Mount count: 173
> Maximum mount count: -1
> Last checked: Sun Feb 28 12:33:46 2021
> Check interval: 0 (<none>)
> Lifetime writes: 34 TB
> Reserved blocks uid: 0 (user root)
> Reserved blocks gid: 0 (group root)
> First inode: 11
> Inode size: 256
> Required extra isize: 32
> Desired extra isize: 32
> Journal inode: 8
> First orphan inode: 22414454
> Default directory hash: half_md4
> Directory Hash Seed: 3ff09b4a-bf6b-41ac-844d-310aebf87fbf
> Journal backup: inode blocks
> Checksum type: crc32c
> Checksum: 0xf4add38b
>
>
>
> Il giorno mar 6 apr 2021 alle ore 16:11 Kevin Korb via rsync <
> rsync@lists.samba.org> ha scritto:
>
>> Those aren't really rsync errors they are just rsync telling you what
>> the kernel told it. The only thing I see wrong in your paste is that
>> you didn't use a trailing / on the source+target. Those do mean
>> something to rsync. The only thing I see wrong in the instructions is
>> the use of dd to make a file of a specific size. The truncate command
>> does that much better.
>>
>> Anyway, check the mount options on the file system (use the mount
>> command it will show them) and the options on the filesystem itself with
>> tune2fs -l. My guess is that either ACLs or XATTRs are not enabled and
>> they probably are in use since the instructions told you to tell rsync
>> to copy those. You can also try running rsync without the -A and -X to
>> confirm.
>>
>> On 4/6/21 9:50 AM, Mario Marietto via rsync wrote:
>> > Hello.
>> >
>> > I want to virtualize correctly Android 10 on top of my Jetson nano
>> > (arm64) using qemu and kvm on ubuntu 18.04. This is the tutorial that
>> > I'm following :
>> >
>> > https://github.com/antmicro/kvm-aosp-jetson-nano
>> > <https://github.com/antmicro/kvm-aosp-jetson-nano>
>> >
>> > everything went good until this command :
>> >
>> > |sudo rsync -avxHAX system-r{o,w}/
>> >
>> > |
>> >
>> > |something is not good because I get a lot of errors when I transfer the
>> > files and permissions from the source to the destination path (both are
>> > on the same disk and on the same ext4 partition. You can see the full
>> > log with the errors here :
>> >
>> > |
>> >
>> > https://pastebin.ubuntu.com/p/W9GjPCt8G4/
>> > <https://pastebin.ubuntu.com/p/W9GjPCt8G4/>
>> >
>> > the consequence of these errors is that when I try to emulate android
>> > with qemu like this :
>> >
>> > |qemu-system-aarch64 \ -enable-kvm \ -smp 4 \ -m 2048 \ -cpu host \ -M
>> > virt \ -device virtio-gpu-pci \ -device usb-ehci \ -device usb-kbd \
>> > -device virtio-tablet-pci \ -usb \ -serial stdio \ -display sdl,gl=on \
>> > -kernel aosp/Image \ -initrd aosp/ramdisk.img \ -drive
>> > index=0,if=none,id=system,file=aosp/system.img \ -device
>> > virtio-blk-pci,drive=system \ -drive
>> > index=1,if=none,id=vendor,file=aosp/vendor.img \ -device
>> > virtio-blk-pci,drive=vendor \ -drive
>> > index=2,if=none,id=userdata,file=aosp/userdata.img \ -device
>> > virtio-blk-pci,drive=userdata \ -full-screen \ -append
>> > "console=ttyAMA0,38400 earlycon=pl011,0x09000000 drm.debug=0x0 rootwait
>> > rootdelay=5 androidboot.hardware=ranchu androidboot.selinux=permissive
>> > security=selinux selinux=1 androidboot.qemu.hw.mainkeys=0
>> > androidboot.lcd.density=160" |
>> >
>> >
>> > this is the error that I get :
>> >
>> > [ 2.532754] init: init first stage started!
>> > [ 2.535936] init: [libfs_mgr]ReadFstabFromDt(): failed to read fstab
>> > from dt
>> > [ 2.540632] init: [libfs_mgr]ReadDefaultFstab(): failed to find device
>> > default fstab
>> > [ 2.546246] init: Failed to fstab for first stage mount
>> > [ 2.549616] init: Using Android DT directory
>> > /proc/device-tree/firmware/android/
>> > [ 2.555116] init: [libfs_mgr]ReadDefaultFstab(): failed to find device
>> > default fstab
>> > [ 2.560762] init: First stage mount skipped (missing/incompatible/empty
>> > fstab in device tree)
>> > [ 2.566906] init: Skipped setting INIT_AVB_VERSION (not in recovery
>> mode)
>> > [ 2.571227] init: execv("/system/bin/init") failed: No such file or
>> > directory
>> > [ 2.593768] init: #00 pc 00000000000e90a0 /init
>> > [ 2.599958] reboot: Restarting system with command 'bootloader'
>> >
>> > --
>> > Mario.
>> >
>>
>> --
>> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
>> Kevin Korb Phone: (407) 252-6853
>> Systems Administrator Internet:
>> FutureQuest, Inc. ke...@futurequest.net (work)
>> Orlando, Florida k...@sanitarium.net (personal)
>> Web page: https://sanitarium.net/
>> PGP public key available on web site.
>> ~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,
>>
>> --
>> Please use reply-all for most replies to avoid omitting the mailing list.
>> To unsubscribe or change options:
>> https://lists.samba.org/mailman/listinfo/rsync
>> Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
>>
>
>
> --
> Mario.
>
--
Mario.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
