what should I do?

[file system]

[root@ecfarm2 log]# dmesg|more
Allocating block in system zone - block = 426328
EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block
= 426329
EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block
= 426330
EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block
= 426331
EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block
= 426332
EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block
= 426333
EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block
= 426334
EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block
= 426335
EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in system zone - block
= 426336
EXT3-fs error (device ida0(72,1)): ext3_new_block: Allocating block in

which filesystems that I recover? which mounted point?

The linux contain 1 disk 36.4GB

I have backed-up data.
what should I do to recover it

[root@ecfarm2 log]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/ida/c0d0p1 2.0G 1.4G 532M 73% /
/dev/ida/c0d0p9 25G 21G 2.4G 90% /data5
/dev/ida/c0d0p8 985M 702M 234M 76% /home
none 1.9G 0 1.9G 0% /dev/shm
/dev/ida/c0d0p7 2.9G 2.5G 295M 90% /usr
/dev/ida/c0d0p5 2.0G 1.9G 58M 97% /var
spb:/B0 27G 14G 13G 52% /nas
spb:/B2 266G 243G 21G 93% /mnt
spb:/B3 27G 24G 3.0G 89% /nas3

[Steven E. Protter]

Shalom,


Arrange for reboot and fsck of this system.

What have you done to this system lately.

To answer your question on restoring the data, you'll have to tell me how you backed it up in the first place.

SEP

[file system]

I mean backed-up is only backing up data file system except OS area.

how can i backup OS area?

[Ralf Hildebrandt]

device ida0(72,1): check if the major and minor numbers for any of your /dev/ida/* files match 72 and 1. I guess it's /dev/ida/c0d0p1 that's affected.

touch /forcefsck

and reboot.

[Alan_152]

back up the system, break the raid array, and test each of the drives with badblocks. Identifiy the bad drive(s), replace, rebuild the array, and restore.

[Ivan Ferreira]

You can save the OS data using the tar or star comman. Star is preferred.

Ensure that the array is not having problems, run array configuration utility.

Also, I think that you only need to run fsck, if fsck cannot repair it, destroy and re-create the filesytem.

I think that you should not destroy the array.