#278 block to be freed is outside the map

utilities (15)


we have a disk array (with a Raid 6 controller), mounted by a 32 bit Ubuntu 8.04 server. The system has an Intel(R) Core(TM)2 CPU. We are using the JFS file system for the disk array. The total disk array size is 16 TB. Due to the raid 6 redundancy, the total partition size is 13 TB. The partition has been created with gparted using the GPT partition table.

Yesterday, I have found the disk array mounted in read-only mode. Looking at the kernel log I have found the following message:

[156294.776865] blkno = 0, nblocks = 0
[156294.776895] ERROR: (device sda1): dbFree: block to be freed is outside the map

The current used space is the following (/dev/sda1):

~$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 453G 7.6G 422G 2% /
varrun 2.0G 68K 2.0G 1% /var/run
varlock 2.0G 0 2.0G 0% /var/lock
udev 2.0G 52K 2.0G 1% /dev
devshm 2.0G 0 2.0G 0% /dev/shm
/dev/sda1 13T 7.5T 5.3T 59% /archive_sps

Our system was stucked 3 days ago. A reboot was necessary and a complete file system check was performed. The jfs_fsck program fixed the file system successfully. Now we have this problem, maybe related to the previous one.

Does someone have any hint about it? Is it safe to have a 13 TB partition in a 32 bit system with JFS. How can such error be generated?

Thank you for any help.




  • David Kleikamp

    David Kleikamp - 2010-02-22

    JFS should work okay on a 13 TB partition. The error indicates that some data structure had zero fields where it should have had something else. It's possible that fsck failed to fix everything correctly. Does a subsequent fsck show any errors?

  • David Kleikamp

    David Kleikamp - 2010-02-22
    • assigned_to: nobody --> shaggyk
  • Marco

    Marco - 2010-02-23

    In the evening, the raid 6 controller has shown a red light for one of the 16 disks of the array. Also looking into the raid bios, we have seen error messages for such disk. Hence, the above jfs error is caused by a hardware failure.

    This bug can be closed as "not a bug".

    Thank you.

  • David Kleikamp

    David Kleikamp - 2010-02-23

    Thanks for the follow-up. Closing due to hardware problem.

  • David Kleikamp

    David Kleikamp - 2010-02-23
    • status: open --> closed-invalid

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks