fsck and raidtools

[Sy Ali]

fsck seems to go mental when I try to use it on an md device.  Is this normal?

 # fsck /dev/md0
 fsck 1.39 (29-May-2006)
 e2fsck 1.39 (29-May-2006)
 The filesystem size (according to the superblock) is 17101184 blocks
 The physical size of the device is 17101168 blocks
 Either the superblock or the partition table is likely to be corrupt!
 Abort<y>?

Going ahead with the repairs seems to do nothing.  This error will
always reappear.

What's going on?  How can I check an md device if fsck always acts like this?

It sounds reasonable that I would have to check the (in this case) two
source drives individually.  Is that right?
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml