11-17-2014
Fsck -n on mounted FS - how unreliable ?
greetings all, we had SAN bobbles recently and so I ran fsck against all local FS on all systems.
our domino servers present a moving set of alleged corruption, both JFS and JFS2 FS.
Am I playing whack-a-mole with special effects (i.e. false positives) produced by vigorous filesystem activity while I'm trying to scan it ? Or is this potentially real enough so it's worth taking outages to unmount FS, etc. ?
TIA
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. Solaris
OS: Solaris 5.8
Everytime I run fsck -y I get: FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX? yes
Do I need to run fsck with the backup superblock option or is there
some other option I should use. I have tried the format->analyze->read
option but that does not report any corrupt blocks.... (5 Replies)
Discussion started by: run_time_error
5 Replies
3. UNIX for Dummies Questions & Answers
I have a Solaris 7 box. We got a strange error in the syslog, which read as follows:
Nov 15 11:50:16 server-01 unix: NOTICE: free inode /mount1/8025691 had size 0x20d
I consulted with a fellow sysadmin, and he suggested running "fsck -N" on the filesystem in question without unmounting it. So I... (1 Reply)
Discussion started by: GKnight
1 Replies
4. 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
5. 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
6. 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
7. 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
8. Solaris
I am not able to boot into solaris. I am getting following message.
The / file system (/dev/rdsk/c0t0d0s0) is being checked.
Warning - Unable to repair the / filesystem. Run fsck manually(fsck -F ufs /dev/rdsk/c0t0d0s0).
I ran fsck manually but it didn't work.
Help from anyone would be... (1 Reply)
Discussion started by: likhitgatagat
1 Replies
9. 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
10. 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
LEARN ABOUT NETBSD
umount
UMOUNT(8) BSD System Manager's Manual UMOUNT(8)
NAME
umount -- unmount filesystems
SYNOPSIS
umount [-fvFR] [-t fstypelist] special | node
umount -a [-fvF] [-h host] [-t fstypelist]
DESCRIPTION
The umount command calls the unmount(2) system call to remove a special device or the remote node (rhost:path) from the filesystem tree at
the point node. If either special or node are not provided, the appropriate information is taken from the fstab(5) file.
The options are as follows:
-a All the currently mounted filesystems except the root are unmounted.
-f The filesystem is forcibly unmounted. Active special devices continue to work, but all other files return errors if further accesses
are attempted. The root filesystem cannot be forcibly unmounted.
-F Fake the unmount; perform all other processing but do not actually attempt the unmount. (This is most useful in conjunction with -v,
to see what umount would attempt to do).
-R Take the special | node argument as a path to be passed directly to unmount(2), bypassing all attempts to be smart about mechanically
determining the correct path from the argument. This option is incompatible with any option that potentially unmounts more than one
filesystem, such as -a, but it can be used with -f and/or -v. This is the only way to unmount something that does not appear as a
directory (such as a nullfs mount of a plain file); there are probably other cases where it is necessary.
-h host
Only filesystems mounted from the specified host will be unmounted. This option is implies the -a option and, unless otherwise spec-
ified with the -t option, will only unmount NFS filesystems.
-t fstypelist
Is used to indicate the actions should only be taken on filesystems of the specified type. More than one type may be specified in a
comma separated list. The list of filesystem types can be prefixed with ``no'' to specify the filesystem types for which action
should not be taken. For example, the umount command:
umount -a -t nfs,mfs
unmounts all filesystems of the type NFS and MFS, whereas the umount command:
umount -a -t nonfs,mfs
unmounts all file systems except those of type NFS and MFS.
-v Verbose, additional information is printed out as each filesystem is unmounted.
FILES
/etc/fstab filesystem table
SEE ALSO
unmount(2), fstab(5), mount(8)
HISTORY
A umount command appeared in Version 6 AT&T UNIX.
BSD
May 17, 2009 BSD