LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 07-22-2009, 12:33 AM   #1
windstory
Member
 
Registered: Nov 2008
Posts: 486

Rep: Reputation: 36
at shutting down, rm commands occurs....


My box is centos x86 5.3.
I just now shut down my box, then rm commands occurs like atached picture.

Is this removing my system?
Attached Thumbnails
Click image for larger version

Name:	2009-07-22_132646.jpg
Views:	22
Size:	119.5 KB
ID:	1069  
 
Old 07-22-2009, 01:32 AM   #2
swapnshukla
LQ Newbie
 
Registered: Dec 2006
Posts: 13

Rep: Reputation: 3
This looks like that user issuing shutdown command is not eligible to work with /var directory (Read Only file system)

Or
There might be a chance of your /var file systems curruption so you can try running fsck to the /var and then do to shutdown.

Activities performed with rm during shutdown are normal but finding Read Only Filesystem is not.
 
Old 07-22-2009, 01:39 AM   #3
windstory
Member
 
Registered: Nov 2008
Posts: 486

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by swapnshukla View Post
This looks like that user issuing shutdown command is not eligible to work with /var directory (Read Only file system)

Or
There might be a chance of your /var file systems curruption so you can try running fsck to the /var and then do to shutdown.

Activities performed with rm during shutdown are normal but finding Read Only Filesystem is not.
swapnshukla,

Thnaks for your kind explanation.

Now after shutting down, system is on booting.
And system shows,

Code:
/dev/volGroup00/myhard01 contains a filr system with errors. check forced. 
... -12.7%
I want to know what this is.
 
Old 07-22-2009, 04:50 AM   #4
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Debian
Posts: 8,576
Blog Entries: 31

Rep: Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195
Hello windstory
Quote:
Originally Posted by swapnshukla View Post
This looks like that user issuing shutdown command is not eligible to work with /var directory (Read Only file system)

Or
There might be a chance of your /var file systems curruption so you can try running fsck to the /var and then do to shutdown.

Activities performed with rm during shutdown are normal but finding Read Only Filesystem is not.
The shutdown command can only be run with root privileges:
Code:
c@CW8:~$ shutdown now
shutdown: Need to be root
All the directories listed in the rm error messages are not on the /var/ file system; they are on temporary file systems (tmpfs) in memory, mounted in the /var file system
Code:
c@CW8:~$ df -t tmpfs
Filesystem           1K-blocks      Used Available Use% Mounted on
varrun                 1684452       236   1684216   1% /var/run
varlock                1684452         4   1684448   1% /var/lock
[snip]
I guess it's normal to try and remove these things during shutdown. The issue is not that any harm is being done to the /var/run and /var/lock file systems (they disappear when the power is off) but that the daemons mentioned in the error messages are not able to shut down normally. They may or may not continue shutting down normally after the rm error, depending on how their shutdown (kill) scripts are programmed.

I have no idea how /var/run and /var/lock have become read-only. Are there any clues in the /var/log files like kern.log, daemon.log, messages and syslog?

Best

Charles
 
Old 07-22-2009, 04:58 AM   #5
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Debian
Posts: 8,576
Blog Entries: 31

Rep: Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195
Hello windstory
Quote:
Originally Posted by windstory View Post
Now after shutting down, system is on booting.
And system shows,

Code:
/dev/volGroup00/myhard01 contains a filr system with errors. check forced. 
... -12.7%
I want to know what this is.
As it says, the system has detected error(s) on the file system on /dev/volGroup00/myhard01. Could be glitchy transients that the check is able to fix or could be a hardware problem.

Assuming the check works well enough to mount that file system, it would be prudent to backup its files and test the backup. When you get that sort of error it may "go away" but more often gets worse.

What type of file system is it and where do you mount it?

Best

Charles
 
Old 07-22-2009, 06:50 AM   #6
windstory
Member
 
Registered: Nov 2008
Posts: 486

Original Poster
Rep: Reputation: 36
Quote:
Originally Posted by catkin View Post
Hello windstory As it says, the system has detected error(s) on the file system on /dev/volGroup00/myhard01. Could be glitchy transients that the check is able to fix or could be a hardware problem.

Assuming the check works well enough to mount that file system, it would be prudent to backup its files and test the backup. When you get that sort of error it may "go away" but more often gets worse.

What type of file system is it and where do you mount it?

Best

Charles
catkin,

Thanks for your kind replies.

My system is boot up after long time checking.
And now I don,t know what to do.

I am affraid what's wrong or bad.

If possible, please let me know how I can check my system,s health.
 
Old 07-22-2009, 08:03 AM   #7
catkin
LQ 5k Club
 
Registered: Dec 2008
Location: Tamil Nadu, India
Distribution: Debian
Posts: 8,576
Blog Entries: 31

Rep: Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195Reputation: 1195
Hello windstory
Quote:
Originally Posted by windstory View Post
I am affraid what's wrong or bad.

If possible, please let me know how I can check my system,s health.
Take a backup, if your data is important. That's first priority.

Then you could answer my requests for more information to try and understand what has gone wrong. Probably your disk hardware is failing but it could be file system corruption caused by memory errors or motherboard problems such as hard disk controller problems.

You need to gather information to try and identify the likely problem. Once you have backed up your data then you can be more relaxed about it because you have less to lose.

Best

Charles
 
Old 07-23-2009, 12:43 AM   #8
swapnshukla
LQ Newbie
 
Registered: Dec 2006
Posts: 13

Rep: Reputation: 3
Thumbs up Thanks

[QUOTE=catkin;3616130]Hello windstory The shutdown command can only be run with root privileges:
Code:
c@CW8:~$ shutdown now
shutdown: Need to be root
All the directories listed in the rm error messages are not on the /var/ file system; they are on temporary file systems (tmpfs) in memory, mounted in the /var file system
Code:
c@CW8:~$ df -t tmpfs
Filesystem           1K-blocks      Used Available Use% Mounted on
varrun                 1684452       236   1684216   1% /var/run
varlock                1684452         4   1684448   1% /var/lock
[snip]

Charles thanks for the knowledge update as mentioning shutdown issuing from a non privilege user was my oversight but really tempfs details I have been updated with as I was not aware of.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
process status when interrupt occurs? Felicia23 Linux - Kernel 1 01-28-2009 05:09 AM
a network warning occurs when log in cricketlong Linux - Networking 6 12-19-2008 04:40 AM
Unwanted shutdown occurs rushenas Linux - Hardware 2 08-08-2008 05:08 AM
What happens when a segmentation fault occurs rob_of_owensboro Programming 5 01-12-2006 04:21 PM
finding the mode(# which occurs most often) of a given vector mshinska Programming 3 11-21-2005 08:14 PM


All times are GMT -5. The time now is 11:00 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration