Sponsored Content
Full Discussion: File System inconsistency
Top Forums UNIX for Dummies Questions & Answers File System inconsistency Post 65464 by Perderabo on Saturday 5th of March 2005 09:12:55 AM
Old 03-05-2005
I'm not following all of this, but here are a few comments. Are you sure that /usr is mounted? Are you sure that you don't know the device name? It's not easy to find out that a file system is mounted without also obtaining the device name. For example, with the "df" command, the device name is the first field. You can just examine /etc/fstab to get the device name. But you should not actually need the device name. Modern versions of fsck will look it up in /etc/fstab. So simply:
fsck /usr
really should work.

Ideally you should find some way to umount /usr or arrange that it was never mounted prior to fsck. A boot cd (can linux really boot from a diskette?) would be a good option. You're right that running fsck on a mounted filesystem is very dangerous. This is because some of the data from that filesystem is sitting in buffer cache. When this cache is written out, it will intermix with the data written by fsck and scramble the filesystem. So you need to do the following sequence of commands:
sync
<wait 10 seconds or so>
fsck /usr
reboot -n

The first sync will flush out any changed data in / or any other mounted filesystems. You need to wait until the disk writes complete. Then run fsck.
Then immediately reboot without syncing. Also during this entire procedure, almost nothing else must be happening. It is relatively safe in single user mode. This is not completely safe, but your system is not usuable anyway, so it is what I would try. There is a risk of damaging other mounted filesystems. The first sync together with minimizing activity should mitigate this danger. If you decide to try it, please post back and let us know how it works.

However, even if this does work, you may not be home free. fsck may not be able to repair your disk. "attempt to read blocks from filesystem resulted in short read" make me think that your disk may be bad in a hardware sense. fsck cannot repair broken hardware.

Whether or not fsck seems to work, you must immediately do the "reboot -n". Good luck.
 

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
orte-clean(1)							     Open MPI							     orte-clean(1)

NAME
orte-clean - Cleans up any stale processes and files leftover from Open MPI jobs. SYNOPSIS
orte-clean [--verbose] mpirun --pernode [--host | --hostfile file] orte-clean [--verbose] OPTIONS
[-v | --verbose] This argument will run the command in verbose mode and print out the universes that are getting cleaned up as well as pro- cesses that are being killed. DESCRIPTION
orte-clean attempts to clean up any processes and files left over from Open MPI jobs that were run in the past as well as any currently running jobs. This includes OMPI infrastructure and helper commands, any processes that were spawned as part of the job, and any temporary files. orte-clean will only act upon processes and files that belong to the user running the orte-clean command. If run as root, it will kill off processes belonging to any users. When run from the command line, orte-clean will attempt to clean up the local node it is run from. When launched via mpirun, it will clean up the nodes selected by mpirun. EXAMPLES
Example 1: Clean up local node only. example% orte-clean Example 2: To clean up on a specific set of nodes specified on command line, it is recommended to use the pernode option. This will run one orte-clean for each node. example% mpirun --pernode --host node1,node2,node3 orte-clean To clean up on a specific set of nodes from a file. example% mpirun --pernode --hostfile nodes_file orte-clean Example 3: Within a resource managed environment like N1GE, SLURM, or Torque. The following example is from N1GE. First, we see that we have two nodes with two CPUs each. example% qsh -pe orte 4 example% mpirun -np 4 hostname node1 node1 node2 node2 Clean up all the nodes in the cluster. example% mpirun --pernode orte-clean Clean up a subset of the nodes in the cluster. example% mpirun --pernode --host node1 orte-clean SEE ALSO
orterun(1), orte-ps(1) 1.4.5 Feb 10, 2012 orte-clean(1)
All times are GMT -4. The time now is 05:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy