OpenVZ Forum: Support » *SOLVED* Problem starting lstat match.Po no such file

Home » General » Support » *SOLVED* Problem starting lstat match.Po no such file

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

*SOLVED* Problem starting lstat match.Po no such file [message #25634]

Fri, 04 January 2008 16:55

JimL
Messages: 116
Registered: February 2007

Senior Member

vzctl start 225
Starting VE ...
vzquota : (warning) Incorrect quota shutdown for id 225, recalculating disk usage
vzquota : (error) quota check : lstat `match.Po': No such file or directory
vzquota on failed [1]

Is there a way to recover from this?

Jim.

[Updated on: Sun, 06 January 2008 11:52] by Moderator

Report message to a moderator

Re: Problem starting lstat match.Po no such file [message #25640 is a reply to message #25634]

Sat, 05 January 2008 08:53

vaverin
Messages: 708
Registered: September 2005

Senior Member

can you try to remove quota file by using 'vzquota drop 225' command? In this case quota will be recalculated automatically when this VE will be started again.

thank you,
Vasily Averin

Report message to a moderator

Re: Problem starting lstat match.Po no such file [message #25641 is a reply to message #25640]

Sat, 05 January 2008 10:54

JimL
Messages: 116
Registered: February 2007

Senior Member

root@chinaberry:/vz# vzquota drop 225
root@chinaberry:/vz# vzctl start 225
Starting VE ...
Initializing quota ...
vzquota : (error) quota check : lstat `match.Po': No such file or directory
vzquota init failed [1]

Unfortunately no.

Thanks,
Jim.
Kernel: Linux version 2.6.18-8.1.15.el5.028stab047.1

Report message to a moderator

Re: Problem starting lstat match.Po no such file [message #25643 is a reply to message #25641]

Sat, 05 January 2008 17:59

vaverin
Messages: 708
Registered: September 2005

Senior Member

In this case could you please strace 'vzctl start'

Report message to a moderator

Re: Problem starting lstat match.Po no such file [message #25659 is a reply to message #25643]

Sun, 06 January 2008 11:50

JimL
Messages: 116
Registered: February 2007

Senior Member

OK problem solved. I think my disk is starting to go bad. Per the suggestion on another recent post, I unmounted the offending partition and did an fsck. I had to do it about 8 times to get a clean run. Doesn't bode well for that disk I'm afraid. It has pretty consistant read errors even after rewriting the block.

Anyway I rsynced that partition to another, mounted the new on and all is back to normal.

Thanks,
Jim.

Report message to a moderator

Previous Topic:	Using and Setting up NTP for OpenVZ Environment.
Next Topic:	SOLVED unloading iptables modules failed

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Dec 07 09:26:55 GMT 2025

Total time taken to generate the page: 0.12816 seconds