04-16-2010
If you're having I/O errors, you've got bigger problems than removing the bad files. That's not normal behavior. The disk may be dying.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I've been successfully running a daily cron script to backup certain things on my server but just recently I started getting input/output errors for everything. For each directory the script tries to backup I now get this:
cp: accessing `/mnt/backup/**dir**/': Input/output error (8 Replies)
Discussion started by: JPigford
8 Replies
2. AIX
Hello,
I encountered a never-seen-before error message soon after the extension of a file system on an AIX 5.2:
$ sudo chfs -a size=+1G /filesystemtest
v3fshelper: /dev/lvfilesystemtest: There is an input or output error.
No error reported by errpt, file system correctly extended.
Can... (2 Replies)
Discussion started by: padawan75
2 Replies
3. Shell Programming and Scripting
hello,
Any suggestion on how to prevent Standard output and Standard Error to window? (3 Replies)
Discussion started by: katrvu
3 Replies
4. Shell Programming and Scripting
Hi
I have a script and its execution takes 40 - 60 minutes. The script is run on the console window of the machine. Script execution should not be broken by running ctrl-C under any circumstances. Is there a way to lock the window from any user input (ctrl-C in fact) till the end of the script... (3 Replies)
Discussion started by: aoussenko
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I want to check a particular word is in standard error output or not. Can I acheive it in single command?
For example,
Delete file_name 2>error.log
cat error.log
Output:
XXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXX
Successfully deleted
XXXXXXXXXXXXXXXXX
where delete is... (2 Replies)
Discussion started by: poova
2 Replies
6. Shell Programming and Scripting
Hi,
I have two files , one file with data file with attributes that need to be sent to another file to generate a predefined format.
Example:
File.txt
AP|{SSHA}VEEg42CNCghUnGhCVg==
APVG3|{SSHA}XK|"password"
AP3|{SSHA}XK|"This is test"
....
etc
---------
test.sh has... (1 Reply)
Discussion started by: hudson03051nh
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am facing issue while using scp. Source & target machines are Linux & HP-UX respectively.
On target machine, if I fire the following command, I get error:
Now if I try scp on another file, which is on the same source machine, it works fine.
All directories and subdirectories... (2 Replies)
Discussion started by: Technext
2 Replies
8. Shell Programming and Scripting
Hi, i have the below code that will compare the value from 2 variables:
./wlst.sh JMSmon.py > out.dat
w=`sed -e 's/\(.*!\)\(.*\)\(, Queue.*$\)/\2/' out.dat | awk '/'$1'/{n=0;{print $n}}'|head -n 1`
if
then
x=`sed -e 's/\(.*!\)\(.*\)\(, Queue.*$\)/\2/' out.dat | awk '/'$1'/{n=2;next}n{print... (2 Replies)
Discussion started by: scripter123
2 Replies
9. AIX
Hi Folks,
Any system admin did provide AIX file system control to prevent user/ admin accidentally remove database files ?
Thanks. (4 Replies)
Discussion started by: ckwan
4 Replies
10. Red Hat
Hi issue with red hat and san.
I had a LUN shared to me from an oracle storage
I am able to see it and the size.
~]# multipath -ll
mpathe (3600144f0e984617b00005b466bd70014) dm-3 SUN,ZFS Storage 7430
size=10T features='0' hwhandler='0' wp=rw
|-+- policy='round-robin 0' prio=1... (0 Replies)
Discussion started by: goya
0 Replies
BAD144(8) System Manager's Manual BAD144(8)
NAME
bad144 - read/write DEC standard 144 bad sector information
SYNOPSIS
bad144 disktype disk [ sno [ bad ... ] ]
DESCRIPTION
Bad144 can be used to inspect the information stored on a disk that is used by the disk drivers to implement bad sector forwarding. The
format of the information is specified by DEC standard 144, as follows.
The bad sector information is located in the first 5 even numbered sectors of the last track of the disk pack. There are five identical
copies of the information, described by the dkbad structure. Only the first of these copies is used.
Replacement sectors are allocated starting with the first sector before the bad sector information and working backwards towards the begin-
ning of the disk. A maximum of 126 bad sectors can be supported. The position of the bad sector in the bad sector table determines which
replacement sector it corresponds to.
The bad sector information and replacement sectors are conventionally only accessible through the ``h'' file system partition of the disk.
If that partition is used for a file system, the user is responsible for making sure that it does not overlap the bad sector information or
any replacement sectors.
The bad sector structure is as follows:
struct dkbad {
long bt_csn; /* cartridge serial number */
u_short bt_mbz; /* unused; should be 0 */
u_short bt_flag; /* -1 => alignment cartridge */
struct bt_bad {
u_short bt_cyl; /* cylinder number of bad sector */
u_short bt_trksec; /* track and sector number */
} bt_bad[MAXBAD];
};
Unused slots in the bt_bad array are filled with all bits set, a putatively illegal value. MAXBAD (in <sys/dkbad.h>) may be tuned locally
to reduce the space required to hold the bad-sector file in memory. It may not be greater than 126, which uses the whole disk sector. Bad
sectors past MAXBAD may be included by the formatter, but replacement sectors will not be used until MAXBAD is increased.
Bad144 is invoked by giving a device type (e.g. rk07, rm03, rm05, etc.), and a device name (e.g. hk0, hp1, etc.). It reads the first sec-
tor of the last track of the corresponding disk and prints out the bad sector information. It may also be invoked giving a serial number
for the pack and a list of bad sectors, and will then write the supplied information onto the same location. Note, however, that bad144
does not arrange for the specified sectors to be marked bad in this case. This option should only be used to restore known bad sector
information which was destroyed.
New bad sectors can be added by running the standard DEC formatter in section ``bad.''
SEE ALSO
badsect(8)
BUGS
Not all drivers support bad-sector forwarding on the PDP-11.
It should be possible to both format disks on-line under UNIX and to change the bad sector information, marking new bad sectors, without
running a standalone program.
The bootstrap drivers used to boot the system do not understand bad sectors or handle ECC errors. This means that none of these errors can
occur when reading the file /unix to boot. Sector 0 of the disk drive and the file /boot in the root file system of that drive must also
not have any of these errors in it.
The drivers that write a system core image on disk after a crash do not handle errors; thus the crash dump area must be free of errors and
bad sectors.
3rd Berkeley Distribution BAD144(8)