Issues with Raid1 on a SS20 running 2.4.20

Issues with Raid1 on a SS20 running 2.4.20

[Scott Walker]

I have a SS20 with 2 18G disks in it. Both disks are identical Here is
my config setup.


raiddev                 /dev/md2
raid-level              1
nr-raid-disks           2
nr-spare-disks          0
chunk-size              4
persistent-superblock   1

device                  /dev/sda6
raid-disk               0
device                  /dev/sdb6
raid-disk               1

I have Raid and Raid1 compiled into Kernel 2.4.20.

Below is what happens when I fsck a raid device, Either on start or from
cli.

(none):~# fsck /tmp
fsck 1.33 (21-Apr-2003)
e2fsck 1.33 (21-Apr-2003)
The filesystem size (according to the superblock) is 255626 blocks
The physical size of the device is 255600 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort<y>? 

If I mount -a I get it mounted with no issues and the files systesm
works perfectly.

md: raid1 personality registered as nr 3
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.

Above is the line from the kernel boot up


I'm at a loss. Does anyone have some info?

Re: Issues with Raid1 on a SS20 running 2.4.20

[Paul Clements]

Scott Walker wrote:
 
> Below is what happens when I fsck a raid device, Either on start or from
> cli.
> 
> (none):~# fsck /tmp
> fsck 1.33 (21-Apr-2003)
> e2fsck 1.33 (21-Apr-2003)
> The filesystem size (according to the superblock) is 255626 blocks
> The physical size of the device is 255600 blocks
> Either the superblock or the partition table is likely to be corrupt!
> Abort<y>?

> I'm at a loss. Does anyone have some info?

I'm guessing that you created the filesystem on one of the component
devices (sda6, sdb6) before raiding them together. That doesn't always
work. The resulting md device can be up to 4K (your chunk size is 4k) or
64k (if you have a persistent superblock) smaller than the component
devices.

You can try to resize2fs the filesystem to the proper size or recreate
the filesystem by doing mkfs /dev/md2.

You will eventually get filesystem errors when the filesystem approaches
full capacity if you continue to use it as-is.

--
Paul