03-05-2019
Has this box been abruptly powered off (power failure or kernel panic ?)
That would be the reason for error regarding journal recovery.
Course of action would be to boot rescue / live, active the root volume group and run a fsck on root logical volume.
Or do a clean reboot, and it should run fsck automatically during boot.
As for the error in the first post, well, looks like data and catalog directories of <insert application> exist, so you need to delete those before rerun.
Hope that helps
Regards
Peasant.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i am a newbie to unix admin stuff so bare with me. -- i get this message when executing mysql_install_db during the installation of mysql. what is the cause of this and how can it be fixed. btw - i have tried installing as root and other accounts also.
scripts/mysql_install_db:... (6 Replies)
Discussion started by: theDirtiest
6 Replies
2. UNIX for Dummies Questions & Answers
Hi There,
I'm trying to install LyX 1.4.3 on a machine running Redhat 7.3. I can't upgrade the OS since I don't have root, but I've been given permission to install sw into pkgs by the Sys Admins.
./configure using the Qt frontend worked, but when I then enter make I get:
make: Entering... (3 Replies)
Discussion started by: dirgni
3 Replies
3. Red Hat
Dear All I want to configure DNS in redhat linux. i am following these steps but when i restart the services it is showing status failed. Please any body can help me on urgent basis.
#service named restart
Stopping named:
Starting named:
---------Edited in named.conf... (2 Replies)
Discussion started by: sahu.tapan
2 Replies
4. HP-UX
Hi,
I'm new to HP-UX.
I have LVM on /var with 92Gig. I would like to reduce it to create another LVM for Oracle client with 800 meg or so. How to do it. I'm running 11.iv3
Thanks (4 Replies)
Discussion started by: lamoul
4 Replies
5. Red Hat
Hi Expert,
I am trying to restart automount as it's consume much CPU.
Tasks: 2392 total, 7 running, 2352 sleeping, 25 stopped, 8 zombie Cpu(s): 9.3% us, 28.5% sy, 0.0% ni, 61.5% id, 0.2% wa, 0.2% hi, 0.2% si Mem: 15799928k total, 11029764k used, 4770164k free, 162424k buffers Swap: 22773752k... (2 Replies)
Discussion started by: regmaster
2 Replies
6. Red Hat
hi all ,
I'm trying for the Red-hat cluster setup with the ' Enable shared storage support'. But hang up with a error that
"Packages of set "Clustered Storage" are not present in any available repository". I made this setup by installing the rpm manually..I ve attached the rpm list and error... (0 Replies)
Discussion started by: sriniv666
0 Replies
7. UNIX for Dummies Questions & Answers
Hi Guys,
I m using redhat 6, I have installed root partition as non-LVM .
Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies
8. UNIX for Dummies Questions & Answers
i have several lv (data , data1 , data2) under same volume group,
i just want to test 1 lv for data errors is that possible?
this test all sdc disk , but i just want to test lv_data
smartctl -a /dev/sdc
because lv_data2 is corrupt , but i don't know if this lv uses sdc disk (1 Reply)
Discussion started by: prpkrk
1 Replies
9. UNIX for Advanced & Expert Users
Hi,
I am having a text file with the following contents
###########
File1
###########
some
page1.txt
text
page.txt
When I sort this file on Red Hat 5, then I get the following output
###########
File1
###########
page1.txt
page.txt
some (3 Replies)
Discussion started by: sarbjit
3 Replies
10. Red Hat
Dear all,
I am reciving the following error in the /var/log/messages of my system
Jul 18 11:14:27 airtest xinetd: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:14:27 airtest xinetd: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:19:17 airtest xinetd: START: echo-dgram... (1 Reply)
Discussion started by: pistachio
1 Replies
LEARN ABOUT HPUX
fsck.hfsplus
FSCK_HFS(8) BSD System Manager's Manual FSCK_HFS(8)
NAME
fsck.hfs -- HFS file system consistency check
SYNOPSIS
fsck.hfs -q [-df] special ...
fsck.hfs -p [-df] special ...
fsck.hfs [-n | -y | -r] [-dfgl] [-m mode] [-c size] special ...
DESCRIPTION
The fsck.hfs utility verifies and repairs standard HFS and HFS+ file systems.
The first form of fsck.hfs quickly checks the specified file systems to determine whether they were cleanly unmounted.
The second form of fsck.hfs preens the specified file systems. It is normally started by fsck(8) during systen boot, when a HFS file system
is detected. When preening file systems, fsck.hfs will fix common inconsistencies for file systems that were not unmounted cleanly. If more
serious problems are found, fsck.hfs does not try to fix them, indicates that it was not successful, and exits.
The third form of fsck.hfs checks the specified file systems and tries to repair all detected inconsistencies.
If no options are specified fsck.hfs will always check and attempt to fix the specified file systems.
The options are as follows:
-c size Specify the size of the cache used by fsck.hfs internally. Bigger size can result in better performance but can result in
deadlock when used with -l option. Size can be specified as a decimal, octal, or hexadecimal number. If the number ends with
a ``k'', ``m'', or ``g'', the number is multiplied by 1024 (1K), 1048576 (1M), or 1073741824 (1G), respectively.
-d Display debugging information. This option may provide useful information when fsck.hfs cannot repair a damaged file system.
-f When used with the -p option, force fsck.hfs to check `clean' file systems, otherwise it means force fsck.hfs to check and
repair journaled HFS+ file systems.
-g Causes fsck.hfs to generate its output strings in GUI format. This option is used when another application with a graphical
user interface (like Mac OS X Disk Utility) is invoking the fsck.hfs tool.
-l Lock down the file system and perform a test-only check. This makes it possible to check a file system that is currently
mounted, although no repairs can be made.
-m mode Mode is an octal number that will be used to set the permissions for the lost+found directory when it is created. The
lost+found directory is only created when a volume is repaired and orphaned files or directories are detected. fsck.hfs places
orphaned files and directories into the lost+found directory (located at the root of the volume). The default mode is 01777.
-p Preen the specified file systems.
-q Causes fsck.hfs to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the exit
status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message is
printed to standard output describing whether the volume was clean or dirty.
-y Always attempt to repair any damage that is found.
-n Never attempt to repair any damage that is found.
-r Rebuild the catalog file on the specified file system. This option currently will only work if there is enough contiguous
space on the specified file system for a new catalog file and if there is no damage to the leaf nodes in the existing catalog
file.
SEE ALSO
fsck(8)
BUGS
fsck.hfs is not able to fix some inconsistencies that it detects.
HISTORY
The fsck.hfs command appeared in Mac OS X Server 1.0 .
Mac OS X November 21, 2002 Mac OS X