We use unixware 7.1.4 OS. We have the following problem:
* we have a corrupted filesystem (filesystem type is vxfs)
* we tried to clean it with this command:
* after this command the system display the following message:
"UX:fsck:WARNING: the following command (process 'PID') was terminated by signal 11 and dumped core".
Thanks.
Last edited by Yogesh Sawant; 04-10-2011 at 10:53 AM..
Reason: added code tags
how can i modify the filesystem in the sco unixware?
i only know use divvy command to moify the sco unix open server 5.05,but what is the corresponding command in the sco unixware?
i want to modify a filesystem to a raw device using the command (2 Replies)
Has anyone had any experience with VXFS and ACL's? For some reason when these two are used together ACL's don't seem to work properly (i.e. sometimes ACL's won't be applied to files in a directory so that when trying to move the directory, the new directory is created but the old directory still... (3 Replies)
hi guys,
I am studying for the solaris scsa and i want to practice with ufsdump and restores, fssnaps etc...
my question is, i finally found a server with a tape drive attached that i can mess arouund with because its not a critical box.
its running solaris 8, and i want to do a ufsdump, but... (2 Replies)
Hello,
I am having performance problem when , i ported a c code from Unixware 2.1 to Unixware 7.0.0.
My program establishes a synchornous connection with the client in a windows OS and then sends and receives messsages using the recv and send calls.
What i hyave noticed is that after a... (0 Replies)
Dear all,
What should I do with the following error message:
vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
Thanks for your advises, (1 Reply)
Hello,
Am basically working on VxFS filesystem and while tracking the file, I got stuck at one point.
As I am able to locate the superblock(it is at offset 1024 from the start of partition). And from superblock I got the sector no. of "OLT extent".
By jumping to the sector no where OLT... (1 Reply)
Hi,
How do I determine the free space below?
# vxdg -g msb_db_dg free
DISK DEVICE TAG OFFSET LENGTH FLAGS
msb_db_dg01 sdb sdb 312475648 316571392 n
Thanks! (1 Reply)
Hi,
I have two filesystems called /u009 and /u008. I need to release 60gb from /u009 and add it to /u008 fs through fsadm command..
these are vxfs filesystem..its urgent..
thanx in advance (5 Replies)
Hi,
I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local.
Please tell me the commands which I can run... (2 Replies)
Hi Gurus,
Please Help me to resolve below issue.
OS Version : HP-UX B.11.00 U 9000/800 62830930
When ever i try to mount following logical volumes, it throws me error.
mount -a
vxfs mount: /dev/datavg1/lvusr40 is corrupted. needs checking
vxfs mount: /dev/datavg1/lvusr38 is... (2 Replies)
Discussion started by: Justin John
2 Replies
LEARN ABOUT LINUX
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)