#9513 BLOC Not Tri: ext4 filesystems craps its journal

Zarro Boogs per Child bugtracker at laptop.org
Fri Oct 16 14:48:02 EDT 2009


#9513: ext4 filesystems craps its journal
--------------------------+-------------------------------------------------
 Reporter:  wad           |                 Owner:                     
     Type:  defect        |                Status:  new                
 Priority:  blocker       |             Milestone:  Not Triaged        
Component:  not assigned  |               Version:  1.5-B2             
 Keywords:                |           Next_action:  approve for release
 Verified:  0             |   Deployment_affected:                     
Blockedby:                |              Blocking:                     
--------------------------+-------------------------------------------------
 On an XO-1.5 B2 prototype, I have twice seen an ext4 filesystem get itself
 into a state where it cannot be used.

 Freeing unused kernel memory: 300k freed
 [    5.713384] Write protecting the kernel text: 3264k
 [    5.729086] Write protecting the kernel read-only data: 1068k
 [    5.880454] udev: starting version 141
 [    7.508080] EXT4-fs: barriers enabled
 [    7.527402] kjournald2 starting: pid 1135, dev mmcblk0p2:8, commit
 interval 5 seconds
 [    7.545471] EXT4-fs: delayed allocation enabled
 [    7.560151] EXT4-fs: file extents enabled
 [    7.578287] EXT4-fs: mballoc enabled
 [    7.591597] EXT4-fs: mounted filesystem mmcblk0p2 with ordered data
 mode
 [    7.791447] EXT4 FS on mmcblk0p2, internal journal on mmcblk0p2:8
 [    7.816735] mkdir used greatest stack depth: 2296 bytes left
 [    8.133044] EXT4 FS on mmcblk0p2, internal journal on mmcblk0p2:8
 [    8.658607] dcon_freeze_store: 0
 [    8.661898] dcon_source_switch to CPU
 [    9.219340] olpc-dcon: The CPU has control
 [   28.557857] EXT4-fs error (device mmcblk0p2) in ext4_new_inode: Journal
 has aborted
 [   28.572789] EXT4-fs error (device mmcblk0p2) in ext4_create: Journal
 has aborted
 [   29.015088] ext4_abort called.
 [   29.018164] EXT4-fs error (device mmcblk0p2): ext4_journal_start_sb:
 Detected aborted journal
 [   29.026884] Remounting filesystem read-only

 Running fsck on the partition fixes stuff, but the filesystem still has
 problems and cannot be used.   New files can be created, but existing
 files cannot be deleted.

 Can we please test an ext3 filesystem in our next XO-1.5 release.

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


More information about the Bugs mailing list