On Thu, 2 Aug 2001, KELEMEN Peter wrote:
> * Seth Mos (knuffie@xxxxxxxxx) [20010801 09:46]:
> > That is probably caused by an IO error. I see you are using lvm
> > which could be related. If an IO error occurs the filesystem
> > will shutdown to prevent more damage.
> Well. I checked the hard drive (read-only) in another machine, it
> reports no errors. S.M.A.R.T. is happy, no relocated sectors or
> raw read, seek or CRC errors. Nothing.
That counters the hardware site.
> > This error could be on the device (bad cluster on the disk) or
> > something in a software layer like md or lvm going wrong which
> > is seen by XFS as a hardware error. What is actually the lvm
> > device. Do you use md or any other software that might
> > interfere? IDE or scsi and what controller and system. How is
> > the lvm device constructed.
> EIDE, no UDMA. No MD at all, LVM is pretty straightforward, a
> lonely 20G disk sliced into two, sitting in an extended partition.
> A big partition is actually the only PV, carrying a VG with six
> LVs. No magic, this is supposed to be a workstation. Kernel is
> tracked CVS, compiled with egcs-1.1.2. No overclock.
That indeed seems very simple. The problem is that it is hard to debug
since it will probably be extrmely hard to replicate. If you can find a
way to reproduce this, let us know please. We'd love to squash XFS related
I have absolutely zipp experience with LVM so I can't comment on any
problems on that front.
> The thing hasn't happened since (knock on wood).
Good luck then, you will need it for the next knock on wood.