'ls' or 'ext4ls' misses files on FS
HI!
Did I miss anything myself?
U-Boot: => ext4ls mmc 0:8 /home/root <DIR> 4096 . <DIR> 4096 .. <DIR> 4096 .node_app_slot
Linux: # ls -la /home/root/ total 76 drwxr-xr-x 3 root root 4096 Apr 30 09:27 . drwxr-xr-x 4 root root 4096 Apr 30 09:11 .. -rw------- 1 root root 4188 Apr 30 09:11 .bash_history drwxr-xr-x 2 root root 4096 Mar 8 2016 .node_app_slot -rw------- 1 root root 24 Apr 30 09:27 .python-history -rw------- 1 root root 1250 Apr 29 2016 .viminfo -rw-r--r-- 1 root root 14054 Apr 29 2016 crashlog_00001.tar.gz -rw-r--r-- 1 root root 14022 Apr 29 2016 crashlog_00002.tar.gz -rw-r--r-- 1 root root 13972 Apr 29 2016 crashlog_00003.tar.gz
On Thu, Apr 30, 2020 at 12:34 PM Andy Shevchenko andy.shevchenko@gmail.com wrote:
HI!
Did I miss anything myself?
U-Boot v2020.04
U-Boot: => ext4ls mmc 0:8 /home/root
<DIR> 4096 . <DIR> 4096 .. <DIR> 4096 .node_app_slot
Linux:
(Some v3.10.98 based BSP)
# ls -la /home/root/ total 76 drwxr-xr-x 3 root root 4096 Apr 30 09:27 . drwxr-xr-x 4 root root 4096 Apr 30 09:11 .. -rw------- 1 root root 4188 Apr 30 09:11 .bash_history drwxr-xr-x 2 root root 4096 Mar 8 2016 .node_app_slot -rw------- 1 root root 24 Apr 30 09:27 .python-history -rw------- 1 root root 1250 Apr 29 2016 .viminfo -rw-r--r-- 1 root root 14054 Apr 29 2016 crashlog_00001.tar.gz -rw-r--r-- 1 root root 14022 Apr 29 2016 crashlog_00002.tar.gz -rw-r--r-- 1 root root 13972 Apr 29 2016 crashlog_00003.tar.gz
-- With Best Regards, Andy Shevchenko
On Thu, Apr 30, 2020 at 12:35:20PM +0300, Andy Shevchenko wrote:
On Thu, Apr 30, 2020 at 12:34 PM Andy Shevchenko andy.shevchenko@gmail.com wrote:
HI!
Did I miss anything myself?
U-Boot v2020.04
U-Boot: => ext4ls mmc 0:8 /home/root
<DIR> 4096 . <DIR> 4096 .. <DIR> 4096 .node_app_slot
Linux:
(Some v3.10.98 based BSP)
# ls -la /home/root/ total 76 drwxr-xr-x 3 root root 4096 Apr 30 09:27 . drwxr-xr-x 4 root root 4096 Apr 30 09:11 .. -rw------- 1 root root 4188 Apr 30 09:11 .bash_history drwxr-xr-x 2 root root 4096 Mar 8 2016 .node_app_slot -rw------- 1 root root 24 Apr 30 09:27 .python-history -rw------- 1 root root 1250 Apr 29 2016 .viminfo -rw-r--r-- 1 root root 14054 Apr 29 2016 crashlog_00001.tar.gz -rw-r--r-- 1 root root 14022 Apr 29 2016 crashlog_00002.tar.gz -rw-r--r-- 1 root root 13972 Apr 29 2016 crashlog_00003.tar.gz
Check for what flags are enabled on the filesystem, perhaps there's yet another new ext4 flag that we can't handle and need to have some check for. Thanks!
On Thu, Apr 30, 2020 at 5:13 PM Tom Rini trini@konsulko.com wrote:
On Thu, Apr 30, 2020 at 12:35:20PM +0300, Andy Shevchenko wrote:
On Thu, Apr 30, 2020 at 12:34 PM Andy Shevchenko andy.shevchenko@gmail.com wrote:
HI!
Did I miss anything myself?
U-Boot v2020.04
U-Boot: => ext4ls mmc 0:8 /home/root
<DIR> 4096 . <DIR> 4096 .. <DIR> 4096 .node_app_slot
Linux:
(Some v3.10.98 based BSP)
# ls -la /home/root/ total 76 drwxr-xr-x 3 root root 4096 Apr 30 09:27 . drwxr-xr-x 4 root root 4096 Apr 30 09:11 .. -rw------- 1 root root 4188 Apr 30 09:11 .bash_history drwxr-xr-x 2 root root 4096 Mar 8 2016 .node_app_slot -rw------- 1 root root 24 Apr 30 09:27 .python-history -rw------- 1 root root 1250 Apr 29 2016 .viminfo -rw-r--r-- 1 root root 14054 Apr 29 2016 crashlog_00001.tar.gz -rw-r--r-- 1 root root 14022 Apr 29 2016 crashlog_00002.tar.gz -rw-r--r-- 1 root root 13972 Apr 29 2016 crashlog_00003.tar.gz
Check for what flags are enabled on the filesystem, perhaps there's yet another new ext4 flag that we can't handle and need to have some check for. Thanks!
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg spars e_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: clean
if it's not enough, tell me what should I run?
On Thu, Apr 30, 2020 at 06:11:19PM +0300, Andy Shevchenko wrote:
On Thu, Apr 30, 2020 at 5:13 PM Tom Rini trini@konsulko.com wrote:
On Thu, Apr 30, 2020 at 12:35:20PM +0300, Andy Shevchenko wrote:
On Thu, Apr 30, 2020 at 12:34 PM Andy Shevchenko andy.shevchenko@gmail.com wrote:
HI!
Did I miss anything myself?
U-Boot v2020.04
U-Boot: => ext4ls mmc 0:8 /home/root
<DIR> 4096 . <DIR> 4096 .. <DIR> 4096 .node_app_slot
Linux:
(Some v3.10.98 based BSP)
# ls -la /home/root/ total 76 drwxr-xr-x 3 root root 4096 Apr 30 09:27 . drwxr-xr-x 4 root root 4096 Apr 30 09:11 .. -rw------- 1 root root 4188 Apr 30 09:11 .bash_history drwxr-xr-x 2 root root 4096 Mar 8 2016 .node_app_slot -rw------- 1 root root 24 Apr 30 09:27 .python-history -rw------- 1 root root 1250 Apr 29 2016 .viminfo -rw-r--r-- 1 root root 14054 Apr 29 2016 crashlog_00001.tar.gz -rw-r--r-- 1 root root 14022 Apr 29 2016 crashlog_00002.tar.gz -rw-r--r-- 1 root root 13972 Apr 29 2016 crashlog_00003.tar.gz
Check for what flags are enabled on the filesystem, perhaps there's yet another new ext4 flag that we can't handle and need to have some check for. Thanks!
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg spars e_super large_file huge_file uninit_bg dir_nlink extra_isize
[snip]
if it's not enough, tell me what should I run?
Yes, it could be one of those. Clear flags until it works, if it lets you, otherwise make some test images with specific flags. Thanks.
participants (2)
-
Andy Shevchenko -
Tom Rini