09-14-2005
Quote:
Originally Posted by Perderabo
I hope that no one is running "fsck -y" on a mounted filesystem. Yes, I would expect this result all the time if the filesystem is mounted.
Agreed. However we did have a post the other week about someone who had done 'rm /dev/*'
![EEK! Smilie](https://www.unix.com/images/smilies/eek.gif)
so you never know.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Once in a while, I would think it advisable to run fsck -y to check the disk.
Should I sign in as su or sudo?
What is the difference and which is preferred?
Thank you in Advance! (4 Replies)
Discussion started by: rpatrick
4 Replies
2. UNIX for Dummies Questions & Answers
I want to use fsck to check and repair my linux system. When I use this command, what do I need to pay attention to or what should I do to make job running successfully. Thanks for your inputs for a newbie. (3 Replies)
Discussion started by: duke0001
3 Replies
3. UNIX for Dummies Questions & Answers
hy guys
I got a ques
I cant acess root, i tried to fsck it, but gets errors to read file systems. What steps do you take to recover the host before you see if there is any data corruption on the root drive?
Regards
Charneet (1 Reply)
Discussion started by: charneet
1 Replies
4. Solaris
Hello
I am getting this in dmesg:
/mount1: unexpected free inode 1262865, run fsck(1M) -o f
What are the options I should use with fsck?
thanks (2 Replies)
Discussion started by: melanie_pfefer
2 Replies
5. UNIX for Dummies Questions & Answers
i want to know what does it mean by doing a consistentcy check fsck on a disk and why journaling filesystems dont need to do it
and what is meant by disk is in a consistent state when writing because entries are recorded in a journal and then to the metadata and then removed from journal (1 Reply)
Discussion started by: farhan_t49
1 Replies
6. UNIX for Dummies Questions & Answers
Hello
I own a SPARC Ultra 10 workstation (standalone) and when issuing the fsck command I get the following output on fs C0t0d0s7:
Phase 1 (checks blocks and sizes):
dada warning: /pci@lf;0/pci@1, 1/ide@3/dad@0,0(dad1): ATA Transport failed:reason, `incomplete'>
Uncorrectable data... (2 Replies)
Discussion started by: tjwops
2 Replies
7. Solaris
What can I fix this issue? I have ran below commands but everything is same.:confused:
WARNING: Last shutdown is later than time on time-of-day chip: check date.
The / file system (/dev/rdsk/c1t0d0s0) is being checked
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 Replies
8. UNIX for Advanced & Expert Users
unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0)
--------------------------------------------------------------------------------
What can I fix this issue? I have ran below commands but everything is same.
WARNING: Last shutdown is later than time... (2 Replies)
Discussion started by: VijayPuttu
2 Replies
9. Solaris
Hi,
When we are running fsck in vxvm FS within few sec it will completed even if data is more than 500GB or in TB also.
compare to UFS FS in that it will take more time compare with vxvm.UFS check FS in block level. & then vvxm on where its checking the FS.
Please explain. (1 Reply)
Discussion started by: tiger09
1 Replies
10. Solaris
Dear all,
solaris version
--------------------
Oracle Solaris 10 9/10 s10s_u9wos_14a SPARC
Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
Assembled 11 August 2010
-bash-3.2$ uname -a
SunOS nblabsvr 5.10 Generic_144488-08 sun4u sparc SUNW,SPARC-Enterprise
... (5 Replies)
Discussion started by: ossupport55
5 Replies
LEARN ABOUT LINUX
mounted
mounted(7) Miscellaneous Information Manual mounted(7)
NAME
mounted - event signalling that a filesystem has been mounted
SYNOPSIS
mounted DEVICE=DEVICE MOUNTPOINT=MOUNTPOINT TYPE=TYPE OPTIONS=OPTIONS [ENV]...
DESCRIPTION
The mounted event is generated by the mountall(8) daemon after it has mounted a filesystem. mountall(8) will wait for all services started
by this event to be running, all tasks started by this event to have finished and all jobs stopped by this event to be stopped before con-
tinuing with other filesystems.
The DEVICE, MOUNTPOINT, TYPE and OPTIONS environment variables contain the values of the fstab(5) fields for this mountpoint.
EXAMPLE
A tool that should be run after mounting the /tmp filesystem might use:
start on mounted MOUNTPOINT=/tmp
task
SEE ALSO
mounting(7) virtual-filesystems(7) local-filesystems(7) remote-filesystems(7) all-swaps(7) filesystem(7)
mountall 2009-12-21 mounted(7)