>
> Did anyone else see that "Free blocks count corrupted for block group X"
> error in /var/log/messages?
> Or others, especially with large filesystems?
>
Mine is a 24GB raid 5 (hardware dac960). It was fixable with fsck, and
hasn't occurred since the 2.2.0prex kernels. Nonetheless that is
Interesting.
How large is your array (mine has 50 Gig netto)?
Did you have some unusual large directories on the filesystem (i.e. a
directory with several thousand subdirectories or files).
Did anyone else see that "Free blocks count corrupted for block group X"
error in /var/log/messages?
Or o
On Wed, Mar 10, 1999 at 07:28:01PM +0100, Dietmar Stein wrote:
[...]
>We - better I - use SuSE-Linux 6.0 which contains the (SuSE-)patched kernel
>2.0.36 on a SMP-system. The technical data is:
>a pair of PII-400, Asus P2B-DS mainboard, 512 MByte of RAM, three Adaptec
>SCSI-controllers (yeah, I kn
Hi David,
thanks for your answer and also thanks to Matthew and Adam for their hints.To
answer your
questions:
We - better I - use SuSE-Linux 6.0 which contains the (SuSE-)patched kernel
2.0.36 on a SMP-system. The technical data is:
a pair of PII-400, Asus P2B-DS mainboard, 512 MByte of RAM, th
> "EXT2-fs error (device 09:00): ext2_new_block: Free blocks count
> corrupted for block group 259"
> in the log.
> - ext2fs problem
Probably unrelated, but I got this error using the DAC960 hardware raid
driver, linux kernel 2.2.0-pre9, and knfsd a couple of times about 2
months ago, and not
I´m running the december raid patches on a lightly but constantly loaded
nfs soft-raid5 fileserver. Until now there wasn´t any problem during
normal operation, but I just got lots of:
"EXT2-fs error (device 09:00): ext2_new_block: Free blocks count
corrupted for block group 259"
in the log.
the e
