Filesystem contains large files, but lacks LARGE_FILE flag in superblock.

This morning, the fileserver was not online. It is a linux server hosting some
filesystems which are shared via NFS and samba.

After the tape backup the server was hanging in the reboot sequence, because
of requesting a manual file system check.

The error message seen above was

Filesystem contains large files, but lacks LARGE_FILE flag in superblock.
After logging in with the root-password and issuing the fsck command manually,
there was one fix and the system could reboot.

The strange thing was, that this filesystem contains since some months large
files, but only this morning this was a problem.

dumpe2fs -h is a help to investigate the filesystem.

server:/root # dumpe2fs -h /dev/sdc1
dumpe2fs 1.28 (31-Aug-2002)
Filesystem volume name:
Last mounted on:
Filesystem UUID: 3a693ec2-aac3-4207-9282-060677ef3a2d
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery sparse_super large_file
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 8978432
Block count: 17932548
Reserved block count: 179321
Free blocks: 3058549
Free inodes: 8678021
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Last mount time: Thu Mar 19 08:11:23 2009
Last write time: Thu Mar 19 08:11:23 2009
Mount count: 1
Maximum mount count: 26
Last checked: Thu Mar 19 08:09:25 2009
Check interval: 15552000 (6 months)
Next check after: Tue Sep 15 09:09:25 2009
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal UUID:
Journal inode: 8
Journal device: 0x0000
First orphan inode: 0

As you can see, it's already an old installation.
The interesting thing is, that this also shows the number of free inodes, which
can be shown by df -i /Directory

server:/root # df -i /DIR
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/sdc1 8978432 300418 8678014 4% /DIR
This was long time ago a problem, that the system responded with a full
filesystem, but df -h showed still free space. The problem was, that there were
no more free inodes available.