Need to keep running fsck on LVM

Once a week or so I am getting an issue with my volume where I can no longer write to it and I get "read only filesystem" errors. I need to unmount it and run an fsck.ext3 on it and it will fix errors and then will be fine for awhile. I assume that there is a drive that is dying in the array. Is there any way or telling which drive this might be?

Gumby

I would think that if you look in the /var/log/messages and/or /var/log/syslog would give you some indication if there is a hardware failure building.

Try this:

# grep /dev/hd /var/log/messages /var/log/syslog | more

And see what you get.

Nope, that outputs nothing at all.

I do however see the following in /vavr/log/messages over and over and over again...

Dec  1 23:12:46 localhost kernel: attempt to access beyond end of device
Dec  1 23:12:46 localhost kernel: dm-0: rw=0, want=6444890144, limit=905314304

Gumby

I've had the beyond end of device errors on a regular IDE drive before. Then they mysteriously went away.

If you find out, let me know. I was always curious about those.

Have you tried to use smartctl to access SMART data on the drives? --Matt