Power failure: file damage? Post: 302895040

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Power failure: file damage? Post 302895040 by bakunin on Friday 28th of March 2014 10:06:33 AM

03-28-2014

Registered User

Quote:

Originally Posted by raylier

But is it possible that there are damaged files I don't know of but can cause trouble later on?

Yes, there is a very remote chance of that having happened, but it is not at all likely.

Most Unix systems today use a "journaling filesystem" of some sort or other and these are quite robust when it comes to unexpected power loss.

At the startup a system will notice that a filesystem was not properly closed during the shutdown before in such a case and initiate a filesystem check. While older FSes would have a (ever diminishing) chance of such a check not being successful (SUNs sfs, for instance, was famous for the high rate of this happening) or some files being beyond repair modern FSes - and especially journaling FSes - run a very low risk in this regard. Usually you see something like "replaying log" during startup and the time that takes is barely noticeable.

I hope this helps.

bakunin

This User Gave Thanks to bakunin For This Post:

bakunin

View Public Profile for bakunin

Find all posts by bakunin

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Xstartup file failure - HELP !!

Hi, dear Experts ! I need some help, again. Earlier in my work I experienced that one script included in '/etc/dt/config/Xstartup' file caused some serious troubles. But this is another story. The point here is: I changed the script so that it worked again. But... After restart of...

2. UNIX for Dummies Questions & Answers

Restart on power failure

How do I configure my workstation (Solaris 9) to restart and perform any check disk automatically if there is a power failure? Thanks.

3. Solaris

Automatic reboot does not work after power failure

Hi all, I have a server SUN FUJITSU in solaris 10 ; result of uname -a is : SunOS MOBD1 5.10 Generic_118833-03 sun4us sparc FJSV,GPUZC-M I have configured the eeprom to auto-boot as usual and this automatic reboot does not work in case of power failure. I must type "boot" on the prompt "ok"...

4. Shell Programming and Scripting

writting a shell script to delete damage files

hi, I have 100 files say File1.mp3, File2.mp3 .......file100.mp3 i found that File1.mp3 to File50.mp3 are damaged. I want to delete the damaged files from the directory using sed with regex how can i do this. thanks

5. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode

6. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless.

7. Solaris

After power failure, SunFireV240 with SOLARIS 5.9 cannot start

SUNW, Sun Fire V240 Spare Sun OS Release 5.9 After a power failure we try to start the server We have the following messages: Thanks for your assistance

8. Shell Programming and Scripting

Failure of sftp send to log file

I want to transfer all details of sftp connection into a log file and spawn sftp $PCMSu@$FTP_LOC >> log_file is not working for me. Please suggest how to send the data to a log file that has all information if sftp connection is successful or not? Script that I am using: #!/usr/bin/expect...

LEARN ABOUT SUSE

startup

startup(7)						 Miscellaneous Information Manual						startup(7)

NAME

       startup - event signalling system startup

SYNOPSIS

       startup [ENV]...

DESCRIPTION

       The  startup event is generated by the Upstart init(8) daemon after it has completed its own initialisation and is the signal that the rest
       of the system may be started.

       Typically this will involve checking and mounting the partitions and drives that form the filesystem, loading drivers for connected devices
       and starting the X windowing system or other login environment.

       In the default Upstart configuration, the primary task run on the startup event is the /etc/init/rc-sysinit.conf job responsible for gener-
       ating the System V compatible runlevel(7) event.  See that page for a more detailed explanation of this process.

       Paradoxically there is currently no corresponding Upstart-native event signifying that the system is to be shutdown, only the System V com-
       patible runlevel 0 and runlevel 6 events provide this functionality.

EXAMPLE

       A service with no other dependencies run on startup might use:

	      start on startup

SEE ALSO

       runlevel(7) init(8)

Upstart 							    2009-07-09								startup(7)