03-28-2014
Quote:
Originally Posted by
bakunin
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
Thanks. I wil run a fsck manually....
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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... (3 Replies)
Discussion started by: DGoubine
3 Replies
2. UNIX for Dummies Questions & Answers
How do I configure my workstation (Solaris 9) to restart and perform any check disk automatically if there is a power failure?
Thanks. (1 Reply)
Discussion started by: here2learn
1 Replies
3. Solaris
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"... (5 Replies)
Discussion started by: aribault
5 Replies
4. Shell Programming and Scripting
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 Replies)
Discussion started by: pchangba
5 Replies
5. SCO
After System power get failed
File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies
6. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
7. Solaris
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 (7 Replies)
Discussion started by: doudou2012
7 Replies
8. Shell Programming and Scripting
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... (7 Replies)
Discussion started by: Geeta Yadav
7 Replies
LEARN ABOUT NETBSD
fsck_msdos
FSCK_MSDOS(8) BSD System Manager's Manual FSCK_MSDOS(8)
NAME
fsck_msdos -- DOS/Windows (FAT) filesystem consistency checker
SYNOPSIS
fsck_msdos -p [-f] filesystem ...
fsck_msdos [-fny] [-x snap-backup] filesystem ...
DESCRIPTION
The fsck_msdos utility verifies and repairs FAT filesystems (more commonly known as DOS filesystems).
The first form of fsck_msdos preens the specified filesystems. It is normally started by fsck(8) run from /etc/rc during automatic reboot,
when a FAT filesystem is detected. When preening file systems, fsck_msdos will fix common inconsistencies non-interactively. If more seri-
ous problems are found, fsck_msdos does not try to fix them, indicates that it was not successful, and exits.
The second form of fsck_msdos checks the specified file systems and tries to repair all detected inconsistencies, requesting confirmation
before making any changes.
The options are as follows:
-f This option is ignored by fsck_msdos, and is present only for compatibility with programs that check other file system
types for consistency, such as fsck_ffs(8).
-n Causes fsck_msdos to assume no as the answer to all operator questions, except ``CONTINUE?''.
-p Preen the specified filesystems.
-x snap-backup Use a snapshot with snap-backup as backup to check a read-write mounted filesystem. Must be used with -n. See fss(4) for
more details. The point is to check an internally-consistent version of the filesystem to find out if it is damaged; on
failure one should unmount the filesystem and repair it.
-y Causes fsck_msdos to assume yes as the answer to all operator questions.
SEE ALSO
fss(4), fsck(8), fsck_ffs(8), mount_msdos(8)
BUGS
fsck_msdos is still under construction.
BSD
April 11, 2010 BSD