CubieBoard中文论坛

 找回密码
 立即注册
搜索
热搜: unable
查看: 8031|回复: 0

关于使用mk_ext4_rootfs.sh生产文件系统镜像文件报错

[复制链接]
发表于 2014-9-19 23:04:06 | 显示全部楼层 |阅读模式
本帖最后由 2549373113 于 2014-9-19 23:06 编辑

我使用https://github.com/cubieboard/sunxi-bsp,下的mk_ext4_rootfs.sh脚本将制作好的文件系统压缩包转好为rootfs.ext4文件,
执行:
./mk_ext4_rootfs.sh xxx.tar.gz  cubie-core.ext4
报错,这个是怎么回事?看了半天,没搞懂

/home/cubie# ./mk_ext4_rootfs.sh  rootfs.tar.gz cubie-core.ext4

Make rootfs
Make linux.ext4 (size=745)
745+0 records in
745+0 records out
781189120 bytes (781 MB) copied, 16.146 s, 48.4 MB/s
mke2fs 1.42 (29-Nov-2011)
linux.ext4 is not a block special device.
Proceed anyway? (y,n) y
Discarding device blocks: done                           
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
47712 inodes, 190720 blocks
9536 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=197132288
6 block groups
32768 blocks per group, 32768 fragments per group
7952 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840

Allocating group tables: done                           
Writing inode tables: done                           
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

umount: /home/cubie/target_tmp: not mounted
Unpacking /home/cubie/rootfs.tar.gz
tar: proc: implausibly old time stamp 1970-01-01 08:00:00
tar: var/spool/exim4/msglog: time stamp 2019-06-04 22:22:04 is 148525328.296931622 s in the future
tar: var/spool/exim4/input: time stamp 2019-06-04 22:22:04 is 148525328.296717465 s in the future
tar: var/spool/cron/atjobs: time stamp 2019-06-04 22:22:04 is 148525328.296511829 s in the future
tar: var/mail/mail: time stamp 2019-06-04 22:22:04 is 148525328.296164889 s in the future
tar: var/mail: time stamp 2019-06-04 22:22:04 is 148525328.296057505 s in the future
tar: var/log/exim4/mainlog: time stamp 2019-06-04 22:22:04 is 148525328.29588014 s in the future
mv: `/home/cubie/target_tmp/bin' and `/home/cubie/target_tmp/bin' are the same file
mv: `/home/cubie/target_tmp/boot' and `/home/cubie/target_tmp/boot' are the same file
mv: `/home/cubie/target_tmp/dev' and `/home/cubie/target_tmp/dev' are the same file
mv: `/home/cubie/target_tmp/etc' and `/home/cubie/target_tmp/etc' are the same file
mv: `/home/cubie/target_tmp/home' and `/home/cubie/target_tmp/home' are the same file
mv: `/home/cubie/target_tmp/lib' and `/home/cubie/target_tmp/lib' are the same file
mv: `/home/cubie/target_tmp/lost+found' and `/home/cubie/target_tmp/lost+found' are the same file
mv: `/home/cubie/target_tmp/media' and `/home/cubie/target_tmp/media' are the same file
mv: `/home/cubie/target_tmp/mnt' and `/home/cubie/target_tmp/mnt' are the same file
mv: `/home/cubie/target_tmp/opt' and `/home/cubie/target_tmp/opt' are the same file
mv: `/home/cubie/target_tmp/proc' and `/home/cubie/target_tmp/proc' are the same file
mv: `/home/cubie/target_tmp/root' and `/home/cubie/target_tmp/root' are the same file
mv: `/home/cubie/target_tmp/run' and `/home/cubie/target_tmp/run' are the same file
mv: `/home/cubie/target_tmp/sbin' and `/home/cubie/target_tmp/sbin' are the same file
mv: `/home/cubie/target_tmp/selinux' and `/home/cubie/target_tmp/selinux' are the same file
mv: `/home/cubie/target_tmp/srv' and `/home/cubie/target_tmp/srv' are the same file
mv: `/home/cubie/target_tmp/sys' and `/home/cubie/target_tmp/sys' are the same file
mv: `/home/cubie/target_tmp/tmp' and `/home/cubie/target_tmp/tmp' are the same file
mv: `/home/cubie/target_tmp/usr' and `/home/cubie/target_tmp/usr' are the same file
mv: `/home/cubie/target_tmp/var' and `/home/cubie/target_tmp/var' are the same file
Failed to copy rootfs data

回复

使用道具 举报

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

QQ|Archiver|手机版|粤ICP备13051116号|cubie.cc---深刻的嵌入式技术讨论社区

GMT+8, 2024-11-26 00:12 , Processed in 0.020877 second(s), 16 queries .

Powered by Discuz! X3.4

© 2001-2012 Comsenz Inc. | Style by Coxxs

返回顶部