From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 195561] Suspicious persistent EXT4-fs error: ext4_validate_block_bitmap:395: [Proc] bg 17: block 557056: invalid block bitmap
Date: Tue, 09 May 2017 03:20:50 +0000 [thread overview]
Message-ID: <bug-195561-13602-gD03d7VJJW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-195561-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=195561
--- Comment #27 from James tao (tao1hua@aliyun.com) ---
How was the sdcard formatted?
> sdcard formatted by make_ext4fs.
Can you give me a clean reproduction that doesn't involve using AOSP userspace?
> I had try the way you provided. but I can't access to the git
> server(git.kernel).
[taohua@ubuntu-bsp ext4_issue]git clone
git://git.kernel.org/pub/scm/fs/ext2/xfstests-bld.git fstests
Cloning into 'fstests'...
fatal: unable to connect to git.kernel.org:
git.kernel.org[0: 147.75.110.187]: errno=Connection timed out
git.kernel.org[1: 2604:1380:3000:3500::3]: errno=Network is unreachable
[taohua@ubuntu-bsp ext4_issue]ping git.kernel.org
PING pub.nrt.kernel.org (147.75.110.187) 56(84) bytes of data.
64 bytes from 147.75.110.187: icmp_req=1 ttl=53 time=57.2 ms
64 bytes from 147.75.110.187: icmp_req=2 ttl=53 time=57.1 ms
64 bytes from 147.75.110.187: icmp_req=3 ttl=53 time=57.1 ms
Another way, I have try to run only linux (not Android) on the Broadcom ARM
chipset. and using the same kernel version. the test step as follow.
1. mkfs.ext4 /dev/mmcblk0 #format tf card as ext4
2. mount -t ext4 /dev/mmcblk0 /mnt/hd/ #mount tf card
3. mount -t ext4 /dev/mmcblk1p14 /mnt/flash/ # mount emmc partition as ext4
4. cp /mnt/flash/*.data /mnt/hd/ #copy data to tf card
# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 106944 10480 96464 10% /
none 106944 0 106944 0% /dev
tmpfs 118076 8 118068 0% /tmp
shm 118076 0 118076 0% /dev/shm
/dev/mmcblk0 7381352 3124064 3859288 45% /mnt/hd
/dev/mmcblk1p14 4536544 3116564 1166492 73% /mnt/flash
By the test in the same hardware everything looks good. Is it not an ext4
issue, but a issue of make_ext4fs?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-05-09 3:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 2:40 [Bug 195561] New: Suspicious persistent EXT4-fs error (device sda1): ext4_validate_block_bitmap:395: [Proc] bg 17: block 557056: invalid block bitmap bugzilla-daemon
2017-04-24 2:41 ` [Bug 195561] " bugzilla-daemon
2017-04-24 2:42 ` bugzilla-daemon
2017-04-24 2:44 ` bugzilla-daemon
2017-04-24 2:52 ` bugzilla-daemon
2017-04-24 3:00 ` bugzilla-daemon
2017-04-24 3:01 ` [Bug 195561] Suspicious persistent EXT4-fs error: " bugzilla-daemon
2017-04-24 4:51 ` bugzilla-daemon
2017-04-24 16:50 ` bugzilla-daemon
2017-04-24 16:53 ` bugzilla-daemon
2017-04-25 15:22 ` bugzilla-daemon
2017-04-25 15:23 ` bugzilla-daemon
2017-04-25 15:24 ` bugzilla-daemon
2017-04-25 15:27 ` bugzilla-daemon
2017-04-25 15:29 ` bugzilla-daemon
2017-04-25 15:29 ` bugzilla-daemon
2017-04-25 15:31 ` bugzilla-daemon
2017-04-25 15:32 ` bugzilla-daemon
2017-04-25 23:13 ` bugzilla-daemon
2017-04-25 23:14 ` bugzilla-daemon
2017-04-25 23:16 ` bugzilla-daemon
2017-04-25 23:18 ` bugzilla-daemon
2017-04-25 23:19 ` bugzilla-daemon
2017-04-25 23:20 ` bugzilla-daemon
2017-04-26 15:11 ` bugzilla-daemon
2017-04-29 21:59 ` bugzilla-daemon
2017-04-30 2:59 ` bugzilla-daemon
2017-04-30 3:20 ` bugzilla-daemon
2017-05-03 8:17 ` bugzilla-daemon
2017-05-03 17:48 ` bugzilla-daemon
2017-05-09 3:20 ` bugzilla-daemon [this message]
2017-05-09 5:01 ` bugzilla-daemon
2017-05-09 16:10 ` bugzilla-daemon
2017-05-13 12:00 ` bugzilla-daemon
2017-05-14 4:14 ` bugzilla-daemon
2017-05-14 11:41 ` bugzilla-daemon
2017-05-14 14:56 ` bugzilla-daemon
2017-05-14 18:20 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-195561-13602-gD03d7VJJW@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).