On Tue, 27 Oct 2009 21:05:40 -0400 eschvoca <eschvoca@xxxxxxxxx> wrote: [ cutting out a lot of non-relevant parts of the mail; please do that as well] > > [ 13.334718] EXT4-fs error (device sda2): ext4_mb_generate_buddy: > EXT4-fs: group 4: 1051 blocks in bitmap, 108 in gd > [ 13.334733] Aborting journal on device sda2:8. > [ 13.368166] ext4_abort called. > [ 13.368171] EXT4-fs error (device sda2): ext4_journal_start_sb: > Detected aborted journal > [ 13.368174] Remounting filesystem read-only > [ 13.389014] lp: driver loaded but no devices found > [ 13.401049] dcdbas dcdbas: Dell Systems Management Base Driver > (version 5.6.0-3.2) > [ 13.867414] EXT4-fs error (device sda2) in > ext4_reserve_inode_write: Journal has aborted > [ 13.892484] Remounting filesystem read-only > [ 14.034630] EXT4-fs error (device sda2): ext4_mb_generate_buddy: > EXT4-fs: group 5: 6795 blocks in bitmap, 6082 in gd > [ 14.034692] mpage_da_map_blocks block allocation failed for inode > 16807 at logical offset 0 with max blocks 1 with error -30 > [ 14.034700] This should not happen.!! Data will be lost > [ 14.034708] ext4_da_writepages: jbd2_start: 1024 pages, ino 16807; > err -30 [ 14.034711] Pid: 48, comm: pdflush Tainted: G W > 2.6.29-rc7.14-paul1 #1 > [ 14.034712] Call Trace: > [ 14.034718] [<c04e1278>] ? printk+0x18/0x20 > [ 14.034723] [<c022ac87>] ext4_da_writepages+0x567/0x5a0 > [ 14.034726] [<c022db90>] ? ext4_da_get_block_write+0x0/0x220 unfortunately, this is not from the patch Paul sent you, this is your root filesystem telling you it is highly corrupted and it's about to give up... -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
