Modify

Opened 6 years ago

Last modified 3 years ago

#10061 new defect

TL-WR741ND v2.1 on completly empty jffs2-partition (/overlay) 196kB are used

Reported by: eleon216 Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: kernel Version: Trunk
Keywords: Cc:

Description

I wrote a tread in the forum, but no response, but I think it's a bug
https://forum.openwrt.org/viewtopic.php?id=31699

I run openwrt trunk r28151 on a TL-741ND v2.1:

the router is working, but I noticed a high usage on the overlay-partition after a fresh install. 212kB of the available 320kB are used. this is strange because the files on /overlay are only 30KB in total.
I started in failsafe-mode and run the "firstboot"-command to erase the jffs2-partion.

on the completely empty /overlay 196KB are used! I don't think this is normal, and I do not experience this on other devices e.g. on a TL-MR3220 (which has a 4MB SPI-Flash too) only a few KB are used.

Attached files:
df.txt: df -h output
dmesg.txt: dmesg output
jffs2debug.txt: dmesg output of "firstboot" with debuglevel2 of jffs2-kernel module

Attachments (3)

dmesg.txt (5.4 KB) - added by eleon216 6 years ago.
jffs2debug.txt (9.2 KB) - added by eleon216 6 years ago.
df.txt (395 bytes) - added by eleon216 6 years ago.

Download all attachments as: .zip

Change History (5)

Changed 6 years ago by eleon216

Changed 6 years ago by eleon216

Changed 6 years ago by eleon216

comment:1 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

comment:2 Changed 3 years ago by jbennett@…

I just recently noticed this behaviour. I believe the jffs2 file system is detecting a 64k erase block size, and is reserving 3 of those blocks for garbage collection and wear leveling. Other chips don't waste as much space as they possibly have a smaller than 64k erase block.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.