07-23-2009
If that would be the case then I would not be able to write to any file or create new files on the fs, but I can easily do that.
But still fsck in single user mode returns same result (fsck version) as mentioned in my previous msg.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Anyone would know how to get rid off a message that comes up during a boot-up on Solaris? It says that the clusters for this software are not installed. I deleted the software because it was crashing some other stuff but it did not get rid off all the stuff.
Yes, I am coming from windows and... (2 Replies)
Discussion started by: softarch
2 Replies
2. Solaris
(Solaris 8, 4 cpu's)
When I look at my boot messages (/var/adm/messages or dmesg) I noticed the following:
Sep 23 08:53:00 server1 unix: cpu0: SUNW,UltraSPARC-II (upaid 0 impl 0x11 ver 0xa0 clock 450 MHz)
Sep 23 08:53:00 server1 unix: cpu1: SUNW,UltraSPARC-II (upaid 1 impl 0x11 ver... (1 Reply)
Discussion started by: finster
1 Replies
3. Linux
Where do all those messages at boot time get stored / logged?
like:
starting eth0 : OK
starting mysql : OK
etc... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
4. AIX
hi all
i just found one of my p650 server showing a warning message when i
tried to run bosboot command after upgrading TL to AIX 530803.
i also tried to run chpv -c hdisk0 and chpv -c hdisk1 to clear out the
old boot info in hdisk0 and hdisk1 and rerun bosboot -a. it still
showed... (0 Replies)
Discussion started by: rs6000er
0 Replies
5. Red Hat
Hi Guys :)
I am finding out the way to use mondorestore via command line only, no GUI.
I am able to use mondoarchive in the same way but not mondorestore.
can anybody help me out.... Thanks in advance!
halides:b: (0 Replies)
Discussion started by: halides
0 Replies
6. Filesystems, Disks and Memory
Hello All,
I backed up my RHEL 4 as an image.
Then I restored the image on my machine. Everything went fine but I dont get the normal boot sequence as it used to come when I freshly installed RHEL4.
The messages that are shown when the system boots are something like-
" .....
EXT3-fs:... (2 Replies)
Discussion started by: shamik
2 Replies
7. Shell Programming and Scripting
Hi All,
I have to work in the late nights some times for server maintenance and in a hurry to complete I am accidentally changing ownership or permission of directories :(
which have similar names ( /var in root and var of some other directory ).:confused:
Can some one suggest me with the... (1 Reply)
Discussion started by: shiek.kaleem
1 Replies
8. Red Hat
I am trying to understand what are the differences of boot messages verbosity levels for the kernel field in grub.conf
From my research, there appear to be three levels:
quiet
verbose
debug
I have also found documents that specify removing quiet from the kernel field. If this is done, is... (1 Reply)
Discussion started by: thaebich
1 Replies
9. Red Hat
Heyas
So i have my custom Fedora with AwesomeWM spin with alots of customizations using the kickstart method for a liveimage.
A few weeks (2-3 months) ago, i've done some changes i cannot remember.
Those changes made the image from bootable to gui, to not booting to gui any more.
Just... (3 Replies)
Discussion started by: sea
3 Replies
10. Red Hat
Hi all
Many years ago, I found online this script that was incredibly funny and I had blogged it
Unfortunately because of my poor record-keeping, I seem to have lost the shell script
Would somebody be kind enough to tell me how to replicate this?
Thank you! (0 Replies)
Discussion started by: hedkandi
0 Replies
LEARN ABOUT MOJAVE
fsck.xfs
fsck.xfs(8) System Manager's Manual fsck.xfs(8)
NAME
fsck.xfs - do nothing, successfully
SYNOPSIS
fsck.xfs [ filesys ... ]
DESCRIPTION
fsck.xfs is called by the generic Linux fsck(8) program at startup to check and repair an XFS filesystem. XFS is a journaling filesystem
and performs recovery at mount(8) time if necessary, so fsck.xfs simply exits with a zero exit status.
If you wish to check the consistency of an XFS filesystem, or repair a damaged or corrupt XFS filesystem, see xfs_check(8) and
xfs_repair(8).
FILES
/etc/fstab.
SEE ALSO
fsck(8), fstab(5), xfs(5), xfs_check(8), xfs_repair(8).
fsck.xfs(8)