07-31-2010
Gather up 10 of the most interesting problems that have been solved here recently, especially those with novel solutions, and publish an article about them in a journal. Advocate this forum as the premier example of the UNIX/Linux community solving problems together.
9 More Discussions You Might Find Interesting
1. Programming
Hi!!,
could someone tell me how to increase the stack size in HP-UX?
Thanx (7 Replies)
Discussion started by: jyotipg
7 Replies
2. HP-UX
Hi All,
one of the mount point in Hp ux server has reached 95%
its a data base file and can not be deleted.
so i want to know how to increase the size of mount point
i am new to unix ,please help me (1 Reply)
Discussion started by: jyoti
1 Replies
3. Solaris
Hi all,
I have a 130gb HDD of which 95b is taken up by various partitions of windows xp...
I partitioned my HDD and gave solaris 10gb of space, but now owing to some development stuff i need to increase the space!!!
How do i do it!!
Please note that i do have ~20gb of space left still...... (2 Replies)
Discussion started by: wrapster
2 Replies
4. UNIX for Dummies Questions & Answers
Hi..
I want to increase the file system size of any filesystem online, without using the Volume manager like LVMs, is it possible? & if yes then how? (3 Replies)
Discussion started by: Amol21
3 Replies
5. Solaris
Dear all,
I am very new to solaris,
I have installed solaris 10,
i tried installing few softwares into file system, unfortunately system failed to install stating "No space left on device "
i searched few threads and it says, we have to increase root size. where my root size is... (2 Replies)
Discussion started by: radhnki
2 Replies
6. UNIX for Dummies Questions & Answers
Unix protect its password by using salt
It that mean larger the salt size the more secure?
if the salt size increase greatly, will the password still able to be cracked?
thank you for helping (1 Reply)
Discussion started by: cryogen
1 Replies
7. Solaris
Hi,
I am having two metadevices d50 and d100 which are used to created soft partitions as and when required.
d50 and d100 are metadevices formed on different disks.
d50 -- disks 0 & 1
d100 -- disks 2 & 3
I have a soft partition d70 os 50 GB on d50. Now there is no free space on d50.
... (1 Reply)
Discussion started by: sag71155
1 Replies
8. UNIX for Dummies Questions & Answers
hi guys
I am working on my vmware workstation.
I have a /dev/sdb which is 5GB. I am using LVM.
Now I increase /dev/sdb 2 more GB.
fdisk -l shows 7 GB but pvscan still shows 5GB.
how do I make my system recognize the new 7GB added and be able to add those to my physical volumen and... (1 Reply)
Discussion started by: kopper
1 Replies
9. Solaris
Dear All,
How to increase the swap size when physicall memory reaches 60 %. OR it can be only done after the physicall memory is full.
Rgds
Rj (8 Replies)
Discussion started by: jegaraman
8 Replies
LEARN ABOUT SUSE
journal_abort
JOURNAL_ABORT(9) The Linux Journalling API JOURNAL_ABORT(9)
NAME
journal_abort - Shutdown the journal immediately.
SYNOPSIS
void journal_abort(journal_t * journal, int errno);
ARGUMENTS
journal
the journal to shutdown.
errno
an error number to record in the journal indicating the reason for the shutdown.
DESCRIPTION
Perform a complete, immediate shutdown of the ENTIRE journal (not of a single transaction). This operation cannot be undone without closing
and reopening the journal.
The journal_abort function is intended to support higher level error recovery mechanisms such as the ext2/ext3 remount-readonly error mode.
Journal abort has very specific semantics. Any existing dirty, unjournaled buffers in the main filesystem will still be written to disk by
bdflush, but the journaling mechanism will be suspended immediately and no further transaction commits will be honoured.
Any dirty, journaled buffers will be written back to disk without hitting the journal. Atomicity cannot be guaranteed on an aborted
filesystem, but we _do_ attempt to leave as much data as possible behind for fsck to use for cleanup.
Any attempt to get a new transaction handle on a journal which is in ABORT state will just result in an -EROFS error return. A journal_stop
on an existing handle will return -EIO if we have entered abort state during the update.
Recursive transactions are not disturbed by journal abort until the final journal_stop, which will receive the -EIO error.
Finally, the journal_abort call allows the caller to supply an errno which will be recorded (if possible) in the journal superblock. This
allows a client to record failure conditions in the middle of a transaction without having to complete the transaction to record the
failure to disk. ext3_error, for example, now uses this functionality.
Errors which originate from within the journaling layer will NOT supply an errno; a null errno implies that absolutely no further writes
are done to the journal (unless there are any already in progress).
AUTHORS
Roger Gammans <rgammans@computer-surgery.co.uk>
Author.
Stephen Tweedie <sct@redhat.com>
Author.
COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 JOURNAL_ABORT(9)