08-10-2015
You might want to clean up the root filesystem.
Being on 100% on / will lead to these (and worst) kind of problems.
Also, if you are using slices, consider starting from sector 1 instead of 0.
Dunno if UFS will honor that, but if you overwrite the first sector you will be in trouble.
Regards.
Peasant.
10 More Discussions You Might Find Interesting
1. SCO
I have just installed 5.0.7 of openserver and forgot to create a /u filesystem.
I have a root filesystem that takes up most of the hard disc space and I want to reduce the size of that and create a /u.
I have tried divvy amd mkdev fs but to no avail.
Could somebody give me some idea as to how I... (2 Replies)
Discussion started by: rongrout
2 Replies
2. AIX
Hello, this is my first post.
I have a user who cannot create a file over 2 GB's in size eventhough the FS is large file enabled and I added a special stanza in /etc/security/limits to allow an unlimited file size for this particular user (user1 - see below).
ibm:/home/root (4062)#cat... (7 Replies)
Discussion started by: AIXtexas
7 Replies
3. UNIX for Dummies Questions & Answers
Is there any URL or procedure to create a new file system on solaris 8/9/10.. (3 Replies)
Discussion started by: tintedwindow
3 Replies
4. UNIX for Advanced & Expert Users
Hi All:
I am using an adaptor between a 1TB SATA hard drive and solaris 8 box with 68 pin scsi. I use the format utility to partition the HD which works fine but when I use newfs, I get some errors. I will place them below.
I have blocked and the error message is in red.
Anybody got any... (1 Reply)
Discussion started by: mndavies
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
Has anyone ever encountered the following scenario:
I am working on a SUN server with solaris 10 installed and veritas managing the filesystem. One of the file systems has become full:
df -kh /ossrc/dbdumps
Filesystem size used avail capacity Mounted on... (6 Replies)
Discussion started by: eeidel
6 Replies
6. Red Hat
Hi,
I am unable to create/open any file in vi editor for normal user, though using root I am able to create/open any file, using redhat 5.5,
example
vi test
it showing nothing after entering command (9 Replies)
Discussion started by: manoj.solaris
9 Replies
7. Solaris
Hi,
The solaris filesystem /u01 shows available space as 100GB, and used space as 6 GB.
The Problem is when iam trying to install some software or copy some files in this file system /u01 Iam unable to copy or install in this file system due to lack of space.
ofcourse the software... (31 Replies)
Discussion started by: iris1
31 Replies
8. HP-UX
Hi,
I am trying to tar a directory structure. but unable to do due to a symbolic link. Please help
indomt@behpux $ tar -cvf test.tar /home/indomt
a /home/indomt symbolic link to /dxdv/03/ap1dm1
Thanks (1 Reply)
Discussion started by: nag_sathi
1 Replies
9. Red Hat
Hi
I have the following difficulty:
the NetApp admin has clone one file system from one red hatserver and presented this cloned LUN into another redhat server.
I can see the LUN as:
fdisk -l
Disk /dev/sda: 64.4 GB, 64424509440 bytes
255 heads, 63 sectors/track, 7832 cylinders
Units =... (1 Reply)
Discussion started by: fretagi
1 Replies
10. AIX
Hi,
I have inherited this AIX 5.3 host. I'm unable to increase the /usr file system. It gives me this error.
What needs to be done to remove this error?
vios:/home/padmin$ chfs -a size=+128M /usr
0516-304 lquerypv: Unable to find device id 0002ef4df616f9690000000000000000 in the Device
... (14 Replies)
Discussion started by: dn888
14 Replies
PVCK(8) System Manager's Manual PVCK(8)
NAME
pvck - check physical volume metadata
SYNOPSIS
pvck [-d|--debug] [-h|--help] [-v|--verbose] [--labelsector] PhysicalVolume [PhysicalVolume...]
DESCRIPTION
pvck checks physical volume LVM metadata for consistency.
OPTIONS
See lvm for common options.
--labelsector sector
By default, 4 sectors of PhysicalVolume are scanned for an LVM label, starting at sector 0. This parameter allows you to specify a
different starting sector for the scan and is useful for recovery situations. For example, suppose the partition table is corrupted
or lost on /dev/sda, but you suspect there was an LVM partition at approximately 100 MB. This area of the disk may be scanned by
using the --labelsector parameter with a value of 204800 (100 * 1024 * 1024 / 512 = 204800):
pvck --labelsector 204800 /dev/sda
Note that a script can be used with --labelsector to automate the process of finding LVM labels.
SEE ALSO
lvm(8), pvcreate(8), pvscan(8) vgck(8)
Sistina Software UK LVM TOOLS 2.02.95(2) (2012-03-06) PVCK(8)