I think it means you tried to run fsck across an area being resynced.
-- Mike
On Wed, 12 Apr 2000 [EMAIL PROTECTED] wrote:
> Hello!
>
> This is what I got in the dmesg after my machine with raid5 crashed again:
>
> set_blocksize: b_count 1, dev md(9,0), block 245!
> set_blocksize: b_count 1, dev md(9,0), block 246!
> set_blocksize: b_count 1, dev md(9,0), block 247!
> set_blocksize: b_count 1, dev md(9,0), block 248!
> set_blocksize: b_count 1, dev md(9,0), block 249!
> set_blocksize: b_count 1, dev md(9,0), block 250!
> set_blocksize: b_count 1, dev md(9,0), block 251!
> set_blocksize: b_count 1, dev md(9,0), block 252!
> set_blocksize: b_count 1, dev md(9,0), block 253!
> set_blocksize: b_count 1, dev md(9,0), block 254!
> set_blocksize: b_count 1, dev md(9,0), block 255!
> ll_rw_block: device 09:00: only 4096-char blocks implemented (1024)
> last message repeated 210 times
> md0: blocksize changed during write
> nr_blocks changed to 64 (blocksize 4096, j 0, max_b locks 4333472)
>
> What does it mean?
