[haiku-bugs] [Haiku] #7079: [ext4] could not initialize block allocator, going read-only!

  • From: "diver" <trac@xxxxxxxxxxxx>
  • Date: Sun, 09 Jan 2011 11:40:23 -0000

#7079: [ext4] could not initialize block allocator, going read-only!
---------------------------------+-----------------------------
   Reporter:  diver              |       Owner:  korli
       Type:  bug                |      Status:  new
   Priority:  normal             |   Milestone:  R1
  Component:  File Systems/ext2  |     Version:  R1/Development
   Keywords:                     |  Blocked By:
Has a Patch:  0                  |    Platform:  All
   Blocking:                     |
---------------------------------+-----------------------------
 This is r40175, gcc4hybrid.[[BR]][[BR]]

 ext4 volume always mounts in read-only mode. The following text is printed
 to syslog on every mount:

 {{{
 KERN: ext2: Inode::EnableFileCache(): Failed to create file cache
 KERN: ext2: AllocationBlockGroup(2269,73924621)::Initialize(): Mismatch
 between counted free blocks (520/30350) and what is set on the group
 descriptor (541)
 KERN: ext2: could not initialize block allocator, going read-only!
 }}}

 I tried to run fsck in Ubuntu by running '''touch /forcefsck''' and
 rebooting. That didn't help, exactly the same text is printed to the
 syslog.

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/7079>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts:

  1. Home
  2. haiku-bugs
  3. Archive
  4. 01-2011