01-18-2012
journal errors are SPOF. in the linux filesystem. The surest way to clear them is to drop the journal and then add it again. In yiur case, you would use a recovery (virtual) CD and then use tune2fs to drop and then re add the journal. Check the man page for the options on doing this. (sorry, on my iphone)
10 More Discussions You Might Find Interesting
1. Virtualization and Cloud Computing
Hi
I would like to know how to do virtualization in Rhel 5.3 and Cent os 5.3, As i am new this Virtualization need guidence how to install and configure guest os in Rhel and Cent Os
can some one guide me step by step
Regards
Solaris8in (1 Reply)
Discussion started by: solaris8in
1 Replies
2. Red Hat
Hi, I have some questions about RHEL and CentOS download and installation.
(1) Is RHEL6.0 x86_64 beta downloaded from Red Hat site working fine?
(2) Where to download CentOS 5.5 DVD iso without using BitTorrent?
(3) What are the differences between these two images - CentOS 5.5 i386 and... (6 Replies)
Discussion started by: aixlover
6 Replies
3. Red Hat
Hi all, i have 3 nodes cluster (Centos 5 cluster suit) with out quorum disk,
node vote = 1,
the value of a quorum = 2,
when 2 nodes going offline, cluster services are destoys.
How i can save the cluster and all services(move all services to one alive node)
with out quorum disk when other... (3 Replies)
Discussion started by: Flomaster
3 Replies
4. Red Hat
Hello,
I was wondering if it would be possible to run two VMs one with services for IPv4 and the other one with services for IPv6. The main physical system would be connected to a IPv6 switch.
I think it should be fine but I would like to hear out your comments. (1 Reply)
Discussion started by: svalenciatech
1 Replies
5. Red Hat
Hi guys
I have CentOS installed on my server. I have also installed TFTP server, DHCP server. I am able to install CentOS on remote machines using PXE boot and kickstart cfg file.
I would like to install OpenSUSE using CentOS kickstart file. How do I do it ? I am also fine with any other... (2 Replies)
Discussion started by: msohail
2 Replies
6. Red Hat
Hello,
Can someone suggest me what I missing, I re-sized a root virtual disk to 30GB on the CentOS VM. After re-sizing the disk, I booted the OS and ran fdisk -list command I was able view the size of the disk as 30GB.
Paritions in the vm before I resize are:
/boot - Primary parition
/... (1 Reply)
Discussion started by: bobby320
1 Replies
7. UNIX for Dummies Questions & Answers
Came home the other day to a Napp-it Gui that would not load.
Login would appear but when i attempted I would get the following
Set default permissions and reading disk and pool parameter, please wait..
in case of problems, try a reboot after Power-Off or check disk and pool status at CLI.... (1 Reply)
Discussion started by: fastedd27
1 Replies
8. Red Hat
I was testing Networking Teaming (activebackup) with a VM hosted on VmWare Workstation and VirtualBox, and the result is, if the active interface is down, the system is not using the backup interface.
Tested on both CentOS / RHEL 7
Please find below the command I have used to configure teaming.... (0 Replies)
Discussion started by: atanubanerji
0 Replies
9. Red Hat
Hi All,
I have one logical volume with size as 900G and it is mounted as xfs file system.
Now I want to reduce this partition to 500G.
So I followed the below steps.
unmount the mount point /home
Reduced the volume using the command
Now I remounted the partition.
But the problem... (3 Replies)
Discussion started by: kalpeer
3 Replies
10. Red Hat
Hi!
One of our clients need RHEL 7 on PPC hardware for their R&D setup and they are particular about this being 'Little Endian'.
The problem is that Redhat doesn't have LE RHEL7 images below 7.1 while the latest toolkit (which is needed while reimaging an IBM LPAR) that IBM provides only... (0 Replies)
Discussion started by: satish51392111
0 Replies
LEARN ABOUT DEBIAN
gfs_jadd
gfs_jadd(8) System Manager's Manual gfs_jadd(8)
NAME
gfs_jadd - Add journals to a GFS filesystem
SYNOPSIS
gfs_jadd [OPTION]... <DEVICE|MOINTPOINT>...
DESCRIPTION
gfs_jadd is used to add journals to a GFS filesystem after the device upon which the filesystem resides has been grown. By running
gfs_jadd on a GFS filesystem, you are filling in space between the current end of the filesystem and the end of the device upon which the
filesystem resides. When this operation is complete, the journal index is updated so that machines mounting the filesystem at a later date
will see the newly created journals in addition to the journals already there. Machines which are already running in the cluster are unaf-
fected.
gfs_jadd will not use space that has been formatted for filesystem data even if that space has never been populated with files.
You may only run gfs_jadd on a mounted filesystem, addition of journals to unmounted filesystems is not supported. You only need to run
gfs_jadd on one node in the cluster. All the other nodes will see the expansion has occurred when required.
You must be superuser to execute gfs_jadd. The gfs_jadd tool tries to prevent you from corrupting your filesystem by checking as many of
the likely problems as it can. When growing a filesystem, only the last step of updating the journal index affects the currently mounted
filesystem and so failure part way through the expansion process should leave your filesystem in its original state.
You can run gfs_jadd with the -Tv flags to get a display of the current state of a mounted GFS filesystem. This can be useful to do after
the journal addition process to see if the changes have been successful.
OPTIONS
-j num The number of new journals to add. This defaults to 1.
-J size
The size of the new journals in megabytes. The defaults to 128MB (the minimum size allowed is 32MB). If you want to add journals of
different sizes to the filesystem, you'll need to run gfs_jadd once for each different size of journal. The size you specify here
will be rounded down so that it is a multiple of the journal segment size which was specified at filesystem creation time.
-h Help. Prints out a short usage message and exits.
-q Quiet. Turns down the verbosity level.
-T Test. Do all calculations, but do not write any data to the disk and do not add journals. This is used to discover what the tool
would have done were it run without this flag. You probably want to turn the verbosity level up in order to gain most information
from this option.
-V Version. Print version information, then exit.
-v Verbose. Turn up verbosity of messages.
SEE ALSO
mkfs.gfs(8) gfs_grow(8)
gfs_jadd(8)