#6480 NORM Never A: jffs2 is confused about file size after a truncation

[Zarro Boogs per Child]

#6480: jffs2 is confused about file size after a truncation
--------------------+-------------------------------------------------------
 Reporter:  cscott  |       Owner:  dwmw2                            
     Type:  defect  |      Status:  new                              
 Priority:  normal  |   Milestone:  Never Assigned                   
Component:  kernel  |     Version:  Development build as of this date
 Keywords:          |    Verified:  0                                
 Blocking:          |   Blockedby:                                   
--------------------+-------------------------------------------------------
 On build 693 (kernel 2.6.22-20080211.1.olpc.9f4e619336a08dc):
 {{{
 # cat /dev/zero | head -c 100000000 > /home/olpc/space-filler
 # ls -l /home/olpc/space-filler
 -rw-r--r--  1 root root 100000000 Feb 15 19:44 /home/olpc/space-filler
 # ls -s /home/olpc/space-filler
 97657 /home/olpc/space-filler
 # ls -hs /home/olpc/space-filler
 96M /home/olpc/space-filler
 # cat /dev/null > /home/olpc/space-filler
 # ls -l /home/olpc/space-filler
 -rw-r--r--  1 root root 0 Feb 15 19:45 /home/olpc/space-filler
 # ls -s /home/olpc/space-filler
 97657 /home/olpc/space-filler
 # ls -hs /home/olpc/space-filler
 96M /home/olpc/space-filler
 }}}
 That's pretty funky.  Truncating the file seems to leave somebody's idea
 of its size at nearly 100M.

-- 
Ticket URL: <http://dev.laptop.org/ticket/6480>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system