Sponsored Content
Full Discussion: Fsck question
Operating Systems Solaris Fsck question Post 302894191 by hicksd8 on Monday 24th of March 2014 09:59:23 AM
Old 03-24-2014
What you describe is not unusual. Over long periods of time a filesystem may well develop inconsistencies that fsck will pick up and correct. However, even if these inconsistencies are not corrected but the filesystem is mounted and dismounted in an orderly manner, the filesystem remains usable. The 'flags' that fsck -m looks at are indicating that the filesystem was dismounted properly and so could be remounted okay.

However, a fsck check still finds the filesystem needs fixing.

Unreliable FC connections can be a nightmare and give rise to filesystem corruption.

Many fsck implementations support a '-o full' option which will check every last thing on a filesystem although it takes a very long time to run (depending on the filesystem size, of course). I think the Solaris fsck supports this too (but it is often undocumented).

Hope that helps in some way.
These 2 Users Gave Thanks to hicksd8 For This Post:
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

fsck -y

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 Advanced & Expert Users

fsck with Linux

Hi, I'm running Red Hat 7.1 on an intel. After re-booting from a system crash, I am probpted to run fsck to repair filesystems manually with no options. For example, /: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (ie without -a or -p options) **Dropping you into a shell. ... (2 Replies)
Discussion started by: Breen
2 Replies

3. Solaris

fsck

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

4. UNIX for Dummies Questions & Answers

fsck - what should be done?

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

fsck run

Hi, Can anybody tell me that is it the command "fsck" can be run by the root account only? Thanks. (2 Replies)
Discussion started by: efang
2 Replies

6. UNIX for Dummies Questions & Answers

Fsck ques

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

7. Solaris

fsck -o

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

8. UNIX for Dummies Questions & Answers

about fsck

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

9. UNIX for Dummies Questions & Answers

Fsck error

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

10. Solaris

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.: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
SYSTEMD-FSCK@.SERVICE(8)				       systemd-fsck@.service					  SYSTEMD-FSCK@.SERVICE(8)

NAME
systemd-fsck@.service, systemd-fsck-root.service, systemd-fsck - File system checker logic SYNOPSIS
systemd-fsck@.service systemd-fsck-root.service /lib/systemd/systemd-fsck DESCRIPTION
systemd-fsck@.service and systemd-fsck-root.service are services responsible for file system checks. They are instantiated for each device that is configured for file system checking. systemd-fsck-root.service is responsible for file system checks on the root file system, but only if the root filesystem was not checked in the initramfs. systemd-fsck@.service is used for all other file systems and for the root file system in the initramfs. These services are started at boot if passno in /etc/fstab for the file system is set to a value greater than zero. The file system check for root is performed before the other file systems. Other file systems may be checked in parallel, except when they are on the same rotating disk. systemd-fsck does not know any details about specific filesystems, and simply executes file system checkers specific to each filesystem type (/sbin/fsck.*). This helper will decide if the filesystem should actually be checked based on the time since last check, number of mounts, unclean unmount, etc. If a file system check fails for a service without nofail, emergency mode is activated, by isolating to emergency.target. KERNEL COMMAND LINE
systemd-fsck understands these kernel command line parameters: fsck.mode= One of "auto", "force", "skip". Controls the mode of operation. The default is "auto", and ensures that file system checks are done when the file system checker deems them necessary. "force" unconditionally results in full file system checks. "skip" skips any file system checks. fsck.repair= One of "preen", "yes", "no". Controls the mode of operation. The default is "preen", and will automatically repair problems that can be safely fixed. "yes" will answer yes to all questions by fsck and "no" will answer no to all questions. SEE ALSO
systemd(1), fsck(8), systemd-quotacheck.service(8), fsck.btrfs(8), fsck.cramfs(8), fsck.ext4(8), fsck.fat(8), fsck.hfsplus(8), fsck.minix(8), fsck.ntfs(8), fsck.xfs(8) systemd 237 SYSTEMD-FSCK@.SERVICE(8)
All times are GMT -4. The time now is 05:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy