10-30-2008
From your initial post I was beginning to suspect some kind of filesystem corruption, but after seeing those df output figures that feeling is getting stronger.
I really think you'd be best booting from CD-ROM or network and doing a full fsck of the root filesystem.
Do you run regular backups? Do check that you have a successful one before you do the filesystem check.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, how to create account with the following
be cron enabled
only accessible via sudo (1 Reply)
Discussion started by: vilves
1 Replies
2. IP Networking
how we can find whether net is enabled or not
with out using ping
is there anyway please guide me
thanku ,in advance
sree (1 Reply)
Discussion started by: phani_sree
1 Replies
3. HP-UX
$ uname -a
HP-UX vfauh203 B.11.11 U 9000/800 486452371 unlimited-user license
SCSI TAPE: dev = 0xcd520000 Failed open - st_san_safe enabled ()
is there any tools i can run to further investigate this err0r i received from syslog.log ? im new to hp-ux thanks (1 Reply)
Discussion started by: libchk
1 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
i had 500 users how can i know whether user is disabled or enabled
Thanks,
kalyan (8 Replies)
Discussion started by: kalyan212
8 Replies
5. Solaris
Hi guys.
This may be a stupid question but I am trying to see if my Solaris 9 server has async i/o enabled...
Is there a quick way to determine this?
Thanks in advance. (1 Reply)
Discussion started by: jamie_collins
1 Replies
6. Linux
Hi
when I run the following GET commad:
./snmpget -m ALL -M /data/net/naamab/snmp/snmp_mib/ -v 3 -a MD5 -l authPriv -u test1 -A welcome1 -x DES -X privpass 127.0.0.1 NOVELSAT-MODULATOR-MIB::nsModLineCMMode.0 -d
I get the error:
Encryption support not enabled.
snmpget: USM encryption... (1 Reply)
Discussion started by: naamabm
1 Replies
7. Shell Programming and Scripting
:(
---------- Post updated at 01:51 AM ---------- Previous update was at 01:50 AM ----------
Not working
---------- Post updated at 02:04 AM ---------- Previous update was at 01:51 AM ----------
cp -p /home/* home/exp/*.`date`
i am using this (4 Replies)
Discussion started by: rishiraaz
4 Replies
8. AIX
AIX Version 6.1 and 7.1.
I understand that when the OS initially creates the FS and inodes, its pretty strict, but not always tuned to a 1:1 ratio. I see the same thing when adding a whole disk LV to a separate device.
It seems that when we expand a filesystem the inodes don't get tuned... (5 Replies)
Discussion started by: mrmurdock
5 Replies
9. What is on Your Mind?
Retro Games has announced that the C64 is back, this time full-sized with a working keyboard for the dedicated retro home-computer fan, available December 2019.
See also:
CNN:
Iconic 80s computer The Commodore 64 to return with fully-functional keyboard
YouTube:
The C64 | Trailer
... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT POSIX
systemd-fsck
SYSTEMD-FSCK@.SERVICE(8) systemd-fsck@.service SYSTEMD-FSCK@.SERVICE(8)
NAME
systemd-fsck@.service, systemd-fsck-root.service, systemd-fsck - File system checker logic
SYNOPSIS
systemd-fsck@.service
systemd-fsck-root.service
/lib/systemd/systemd-fsck
DESCRIPTION
systemd-fsck@.service and systemd-fsck-root.service are services responsible for file system checks. They are instantiated for each device
that is configured for file system checking. systemd-fsck-root.service is responsible for file system checks on the root file system, but
only if the root filesystem was not checked in the initramfs. systemd-fsck@.service is used for all other file systems and for the root
file system in the initramfs.
These services are started at boot if passno in /etc/fstab for the file system is set to a value greater than zero. The file system check
for root is performed before the other file systems. Other file systems may be checked in parallel, except when they are on the same
rotating disk.
systemd-fsck does not know any details about specific filesystems, and simply executes file system checkers specific to each filesystem
type (/sbin/fsck.*). This helper will decide if the filesystem should actually be checked based on the time since last check, number of
mounts, unclean unmount, etc.
If a file system check fails for a service without nofail, emergency mode is activated, by isolating to emergency.target.
KERNEL COMMAND LINE
systemd-fsck understands these kernel command line parameters:
fsck.mode=
One of "auto", "force", "skip". Controls the mode of operation. The default is "auto", and ensures that file system checks are done
when the file system checker deems them necessary. "force" unconditionally results in full file system checks. "skip" skips any file
system checks.
fsck.repair=
One of "preen", "yes", "no". Controls the mode of operation. The default is "preen", and will automatically repair problems that can be
safely fixed. "yes" will answer yes to all questions by fsck and "no" will answer no to all questions.
SEE ALSO
systemd(1), fsck(8), systemd-quotacheck.service(8), fsck.btrfs(8), fsck.cramfs(8), fsck.ext4(8), fsck.fat(8), fsck.hfsplus(8),
fsck.minix(8), fsck.ntfs(8), fsck.xfs(8)
systemd 237 SYSTEMD-FSCK@.SERVICE(8)