Filesystem damage in TF card of AM3352

Bruce li

Other Parts Discussed in Thread: AM3352

Dear TI Engineers,

One of my customer encountered below issue about AM3352,

1) Use TF for memory, 2 partition--Boot and rootfs, Boot for Uboot and kernel, FAT format; rootfs is Ext4 format , files are generated by Yocto tool; several 3rd software such as mysql, redis, openstack, MessageQueue, webserver is in the filesystem

2) TF card is handled by MMC0 controller of AM3352, 48MHZ

3) When products with above configuration have spent 2~3 months ion site. Many of them have file system damage information. Most apps is located in /OPT Directory. After test, we found there are some W/R operation from apps and 3rd middleware, and Ext4 file system in TF card got damage.

So my questions are:

1) Is it suitable to choose TF card for this environment? Any better idea?

2) is it possible to avoid if we use lower frequency such as 24MHZ or even lower?

3) Any other suggest for solve this problem ?

Thanks a lot . Look forward for your feedback.

over 7 years ago

0 Biser Gatchev-XID over 7 years ago

TI__Guru**** 393215 points

Hi,

What is the model and manufacturer of the card? Have they tried with cards from different suppliers? What software are they using?

0 Bruce li over 7 years ago in reply to Biser Gatchev-XID

Genius 5580 points

Thanks for your quick reply.

Currently customer is using SanDisk Ultra 16GB Class 10 TF card. And they have purchased some industry-standard TF card, will do the same test later.

About the software, mysql, redis, openstack, MessageQueue, webserver and user aoolication are in use and many module of them will R/W the log.

0 Biser Gatchev-XID over 7 years ago in reply to Bruce li

TI__Guru**** 393215 points

I have asked the factory team for comments on this. Feedback will be posted here when available.

0 Bruce li over 7 years ago in reply to Biser Gatchev-XID

Genius 5580 points

Thank you so much : )

0 Pavel Botev over 7 years ago in reply to Bruce li

TI__Guru**** 170625 points

Hi Bruce,

Is this brand new TF card, or it is already used by another project? Can you test with another new TF card, as the one you are using might be damaged.

Also mount in sync mode to ensure data integrity (trade off is lower performance), see the below wiki for more info:
processors.wiki.ti.com/.../Processor_SDK_Linux_Kernel_Performance_Guide

How did you create this card? Can you try the script located in the latest SDK? The script is using ext3 (not ext4) for rootfs.

ti-processor-sdk-linux-am335x-evm-03.00.00.04/bin/create-sdcard.sh

See the below wiki pages for more details:

processors.wiki.ti.com/.../Processor_SDK_Linux_Training:_Introduction_to_Device_Driver_Development

processors.wiki.ti.com/.../Processor_SDK_Linux_create_SD_card_script

Regards,
Pavel

0 Matthijs van Duin over 7 years ago

Mastermind 8020 points

Are the devices subject to unclean reboots (e.g. watchdog resets) or shutdowns (e.g. power loss) ?

0 Bruce li over 7 years ago in reply to Matthijs van Duin

Genius 5580 points

Most fail cases occured without power loss or reboot

0 Bruce li over 7 years ago in reply to Pavel Botev

Genius 5580 points

Hi Pavel,
Thanks a lot.
We've tried to change to new card and it still failed after several days running . Customer used mkfs.ext4 CMD to creat card, with some parameter such as Journaling, commit=2, data=order, nodelalloc, no barrier etc.
I'll suggest custoemr to try your advice about ext3

0 Matthijs van Duin over 7 years ago in reply to Bruce li

Mastermind 8020 points

Any errors in kernel log?

0 Bruce li over 7 years ago in reply to Matthijs van Duin

Genius 5580 points

here is the log of fsck command in broken TF card.

10jf.txt

Warning!  /dev/mmcblk0p2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inode 261717 has an invalid extent
	(logical block 5, invalid physical block 274879007548, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 6, invalid physical block 17180974593, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 7, physical block 1105411, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 8, physical block 1105417, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 9, physical block 1081821, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 10, physical block 1081818, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 9, invalid physical block 68720566295, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 16777228, invalid physical block 9345849925699, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 12, physical block 1089616, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 14, invalid physical block 1099512717373, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 15, physical block 1089575, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 16, physical block 1089559, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 17, invalid physical block 17180951004, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 18, physical block 1089619, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 19, physical block 1089577, len 2049)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 20, physical block 1089579, len 2)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 22, physical block 1155106, len 129)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 23, physical block 1089626, len 9)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 4120, physical block 1081816, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 1048601, physical block 1081810, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 26, physical block 1089852, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 27, invalid physical block 141012904288361, len 2)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 270532637, physical block 1089578, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 30, physical block 1089625, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 31, physical block 1089640, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 288, invalid physical block 8796094111784, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 536870945, physical block 1081812, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 34, physical block 1081808, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 35, physical block 1081814, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 36, invalid physical block 5283970, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 37, invalid physical block 5497559228464, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 38, physical block 1081811, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 39, physical block 1089594, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 32, physical block 1081817, len 513)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 41, physical block 1089581, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 42, invalid physical block 1099512717638, len 2)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 44, physical block 1081815, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 45, physical block 1089667, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 110, physical block 1089620, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 1073741871, physical block 1081809, len 3)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 48, physical block 1089593, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 49, physical block 1089621, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 50, physical block 1089723, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 51, physical block 1089623, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 52, physical block 1089628, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 53, physical block 1089604, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 54, physical block 1089664, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 55, physical block 1089569, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 56, physical block 1089821, len 2)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 58, physical block 1089687, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 59, physical block 1089719, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 60, physical block 1089722, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 61, physical block 1089778, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 62, physical block 1089629, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 63, physical block 1090194, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 64, physical block 1089797, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 65, physical block 1089720, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 66, physical block 1089718, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 67, physical block 1089663, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 68, physical block 1089817, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 69, physical block 1089820, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 70, physical block 1089665, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 71, physical block 1089721, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 72, physical block 1081770, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 73, physical block 1089647, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 74, physical block 1089661, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 75, physical block 1089716, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 76, physical block 1089605, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 77, physical block 1089818, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 78, physical block 1089685, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 79, physical block 1089630, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 80, physical block 1081790, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 81, physical block 1089816, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 82, physical block 1089975, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 83, physical block 1089662, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 84, physical block 1081791, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 85, physical block 1081789, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 86, physical block 1089595, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 87, physical block 1089622, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 88, physical block 1081771, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 89, physical block 1089660, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 90, physical block 1089686, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 91, physical block 1081813, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 92, physical block 1089717, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 93, physical block 1081774, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 94, physical block 1089624, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 95, physical block 1089658, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 96, physical block 1081768, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 97, physical block 1081788, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 98, physical block 1089656, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 99, physical block 1089715, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 100, physical block 1089668, len 2)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 102, physical block 1089631, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 103, physical block 1089657, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 104, physical block 1089707, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 105, physical block 1089681, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 106, physical block 1089574, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 107, physical block 1089714, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 108, physical block 1081819, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 109, physical block 1081773, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 110, physical block 1081752, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 111, physical block 1081754, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 112, physical block 1089680, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 113, physical block 1089670, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 114, physical block 1089711, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 115, physical block 1081787, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 116, physical block 1089659, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 117, physical block 1089708, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 118, physical block 1081772, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 119, physical block 1089777, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 120, physical block 1081786, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 121, physical block 1081759, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 122, physical block 1089709, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 123, physical block 1089706, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 124, physical block 1089724, len 2)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 126, physical block 1089704, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 127, physical block 1081753, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 128, physical block 1081755, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 129, physical block 1081784, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 130, physical block 1089671, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 131, physical block 1081775, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 16777354, invalid physical block 34636196, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 16777356, physical block 1081778, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 3145870, physical block 1081766, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 145, invalid physical block 68720566516, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 148, invalid physical block 34644251, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 151, invalid physical block 5284096, len 16385)
Clear? no

Inode 261717 has an invalid extent
	(logical block 4325528, invalid physical block 1099512717570, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 154, invalid physical block 19791210389899, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 4251, physical block 1081765, len 33)
Clear? no

Inode 261717 has an invalid extent
	(logical block 156, invalid physical block 1099512717569, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 158, invalid physical block 17180958868, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 134217887, invalid physical block 9478321, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 160, physical block 1081783, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 67109025, physical block 1057041, len 3)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 2097316, physical block 1089813, len 257)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 165, physical block 1081521, len 65)
Clear? no

Inode 261717 has an invalid extent
	(logical block 166, invalid physical block 35184373178640, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 167, physical block 1089841, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 168, physical block 1089845, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 169, invalid physical block 135307570, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 170, invalid physical block 1099512717571, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 683, invalid physical block 140737489445218, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 172, physical block 1089910, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 2097325, physical block 1089812, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 174, physical block 1089823, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 175, physical block 1089710, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 176, physical block 1089564, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 177, physical block 1089878, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 178, physical block 1090591, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 179, physical block 1089560, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 181, invalid physical block 8796094111795, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 182, physical block 1089589, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 2231, invalid physical block 17592187134214, len 65)
Clear? no

Inode 261717 has an invalid extent
	(logical block 184, invalid physical block 68198427, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 185, physical block 1089591, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 186, physical block 1089727, len 65)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 187, physical block 1089566, len 16385)
Clear? no

Inode 261717 has an invalid extent
	(logical block 188, invalid physical block 1099512717362, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 189, physical block 1089883, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 2238, physical block 1089889, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 191, invalid physical block 2199024345113, len 257)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 192, physical block 1089590, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 193, physical block 1089930, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 194, physical block 1089866, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 194, physical block 1081825, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 196, invalid physical block 9478146, len 1)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 197, physical block 1111715, len 165)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 362, physical block 1111937, len 61)
Clear? no

Inode 261717 has out of order extents
	(invalid logical block 423, physical block 1112084, len 88)
Clear? no

Inode 261717 has an invalid extent
	(logical block 510, invalid physical block 4398047623360, len 98)
Clear? no

Inode 261717 has an invalid extent
	(logical block 960, invalid physical block 137440051465, len 71)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 1033, physical block 1098124, len 4097)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 2098189, physical block 1089555, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 9235, physical block 1089618, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 1044, invalid physical block 274878996670, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 1045, physical block 1089776, len 4097)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 1049, physical block 1089635, len 2049)
Clear? no

Inode 261717 has an invalid extent
	(logical block 1050, invalid physical block 4296049075, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 1193, invalid physical block 70506184221102, len 2)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 66731, physical block 1090000, len 2)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 17582, physical block 1089991, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 132274, physical block 3187159, len 3)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 263353, physical block 1090015, len 0)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 2147484858, physical block 1090356, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 1211, physical block 1089965, len 257)
Clear? no

Inode 261717 has an invalid extent
	(logical block 1213, invalid physical block 68720567088, len 1)
Clear? no

Inode 261717 has zero length extent
	(invalid logical block 1236, physical block 1090002)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 1247, physical block 1090357, len 4097)
Clear? no

Inode 261717 has an invalid extent
	(logical block 1247, invalid physical block 17592187134606, len 10)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 17636, physical block 1090176, len 1)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 33555685, physical block 1089916, len 33)
Clear? no

Inode 261717 has an invalid extent
	(logical block 1254, invalid physical block 34360828597, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 1255, invalid physical block 34360828547, len 1)
Clear? no

Inode 261717 has an invalid extent
	(logical block 1278, invalid physical block 135308079, len 3)
Clear? no

Inode 261717, end of extent exceeds allowed value
	(logical block 1073743105, physical block 1091104, len 12)
Clear? no

Inode 261717 has an invalid extent
	(logical block 17677, invalid physical block 8796102501046, len 1)
Clear? no

Inode 261717, i_blocks is 97128, should be 91520.  Fix? no

Inodes that were part of a corrupted orphan linked list found.  Fix? no

Inode 654097 was part of the orphaned inode list.  IGNORED.
Deleted inode 654113 has zero dtime.  Fix? no


Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 7: 1606110 1606111 1606112
Multiply-claimed block(s) in inode 261717: 1606110 1606111 1606112 1089824 1089827
Multiply-claimed block(s) in inode 261767: 1089613
Multiply-claimed block(s) in inode 263873: 1083817 1094327 1094328 1106561 1106562
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 3 inodes containing multiply-claimed blocks.)

File /opt/log/redis.log (inode #261717, mod time Thu Sep  1 10:33:16 2016) 
  has 5 multiply-claimed block(s), shared with 1 file(s):
	<The group descriptor inode> (inode #7, mod time Tue Feb 23 06:11:18 2016)
Clone multiply-claimed blocks? no

Delete file? no

File /opt/au/lirc/src/lirc-0.9.0/setup-driver.sh (inode #261767, mod time Mon Apr 27 09:11:11 2015) 
  has 1 multiply-claimed block(s), shared with 0 file(s):
Multiply-claimed blocks already reassigned or cloned.

File /opt/au/au_pack-1.0.0.15.tar.gz (inode #263873, mod time Mon Apr 27 09:11:13 2015) 
  has 5 multiply-claimed block(s), shared with 0 file(s):
Multiply-claimed blocks already reassigned or cloned.

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  +167972 +168019 +168336 +168353 +168434 +168799 +168815 +168843 +168908 +168914 +168930 +169055 +169076 +169104 +169270 +169384 +169464 +169544 +169665 +169737 +170037 +170263 +170429 +170893 +170990 +171072 +171103 +171148 +171309 +171380 +171803 +171806 +171844 +171862 +171942 +172059 +172072 +172414 +172505 +172534 +172768 +172819 +173504 +173585 +173754 -173858 -173951 -173955 -174005 +174102 +174155 +174210 +174386 +174827 +174864 +175209 +175315 +175431 +175494 +175537 +175545 +175564 +175995 +176051 +176191 +176235 +176320 +176334 +176388 +176489 +176645 +176908 +177163 +177189 +177216 +177364 +177477 +177537 +178170 +178327 +178562 +178626 +178686 +178917 +179151 +179243 +179393 +179537 +180007 +180049 +180188 +180407 +180447 +180493 +180582 +180618 +180658 +180871 +180973 +181091 +181126 +181164 +181167 +181189 +181294 +181547 +181565 +181730 +181836 +182022 +182103 +182141 +182255 +182311 +182389 +182426 +182693 +182805 +183043 +183186 +183321 +183509 +183513 +183618 +184000 +184085 +184280 -(1081752--1081755) -1081759 -1081764 -1081766 -(1081768--1081775) -(1081777--1081779) -1081781 -(1081783--1081784) -(1081786--1081791) -(1081808--1081825) -1089538 -1089555 -(1089558--1089561) -(1089563--1089564) -(1089566--1089570) -(1089574--1089581) -(1089586--1089587) -(1089589--1089597) -(1089603--1089607) -1089616 -(1089618--1089626) -(1089628--1089631) -(1089640--1089642) -1089647 -(1089656--1089671) -(1089680--1089681) -(1089684--1089687) -1089704 -(1089706--1089711) -(1089713--1089727) -(1089776--1089778) -1089780 -(1089792--1089795) -(1089797--1089798) -(1089808--1089814) -(1089816--1089823) -(1089841--1089842) -1089845 -1089866 -1089883 -(1089889--1089891) -1089910 -1089916 -(1089930--1089931) -1089955 -(1089965--1089967) -1089975 -1089991 -(1090000--1090002) -(1090007--1090009) -1090015 -1090125 -(1090176--1090179) -(1090190--1090191) -1090194 -(1090229--1090232) -(1090349--1090352) -(1090356--1090357) -(1091104--1091115) -(1097993--1098063) -1098124 -1100604 -1105409 -1105411 -1105417 -(1111715--1111879) -(1111937--1111997) -(1112084--1112171) -(1112256--1112353) -(2655648--2655651) -(2656029--2656076)
Fix? no

Free blocks count wrong for group #5 (1525, counted=1644).
Fix? no

Free blocks count wrong (3129606, counted=3110938).
Fix? no

Inode bitmap differences:  -654097 -654113
Fix? no

Free inodes count wrong (893681, counted=893585).
Fix? no


rootfs: ********** WARNING: Filesystem still has errors **********

rootfs: 22031/915712 files (0.3% non-contiguous), 529197/3658803 blocks

0 Matthijs van Duin over 7 years ago in reply to Bruce li

Mastermind 8020 points

Bruce li said:
Most fail cases occured without power loss or reboot

Ehh.... how would you detect a failure case without reboot of any kind? You do realize you can't actually fsck a filesystem while it's mounted, and in particular can't fsck the rootfs while the system is running?

Bruce li said:
here is the log of fsck command in broken TF card.

Apparently not... "Warning! /dev/mmcblk0p2 is mounted."

Processors

Processors forum

Filesystem damage in TF card of AM3352