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
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
Good!
No problems with the patch, no significant problems with the tools.
(The only undesirable side effect being significant nerve tickle for
using alpha software on a production server.)
What I´m interested in: has anyone else had any major run-time-problems
with the software-raid (981215 or ja
,
which seems to be under development right now).
---
Thilo Herrmann, Rival Network GmbH
Phone: +49 89 82087-0, email: [EMAIL PROTECTED]
---
usually install loadlin dos boot
partitions. With the large hds the partitioning seems to get somewhat
tricky.
The "begin" and "start" issue is pretty strange. The suse linux
partitioner just shows "from" and "to".
---
Thilo Herrmann, Rival Network GmbH
Phone:
hotremove gives:
/dev/md0: can not hot-remove disk: disk not in array!
The drive is functional, however, I can partition and mke2fs it (raid
stopped).
>(there was one bug displayed in the logs, i've fixed this in my tree
already. a reboot would have fixed this bug, and it's nonfatal
ver kernel: md0: no spare disk to reconstruct
array! -- continuing in degraded mode
Dec 16 20:20:12 fileserver kernel: md: recovery thread finished ...
Dec 16 20:20:12 fileserver kernel: hdg1 [events: 0007](write) hdg1's
sb offset: 16510912
Dec 16 20:20:12 fileserver kernel: hdf1 [events: 00
