Ubuntu
linux package

  1. Bug #438379
  2. Comment #9

Comment 9 for bug 438379

Revision history for this message
Olivier Grisel (olivier-grisel) wrote :

Similar isue with both Jaunty and Karmic (same machine before and after upgrade) with EXT4 main partition on an SSD drive (MackbookPro 5.5). I added a noatime option but the problem as occurred again:

dmesg excerpt:

[85177.117155] EXT4-fs error (device sda3): htree_dirblock_to_tree: bad entry in directory #308546: directory entry across blocks - offset=0, inode=3633236108, rec_len=180364, name_len=142
[85177.117178] Aborting journal on device sda3:8.
[85177.117320] EXT4-fs (sda3): Remounting filesystem read-only
[85189.126309] EXT4-fs error (device sda3): htree_dirblock_to_tree: bad entry in directory #308546: directory entry across blocks - offset=0, inode=3633236108, rec_len=180364, name_len=142
[85192.321605] EXT4-fs error (device sda3): htree_dirblock_to_tree: bad entry in directory #308546: directory entry across blocks - offset=0, inode=3633236108, rec_len=180364, name_len=142
[85198.608480] EXT4-fs error (device sda3): htree_dirblock_to_tree: bad entry in directory #308546: directory entry across blocks - offset=0, inode=3633236108, rec_len=180364, name_len=142
[85209.177

mount output:

/dev/sda3 on / type ext4 (rw,noatime,relatime,errors=remount-ro)

uname -a
Linux turingcarpet 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux

Previous fsck (automatically triggered at reboot) did fixed the bad blocks without loosing important data AFAIK. I hope this will be the case again this time.