04-06-2010
Hi,
This basically happens when the file system is corrupted, please check the filesystem and the mountpoint ,i mean is the filesystem in question an isolated one from /.
umount and e2fsck would be the solution.How ever to prevent it from happening again ( only the read only mount) u may need to tweak a filesystem
run
tune2fs -e continue /dev/sda(name of the filesystem and not the mount point)
this would change the error behavior of the kernel code when errors are detected. There are three states
1] continue
2]remount-ro
3]panic
In all cases, a filesystem error will cause e2fsck to check the filesystem on the next boot.
to check what state of error behavior you filesystem is run
tune2fs -l filesystem|grep "error-behaviour"
10 More Discussions You Might Find Interesting
1. Programming
Every time I close a file that I opened for reading I get the following error: ”Memory fault(coredump)”. And, although it does not (I think) affect the overall process (I write another file based on the file I am reading); it is something I would rather not happen. I don't know why this is... (1 Reply)
Discussion started by: ALTRUNVRSOFLN
1 Replies
2. Programming
I have client and server connected.
client write and read from csock.
server write and read from ssock
suppose the server does :
....
close(ssock); //send FIN to client
othertask();
....
READ ERROR
if after the server close() the client does:
...
read(csock,...);
...... (2 Replies)
Discussion started by: gio
2 Replies
3. Solaris
Hi,
I've some background programs who crash with a SIGNINT receive from anywhere and on the same time I've got the message "Hard error on read, OS error = 32" on my terminal. I don't have any experience on the level for troubelshooting.
The problem can be come also from the version of oracle... (0 Replies)
Discussion started by: Franzlebord
0 Replies
4. UNIX for Dummies Questions & Answers
Hi guys,
i have a script called readnametest.i had written like this
# !/bin/ksh
echo "enter your name please"
read x;
echo " your name is $x"
i am getting an error like "readnametest.ksh: ^M: not found." while executing this one.Could any one please explain me on why this... (4 Replies)
Discussion started by: raoscb
4 Replies
5. Shell Programming and Scripting
Hi All,
there is a script that reads multiple files in a directory starting with CTG_TMPxx where xx is an integer number.
i have a problem in readin the last file. For example, if there are 10 files in that directory, 9 files are read and processed. but the 10th file, its saying as cannot read... (1 Reply)
Discussion started by: vkca
1 Replies
6. OS X (Apple)
My first post :)
I deleted all the files within /system/library/startupitems to the trash bin. Now my mac snow leopard won't boot at all. All I got is the gray screen, apple logo and the spinning wheel...just spinning forever. I was able to boot in single-user mode. I'm trying to copy cp command... (14 Replies)
Discussion started by: haxum
14 Replies
7. Solaris
Hi Guys,
Wondering if anyone has seen/has a fix for this, when i try boot my system from CDROM at the solaris/ttya/ttyb selection menu i get stuck in a loop:
kernel$ /boot/multiboot kernel/$isadir/unix -B install_media=cdrom,console=ttya
loading "/boot/multiboot kernel/$isadir/unix -B... (0 Replies)
Discussion started by: A-Train
0 Replies
8. Solaris
Hi Experts,
I have an error on my solaris 10. I would like to know how to find the root cause of error because the error like encrypted.
Here is the error:
Sep 28 21:02:49 eccprod SC:ci-rg:db-srv-rs: Fault monitor detected error INTERNAL_ERROR: 102 DEFAULT Action=NONE : Error in... (2 Replies)
Discussion started by: edydsuranta
2 Replies
9. Solaris
We encountered these error 2 times(e.g. Solaris 10 with NetWorker installed) with in the month of August, but we couldn't pin point the root cause, it might be bad sector, bad cable or software incompatibility?
Do you experience these issue or please share your understanding about this? Thanks... (0 Replies)
Discussion started by: B@S
0 Replies
10. Shell Programming and Scripting
Hi,
With root user i set this in the .bashrc of user1 on machine 1
more .bashrc
./track.sh
# .bashrc
# Source global definitions
if ; then
. /etc/bashrc
fi
Content of track.sh are
more track.sh
read -p "Enter ID:" reason
while ] # While string is different or empty...... (4 Replies)
Discussion started by: mohtashims
4 Replies
LEARN ABOUT XFREE86
xfs_freeze
xfs_freeze(8) System Manager's Manual xfs_freeze(8)
NAME
xfs_freeze - suspend access to an XFS filesystem
SYNOPSIS
xfs_freeze -f | -u mount-point
DESCRIPTION
xfs_freeze suspends and resumes access to an XFS filesystem (see xfs(5)).
xfs_freeze halts new access to the filesystem and creates a stable image on disk. xfs_freeze is intended to be used with volume managers
and hardware RAID devices that support the creation of snapshots.
The mount-point argument is the pathname of the directory where the filesystem is mounted. The filesystem must be mounted to be frozen
(see mount(8)).
The -f flag requests the specified XFS filesystem to be frozen from new modifications. When this is selected, all ongoing transactions in
the filesystem are allowed to complete, new write system calls are halted, other calls which modify the filesystem are halted, and all
dirty data, metadata, and log information are written to disk. Any process attempting to write to the frozen filesystem will block waiting
for the filesystem to be unfrozen.
Note that even after freezing, the on-disk filesystem can contain information on files that are still in the process of unlinking. These
files will not be unlinked until the filesystem is unfrozen or a clean mount of the snapshot is complete.
The -u flag is used to un-freeze the filesystem and allow operations to continue. Any filesystem modifications that were blocked by the
freeze are unblocked and allowed to complete.
One of -f or -u must be supplied to xfs_freeze.
NOTES
A copy of a frozen XFS filesystem will usually have the same universally unique identifier (UUID) as the original, and thus may be pre-
vented from being mounted. The XFS nouuid mount option can be used to circumvent this issue.
In Linux kernel version 2.6.29, the interface which XFS uses to freeze and unfreeze was elevated to the VFS, so that this tool can now be
used on many other Linux filesystems.
SEE ALSO
xfs(5), lvm(8), mount(8).
xfs_freeze(8)