Sponsored Content
Full Discussion: File System inconsistency
Top Forums UNIX for Dummies Questions & Answers File System inconsistency Post 65544 by callitdctr on Monday 7th of March 2005 06:11:06 AM
Old 03-07-2005
MySQL

Dear All
Yesterday I posted a querry related to file systen inconsistency and as Mr perderabo suggested I used "fsck /usr" command and it worked.
The problem of short read can't be solved and resulted in some bad sectors in disk.
Thanks to Unix.com and Mr perderabo.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Disk inconsistency

Hi, it seems I've got an hw error on more than one device. I use an AIX 5.2. this is the problem desc. Description DISK OPERATION ERROR Probable Causes DASD DEVICE Failure Causes DISK DRIVE DISK DRIVE ELECTRONICS I wish to read the SYSLOG file, where is it ? tk (1 Reply)
Discussion started by: Carmen123
1 Replies

2. Ubuntu

packet inconsistency problem

Hello everyone, I was trying to install db2 on Ubuntu, but got messed up with manual installation and Synaptic. At the moment, I find myself with a filesystem where DB2 is NOT installed ( I removed it with a sudo rm :o ) and with Synaptic still flagging db2exc as installed. The problem is that... (1 Reply)
Discussion started by: clalfa
1 Replies

3. HP-UX

Backspace stty inconsistency

I have this in my .profile: stty erase `tput kbs` which sets erase to ^H for a vt and ^? for an xterm. This has been fine up until now on all systems whether I login using a vt terminal emulator or an xterm. On this new system though, if I log in directly using an xterm, backspace doesn't... (1 Reply)
Discussion started by: Runrig
1 Replies

4. Shell Programming and Scripting

Variable value inconsistency on BASH and CSH

May God never give you the bane of working on Solaris. Now, I am trying to run this simple shell script: #!/bin/sh input="a b c" data="123" while read eachline do data="$data$eachline" done << EOF $(echo "$input") EOF... (2 Replies)
Discussion started by: pavanlimo
2 Replies

5. Shell Programming and Scripting

'find' command inconsistency

I am seeing a strange behavior of the 'find' command on AIX. As you can see, the find command sometimes finds the file and sometimes does not based on how many characters I specified between the wildcards. I know all of these issues can be resolved by using double quotes like "*est*". But I... (3 Replies)
Discussion started by: soleil4716
3 Replies

6. UNIX for Dummies Questions & Answers

Inconsistency between passwd and group

Hi, I have a passwd file with 3 users belonging to the the root group (gid=0), but the group file does not list these users as members of the root group? Shoud I be worried and apart from manually changing it, how can it be remediated? thx Norgaard (1 Reply)
Discussion started by: Norgaard
1 Replies

7. Red Hat

file system inconsistency

here in one of the server the lvol4 is having 20G and used space is 181M but it showing 98% used kindly advice any one can i run fsck -y after unmounted that lvol4 /dev/mapper/vg01-lvol4 20G 19G 418M 98% /var/opt/fedex aymara.emea $ du -sh /var/opt/fedex/... (3 Replies)
Discussion started by: venikathir
3 Replies

8. Solaris

VCS Crashing due to inconsistency in opt (managed by VxvM)

We have a Sun Server running Solaris 10 and Veritas Cluster Server. The RAID Volumes in the Server (/ , swap, opt, var, usr) are managed by VxVm and UFS is grown on all these volumes. Lately the system has been crashing due to an inconsistency in the opt filesystem. Upon reboot we did a fsck on... (1 Reply)
Discussion started by: aji1729
1 Replies

9. Solaris

Svccfg listprop, inconsistency in service property

hi all, Please see below -> bash-3.2# svccfg svc:> select network/http svc:/network/http> select apache2 svc:/network/http:apache2> listprop httpd application httpd/stability astring Evolving httpd/ssl boolean true ... (0 Replies)
Discussion started by: javanoob
0 Replies

10. Linux

Inconsistency with parallel run

Hi All, I am running a parallel processing on aggregating a file. I am splitting the process into 7 separate parallel process and processing the same input file and the process will do the same for each 7 run. The issue I am having is for some reason the 1st parallel processes complete first... (7 Replies)
Discussion started by: arunkumar_mca
7 Replies
FSCK.FAT(8)                                                   System Manager's Manual                                                  FSCK.FAT(8)

NAME
fsck.fat - check and repair MS-DOS filesystems SYNOPSIS
fsck.fat [OPTIONS] DEVICE DESCRIPTION
fsck.fat verifies the consistency of MS-DOS filesystems and optionally tries to repair them. The following filesystem problems can be corrected (in this order): * FAT contains invalid cluster numbers. Cluster is changed to EOF. * File's cluster chain contains a loop. The loop is broken. * Bad clusters (read errors). The clusters are marked bad and they are removed from files owning them. This check is optional. * Directories with a large number of bad entries (probably corrupt). The directory can be deleted. * Files . and .. are non-directories. They can be deleted or renamed. * Directories . and .. in root directory. They are deleted. * Bad filenames. They can be renamed. * Duplicate directory entries. They can be deleted or renamed. * Directories with non-zero size field. Size is set to zero. * Directory . does not point to parent directory. The start pointer is adjusted. * Directory .. does not point to parent of parent directory. The start pointer is adjusted. * Start cluster number of a file is invalid. The file is truncated. * File contains bad or free clusters. The file is truncated. * File's cluster chain is longer than indicated by the size fields. The file is truncated. * Two or more files share the same cluster(s). All but one of the files are truncated. If the file being truncated is a directory file that has already been read, the filesystem check is restarted after truncation. * File's cluster chain is shorter than indicated by the size fields. The file is truncated. * Clusters are marked as used but are not owned by a file. They are marked as free. Additionally, the following problems are detected, but not repaired: * Invalid parameters in boot sector * Absence of . and .. entries in non-root directories When fsck.fat checks a filesystem, it accumulates all changes in memory and performs them only after all checks are complete. This can be disabled with the -w option. OPTIONS
-a Automatically repair the filesystem. No user intervention is necessary. Whenever there is more than one method to solve a problem, the least destructive approach is used. -A Use Atari variation of the MS-DOS filesystem. This is default if fsck.fat is run on an Atari, then this option turns off Atari format. There are some minor differences in Atari format: Some boot sector fields are interpreted slightly different, and the special FAT entries for end-of-file and bad cluster can be different. Under MS-DOS 0xfff8 is used for EOF and Atari employs 0xffff by default, but both systems recognize all values from 0xfff8...0xffff as end-of-file. MS-DOS uses only 0xfff7 for bad clusters, where on Atari values 0xfff0...0xfff7 are for this purpose (but the standard value is still 0xfff7). -b Make read-only boot sector check. -c PAGE Use DOS codepage PAGE to decode short file names. By default codepage 437 is used. -d PATH Delete the specified file. If more than one file with that name exist, the first one is deleted. This option can be given more than once. -f Salvage unused cluster chains to files. By default, unused clusters are added to the free disk space except in auto mode (-a). -l List path names of files being processed. -n No-operation mode: non-interactively check for errors, but don't write anything to the filesystem. -p Same as -a, for compatibility with other *fsck. -r Interactively repair the filesystem. The user is asked for advice whenever there is more than one approach to fix an inconsistency. This is the default mode and the option is only retained for backwards compatibility. -t Mark unreadable clusters as bad. -u PATH Try to undelete the specified file. fsck.fat tries to allocate a chain of contiguous unallocated clusters beginning with the start cluster of the undeleted file. This option can be given more than once. -v Verbose mode. Generates slightly more output. -V Perform a verification pass. The filesystem check is repeated after the first run. The second pass should never report any fixable errors. It may take considerably longer than the first pass, because the first pass may have generated long list of modifications that have to be scanned for each disk read. -w Write changes to disk immediately. -y Same as -a (automatically repair filesystem) for compatibility with other fsck tools. EXIT STATUS
0 No recoverable errors have been detected. 1 Recoverable errors have been detected or fsck.fat has discovered an internal inconsistency. 2 Usage error. fsck.fat did not access the filesystem. FILES
fsck0000.rec, fsck0001.rec, ... When recovering from a corrupted filesystem, fsck.fat dumps recovered data into files named 'fsckNNNN.rec' in the top level directory of the filesystem. BUGS
Does not create . and .. files where necessary. Does not remove entirely empty directories. Should give more diagnostic messages. Undeleting files should use a more sophisticated algorithm. SEE ALSO
fatlabel(8) mkfs.fat(8) HOMEPAGE
The home for the dosfstools project is its GitHub project page <https://github.com/dosfstools/dosfstools>. AUTHORS
dosfstools were written by Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>, Roman Hodek <Roman.Hodek@informatik.uni-erlangen.de>, and others. The current maintainer is Andreas Bombe <aeb@debian.org>. dosfstools 4.1 2015-04-16 FSCK.FAT(8)
All times are GMT -4. The time now is 03:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy