07-30-2013
Quote:
Originally Posted by
manivanm
While a tar file was created, the file system got full and there was no message on the tar failure.
"tar" will
always issue an error message (as well as a non-zero exit code) in such a case. There could only be "no error message" because it was redirected to "/dev/null". Either the exit code or the error message should have been watched in this case.
Quote:
Originally Posted by
manivanm
Then the system was shut down and the administrator says because the file system was full the shut down procedure corrupted the file system.
At first sight i think this is hardly believable. I do not know the shutdown procedure of this specific system (which might be heavily customized to produce such results), but any
normal shutdown-procedure will not bear such results.
Whats more, it happens all the time that filesystems become full. Why should a shutdown-procedure - any normal action a system undertakes, for that matter - corrupt a filesystem? Linux would not be the stable server operating system it is if
any normal operation would cause filesystems - full or not - to become corrupted.
To be honest, lacking any further evidence, i think the admin is telling bullshit. Let him explain what
exactly has happened and post it here if you can't prove//disprove it yourself.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
All of a sudden I landed in a strange problem.
I was working with my C source code in vi editor. I did a wq! and
when reopened, the file is full of "data".. I mean the text contents are gone!!.
I believe this is a file corruption. I have tried the -r option with vi, but no success.
... (5 Replies)
Discussion started by: shibz
5 Replies
2. UNIX for Dummies Questions & Answers
Hi friends,
In my case, there are serveral PCs running Linux in a LAN.
I would like to to mount the directory /A_river of machine-A to the file system of another machine machine-B so that I can access files in that directory.
I do not know how to do this. The situation is complicated by... (2 Replies)
Discussion started by: cy163
2 Replies
3. UNIX for Advanced & Expert Users
Dear Peoples
I am using the following command to transfer the files inbetween two servers, i am using this command in a crontab for doing it in every 1 hour on all days.
rsync --stats --archive --verbose --compress --force --rsh=ssh --exclude-from=/root/cfg/mkt_scn.exclude... (1 Reply)
Discussion started by: thameema
1 Replies
4. AIX
Hi All,
We are facing the problem of file system corruption on DS8300,we have done very much effort to find out the root cause of problem but we still not get any success, we have AIX 5.3 OS installed on system with latest patches, we have upgraded HBA firmwares, DS8300 firmware, System... (5 Replies)
Discussion started by: m_raheelahmed
5 Replies
5. Solaris
I have a solaris 5.6 on which oracle is installed.
we have an alert file
alert_net1.log
now whenever any datacorruption happens we get the file id and block id in the above file.
through this file and block id , we try to find out which table is corrupted and then try to... (1 Reply)
Discussion started by: asalman.qazi
1 Replies
6. SCO
After System power get failed
File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies
7. Emergency UNIX and Linux Support
Today when someone was using Sun Identity Manager to modify a directory managed by Sun Directory Server Enterprise Edition (DSEE 6.3) IDM spit out an object class violation error (I verified that the input data was valid). It also corrupted the directory to the point where I can't even get dsadm to... (7 Replies)
Discussion started by: ilikecows
7 Replies
8. UNIX for Advanced & Expert Users
Hi,
could any one tell is there any test-suite or any idea How to do data corruption validation testing, means there is no any data corruption ?
Regards
Manish (1 Reply)
Discussion started by: manish_tcs_hp
1 Replies
9. Shell Programming and Scripting
We would be migrating UNIX file system to Linux file system.
We do have many directory and sub directories with files.
after migrating unix to linux file system , i want to make sure all the files has been copied ? What would be the best approach to validate directory ,sub-directory and file... (1 Reply)
Discussion started by: balajikalai
1 Replies
10. Solaris
Hello,
I got into a wired state on one of solaris 10 server. When I noticed that server is having some issue, I found that there were dumpadm.conf entries in /etc/shadow and real entries were wiped of. Probably somebody fat fingers.
I was able to boot into failsafe, break SVM mirror, copied... (25 Replies)
Discussion started by: solaris_1977
25 Replies
LEARN ABOUT SUNOS
shutdown
shutdown(1M) System Administration Commands shutdown(1M)
NAME
shutdown - shut down system, change system state
SYNOPSIS
/usr/sbin/shutdown [-y] [-g grace-period] [-i init-state] [message]
DESCRIPTION
shutdown is executed by the super user to change the state of the machine. In most cases, it is used to change from the multi-user state
(state 2) to another state.
By default, shutdown brings the system to a state where only the console has access to the operating system. This state is called single-
user.
Before starting to shut down daemons and killing processes, shutdown sends a warning message and, by default, a final message asking for
confirmation. message is a string that is sent out following the standard warning message "The system will be shut down in ..." If the
string contains more than one word, it should be contained within single (') or double (") quotation marks.
The warning message and the user provided message are output when there are 7200, 3600, 1800, 1200, 600, 300, 120, 60, and 30 seconds
remaining before shutdown begins. See EXAMPLES.
System state definitions are:
state 0 Stop the operating system.
state 1 State 1 is referred to as the administrative state. In state 1 file systems required for multi-user operations are mounted,
and logins requiring access to multi-user file systems can be used. When the system comes up from firmware mode into state
1, only the console is active and other multi-user (state 2) services are unavailable. Note that not all user processes are
stopped when transitioning from multi-user state to state 1.
state s, S State s (or S) is referred to as the single-user state. All user processes are stopped on transitions to this state. In the
single-user state, file systems required for multi-user logins are unmounted and the system can only be accessed through
the console. Logins requiring access to multi-user file systems cannot be used.
state 5 Shut the machine down so that it is safe to remove the power. Have the machine remove power, if possible. The rc0 procedure
is called to perform this task.
state 6 Stop the operating system and reboot to the state defined by the initdefault entry in /etc/inittab. The rc6 procedure is
called to perform this task.
OPTIONS
-y Pre-answer the confirmation question so the command can be run without user intervention.
-g grace-period Allow the super user to change the number of seconds from the 60-second default.
-i init-state If there are warnings, init-state specifies the state init is to be in. By default, system state `s' is used.
EXAMPLES
Example 1: Using shutdown
In the following example, shutdown is being executed on host foo and is scheduled in 120 seconds. The warning message is output 2 minutes,
1 minute, and 30 seconds before the final confirmation message.
example# shutdown -i S -g 120 "===== disk replacement ====="
Shutdown started. Tue Jun 7 14:51:40 PDT 1994
Broadcast Message from root (pts/1) on foo Tue Jun 7 14:51:41...
The system will be shut down in 2 minutes
===== disk replacement =====
Broadcast Message from root (pts/1) on foo Tue Jun 7 14:52:41...
The system will be shut down in 1 minutes
===== disk replacement =====
Broadcast Message from root (pts/1) on foo Tue Jun 7 14:53:41...
The system will be shut down in 30 seconds
===== disk replacement =====
Do you want to continue? (y or n):
FILES
/etc/inittab controls process dispatching by init
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
boot(1M), halt(1M), init(1M), killall(1M), reboot(1M), ufsdump(1M), init.d(4), inittab(4), nologin(4), attributes(5)
NOTES
When a system transitions down to the S or s state, the /etc/nologin file (see nologin(4)) is created. Upon subsequent transition to state
2 (multi-user state), this file is removed by a script in the /etc/rc2.d directory.
SunOS 5.10 9 May 2001 shutdown(1M)