On Monday 06 January 2003 06:30, Rohit wrote:
On Mon, 6 Jan 2003, Derek Fountain wrote:
it via NFS. While writing a few gigs of data to it from another machine, it's falling about all over the place. The logs are full of errors from reiserfs and encouragements to run fsck.
Just make sure that one file is not more than 2G in size, ever. That is an NFS limitation methinks... if individual files are not that big, then there should be no problem. NFS and reiserfs are matured technologies and so is LVM - so I think the problem may lie somewhere else.
Post the log-error when it started. The very first messages - may be the first 10-20 of them.
I don't think posting dozens of errors will help much. Here's what I see: the problems started off with a few dozen "bit already cleared" errors from reiserfs, then it had a load of tree/node problems. Then it got an I/O error, and it all went south from there. On reboot, the LVM vgscan can't read the LV details from the physical volumes. All appears to suggest that the LVM layer went completely bananas. I'm using the kernel level NFS server. I wonder if the user level one would be any better. Perhaps there's something messy in that interaction. -- Australian Linux Technical Conference 2003: http://www.linux.conf.au/ Explain to your boss the benefits of you going...