awww
Oct 8 2003, 04:03 AM
Hello,
I am experiencing strange issues with a p4 I purchased about 1 month ago, in particolar I am finding these strange error messages in /var/log/messages:
kernel: kmod: runaway modprobe loop assumed and stopped
and
kernel: VFS: Error -5 occured while creating quota.
Oct 8 00:39:09 ns7 kernel: VFS: Quota for id 38364 referenced but not present.
Oct 8 00:39:09 ns7 kernel: VFS: Can't read quota structure for id 38364.
Oct 8 00:39:09 ns7 kernel: VFS: Quota for id 38364 referenced but not present.
Oct 8 00:39:09 ns7 kernel: VFS: Can't read quota structure for id 38364.
Oct 8 00:49:45 ns7 kernel: VFS: Inserting already present quota entry (block 38320).
What is that, and most important: how can be resolved?
The average uptime of this server is about 5-6 hours right now...
Thanks
smack
Oct 8 2003, 09:54 AM
VFS is linux's virutal file system layer. I would submit a trouble ticket ASAP.
ScottPO
Oct 8 2003, 02:15 PM
Yea, VFS errors indicate problems in the quota files. This typically causes a crash because then the file system tells a program that there's insufficient space (et cetera) when the program is not expecting this to happen. Submit a trouble ticket, you fix it yourslef:
quotoff -a
quotacheck -ugav (SEE NOTE BELOW)
quotaon -a
IF quotacheck segmentation faults, that means your quota files are beyond repair. Figure out which partition has quotas installed by examing /etc/fstab. Then cd in to that mouunt point, turn quotas off (quotaoff -a) and move the two aquota files somewhere else. Then, run the quotacheck (quotacheck -ugav) and then turn quotas back on (quotaon -a)
Also, answer yes to any question similar to "Partition is already mounted, data will be inaccurate."
awww
Oct 8 2003, 06:04 PM
Thank you very much, let's see if this will help...
awww
Oct 11 2003, 02:48 AM
I rebuilt quotas from scratch but unfortunately it didn't work.
After 19 hours the server hanged again and now, after a reboot, it still shows the same quota error...
Might be a kernel/quotas bug... Any suggestion?
Thank you
smack
Oct 11 2003, 10:00 PM
As it may be a sign of hardware failure, you should really submit a trouble ticket.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.