01-23-2013
Not because of file system getting full but file system ro situation could occue becaused of high I\O rate, bad hardware, incorrectcly configured storage etc..
File sysetm is generally turns read-only to save it self from potential damages.
This User Gave Thanks to parth_buch For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
Could any one please help me in performing the following?
We have the following folder:
/home/test/proj1
/home/test/proj2
/home/test/proj3
Users from different country places files in this folder using FTP (These users uses different flavors of FTP tools).
Our... (1 Reply)
Discussion started by: vfrg
1 Replies
2. Shell Programming and Scripting
In my script, I am creating a file ----> then writting one line (i.e. Timestamp) ----> then FTP'ing. The same script can be executed by many other users.
While other users executing this script, they couldn't Over write this one line (i.e. Timestamp)
My expectation
So I wanted to create a... (2 Replies)
Discussion started by: sbmk_design
2 Replies
3. UNIX for Advanced & Expert Users
I was tryin to copy a large file under /tmp location.
I guess the disk space got full and i got fork error.
Then I tried removing some files but the shell did not let me do anything
bash> rm apache22.tar
bash: fork: Not enough space
bash> pwd
/tmp
bash> vmstat 1
bash: fork: Not... (3 Replies)
Discussion started by: mohtashims
3 Replies
4. Solaris
hi guys..
how to give root permission for particular user
tel me step by step (2 Replies)
Discussion started by: coolboys
2 Replies
5. Solaris
Hi,
I have enabled the Apache webserver on my machime.
Apache root directory is /etc/apache2 and the user in which the web server is configured is webservd,I guess.
I have another user called perf.
Under perf user there is /export/home/perf/v9 directory.
I want to give the OS user of... (3 Replies)
Discussion started by: bikas89
3 Replies
6. AIX
Paging space is 100% full? what step can i take (3 Replies)
Discussion started by: ramraj731
3 Replies
7. UNIX for Dummies Questions & Answers
ANy reasons?
FILESYSTEM not FULL, PERMISSION is 777, but cant write to the filesystem?
any steps to do? reasons for this? (9 Replies)
Discussion started by: kenshinhimura
9 Replies
8. HP-UX
Hi,
I am unable to get the full FS space, as /home is 100% utilized and after deleting unwanted files, its still 100%. After checking the du -sk * | sort -n output and converting it to MBs, the total sizes comes out to be 351 MBs only however the lvol is of 3GB. I don't know where is all the space... (2 Replies)
Discussion started by: Kits
2 Replies
9. Emergency UNIX and Linux Support
Hello,
This is RHEL 5.7. swap is almost full, but I am not sure, what to release and how to release space. This is production server so I would like to try all possible options before reboot.
# top
top - 00:18:26 up 327 days, 7:01, 3 users, load average: 0.16, 0.21, 0.18
Tasks: 782 total, ... (7 Replies)
Discussion started by: solaris_1977
7 Replies
10. UNIX for Beginners Questions & Answers
Hello Team,
Please help me to solve my Problem,
By mistake, I give full permission to /(root) directory. by using the following command "chmod -R 777 /"
after this, the client asks for the password to login via ssh. Before that, I an able to Login without a password.
Please help me to retrieve... (5 Replies)
Discussion started by: Shubham1182
5 Replies
LEARN ABOUT FREEBSD
dumpon
DUMPON(8) BSD System Manager's Manual DUMPON(8)
NAME
dumpon -- specify a device for crash dumps
SYNOPSIS
dumpon [-v] special_file
dumpon [-v] off
dumpon [-v] -l
DESCRIPTION
The dumpon utility is used to specify a device where the kernel can save a crash dump in the case of a panic.
Calls to dumpon normally occur from the system multi-user initialization file /etc/rc, controlled by the ``dumpdev'' variable in the boot
time configuration file /etc/rc.conf.
The default type of kernel crash dump is the mini crash dump. Mini crash dumps hold only memory pages in use by the kernel. Alternatively,
full memory dumps can be enabled by setting the debug.minidump sysctl(8) variable to 0.
For systems using full memory dumps, the size of the specified dump device must be at least the size of physical memory. Even though an
additional 64 kB header is added to the dump, the BIOS for a platform typically holds back some memory, so it is not usually necessary to
size the dump device larger than the actual amount of RAM available in the machine. Also, when using full memory dumps, the dumpon utility
will refuse to enable a dump device which is smaller than the total amount of physical memory as reported by the hw.physmem sysctl(8) vari-
able.
The -l flag causes dumpon to print the current dump device or _PATH_DEVNULL ("/dev/null") if no device is configured.
The -v flag causes dumpon to be verbose about its activity.
IMPLEMENTATION NOTES
Since a panic(9) condition may occur in a situation where the kernel cannot trust its internal representation of the state of any given file
system, one of the system swap devices, and not a device containing a file system, should be used as the dump device.
The dumpon utility operates by opening special_file and making a DIOCSKERNELDUMP ioctl(2) request on it to save kernel crash dumps. If
special_file is the text string: ``off'', dumpon performs a DIOCSKERNELDUMP ioctl(2) on /dev/null and thus instructs the kernel not to save
crash dumps.
Since dumpon cannot be used during kernel initialization, the dumpdev variable of loader(8) must be used to enable dumps for system panics
which occur during kernel initialization.
FILES
/dev/{ada,da}?s?b standard swap areas
/etc/rc.conf boot-time system configuration
SEE ALSO
fstab(5), rc.conf(5), config(8), init(8), loader(8), rc(8), savecore(8), swapon(8), panic(9)
HISTORY
The dumpon utility appeared in FreeBSD 2.1.
BUGS
Because the file system layer is already dead by the time a crash dump is taken, it is not possible to send crash dumps directly to a file.
BSD
October 8, 2014 BSD