03-07-2005
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
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT OPENDARWIN
badsect
BADSECT(8) BSD System Manager's Manual BADSECT(8)
NAME
badsect -- create files to contain bad sectors
SYNOPSIS
/etc/badsect bbdir sector ...
DESCRIPTION
Badsect makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which provides a for-
warding table for bad sectors to the driver; see bad144(8) for details. If a driver supports the bad blocking standard it is much preferable
to use that method to isolate bad blocks, since the bad block forwarding makes the pack appear perfect, and such packs can then be copied
with dd(1). The technique used by this program is also less general than bad block forwarding, as badsect can't make amends for bad blocks
in the i-list of file systems or in swap areas.
On some disks, adding a sector which is suddenly bad to the bad sector table currently requires the running of the standard DEC formatter.
Thus to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard badsect may be used to good
effect.
Badsect is used on a quiet file system in the following way: First mount the file system, and change to its root directory. Make a directory
BAD there. Run badsect giving as argument the BAD directory followed by all the bad sectors you wish to add. (The sector numbers must be
relative to the beginning of the file system, but this is not hard as the system reports relative sector numbers in its console error mes-
sages.) Then change back to the root directory, unmount the file system and run fsck(8) on the file system. The bad sectors should show up
in two files or in the bad sector files and the free list. Have fsck remove files containing the offending bad sectors, but do not have it
remove the BAD/nnnnn files. This will leave the bad sectors in only the BAD files.
Badsect works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block address is the
block containing bad sector and whose name is the bad sector number. When it is discovered by fsck it will ask ``HOLD BAD BLOCK ?'' A posi-
tive response will cause fsck to convert the inode to a regular file containing the bad block.
SEE ALSO
bad144(8), fsck(8), format(8)
DIAGNOSTICS
Badsect refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued if the block is
already in use.
BUGS
If more than one sector which comprise a file system fragment are bad, you should specify only one of them to badsect, as the blocks in the
bad sector files actually cover all the sectors in a file system fragment.
HISTORY
The badsect command appeared in 4.1BSD.
4th Berkeley Distribution June 5, 1993 4th Berkeley Distribution