01-25-2011
Wait wait wait. The correct order is
- Create an image file
- Create a loopback device for the file
- Run pvcreate on the loopback device
- Run vgcreate on the "physical" volume
- Run lvcreate on the volume group
- Create a filesystem on the logical volume
- Mount the logical volume
Why did you create a filesystem on the image file? What were your exact steps and what does your system look like now?
10 More Discussions You Might Find Interesting
1. AIX
Hi everybody,
Is it possible to create a Shared Filesystem on Network to be accessed from 2 Systems?
Both systems are AIX but with different versions. One of these systems is AIX 4.3 & the other is AIX 5.2.
Thanks in advanced (8 Replies)
Discussion started by: aldowsary
8 Replies
2. Solaris
# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c1d0s0 4.5G 4.3G 129M 98% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K ... (4 Replies)
Discussion started by: seyiisq
4 Replies
3. Filesystems, Disks and Memory
Hi all,
I would like to ask on how to create 2MB partition on a Compact Flash card. It supposed to be of FAT12 type, and the CF capacity is 4GB. I try to do the partitioning and specify the size as 2MB but the partition editor automatically resize it to 8MB. I know that this is possible and the... (4 Replies)
Discussion started by: archayl
4 Replies
4. Red Hat
I'm new to linux and need information on how do I create a filesytem on a dedicated on LUN for RHEL 4 and 5? I want the filesystem to be a ext3
---------- Post updated at 10:00 AM ---------- Previous update was at 08:56 AM ----------
Found the answer. This thread can be closed. (1 Reply)
Discussion started by: soupbone38
1 Replies
5. Red Hat
Hi,
I have a LUN presented to a Linux system and would like to ask if someone can advise if the logical volume /dev/mapper/VGOra-LVOra 12G 11G 659M 95% /usr/app/oracle can be extended. Is there any free space to allocate.... The LUN (25G) has been configured as follows:
LUN - ROOT...... (4 Replies)
Discussion started by: jamba1
4 Replies
6. Linux
Hi,
I have a server booted into sysresccd (mini-linux OS) with 1 40 GB disk attached
I am trying to create a volume group and restore another server into the new one
However, when I try to create a partition for /boot it seems that my VG in LVM is not recognized anymore
These are the... (2 Replies)
Discussion started by: galuzan
2 Replies
7. Red Hat
hi,
In my production server having
Enterprise Linux Enterprise Linux Server release 5.5 (Carthage)
Red Hat Enterprise Linux Server release 5.5 (Tikanga)
we have a filesystem of 197 gb (Type ext 3)
Hadisk in which this filesystem reside is sdb is of 217 gb. (NO LVM)
Now I want to... (6 Replies)
Discussion started by: salmanraza
6 Replies
8. AIX
Hello Team,
In a application filesystem, there is a process keep creating the log files. Due to that the filesystem keep getting full. Please let me know how to identify the process which is keep writing in the filesystem.
fuser -u <FS> will show only the user who using the filesystem.... (3 Replies)
Discussion started by: gowthamakanthan
3 Replies
9. Linux
Hi all
I have a system running:
uname -o
GNU/Linux
that has already some file systems created:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_outsystemdb-lv_root
50G 2.7G 45G 6% /
tmpfs 28G 72K 28G 1%... (5 Replies)
Discussion started by: fretagi
5 Replies
10. UNIX for Advanced & Expert Users
Hi,
I have a task of creating a UFS filesystem in an LDOM. It is located in a hypervisor (CDOM).
The storage has been provisioned to the CDOM. How do I make it reflect to the LDOM, and then from there configure/set up the filesystem in the LDOM?
Please help. (1 Reply)
Discussion started by: anaigini45
1 Replies
LEARN ABOUT OPENSOLARIS
fsck.minix
FSCK.MINIX(8) System Administration FSCK.MINIX(8)
NAME
fsck.minix - check consistency of Minix filesystem
SYNOPSIS
fsck.minix [options] device
DESCRIPTION
fsck.minix performs a consistency check for the Linux MINIX filesystem.
The program assumes the filesystem is quiescent. fsck.minix should not be used on a mounted device unless you can be sure nobody is writ-
ing to it. Remember that the kernel can write to device when it searches for files.
The device name will usually have the following form:
/dev/hda[1-63] IDE disk 1
/dev/hdb[1-63] IDE disk 2
/dev/sda[1-15] SCSI disk 1
/dev/sdb[1-15] SCSI disk 2
If the filesystem was changed, i.e., repaired, then fsck.minix will print "FILE SYSTEM HAS CHANGED" and will sync(2) three times before
exiting. There is no need to reboot after check.
WARNING
fsck.minix should not be used on a mounted filesystem. Using fsck.minix on a mounted filesystem is very dangerous, due to the possibility
that deleted files are still in use, and can seriously damage a perfectly good filesystem! If you absolutely have to run fsck.minix on a
mounted filesystem, such as the root filesystem, make sure nothing is writing to the disk, and that no files are "zombies" waiting for
deletion.
OPTIONS
-l, --list
List all filenames.
-r, --repair
Perform interactive repairs.
-a, --auto
Perform automatic repairs. This option implies --repair and serves to answer all of the questions asked with the default. Note
that this can be extremely dangerous in the case of extensive filesystem damage.
-v, --verbose
Be verbose.
-s, --super
Output super-block information.
-m, --uncleared
Activate MINIX-like "mode not cleared" warnings.
-f, --force
Force a filesystem check even if the filesystem was marked as valid. Marking is done by the kernel when the filesystem is
unmounted.
-V, --version
Display version information and exit.
-h, --help
Display help text and exit.
DIAGNOSTICS
There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.
If the device does not exist, fsck.minix will print "unable to read super block". If the device exists, but is not a MINIX filesystem,
fsck.minix will print "bad magic number in super-block".
EXIT CODES
The exit code returned by fsck.minix is the sum of the following:
0 No errors
3 Filesystem errors corrected, system should be rebooted if filesystem was mounted
4 Filesystem errors left uncorrected
7 Combination of exit codes 3 and 4
8 Operational error
16 Usage or syntax error
AUTHORS
Linus Torvalds <torvalds@cs.helsinki.fi>
Error code values by Rik Faith <faith@cs.unc.edu>
Added support for filesystem valid flag: Dr. Wettstein <greg%wind.uucp@plains.nodak.edu>.
Check to prevent fsck of mounted filesystem added by Daniel Quinlan <quinlan@yggdrasil.com>.
Minix v2 fs support by Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>, updated by Nicolai Langfeldt <janl@math.uio.no>.
Portability patch by Russell King <rmk@ecs.soton.ac.uk>.
SEE ALSO
fsck(8), fsck.ext2(8), mkfs(8), mkfs.ext2(8), mkfs.minix(8), reboot(8)
AVAILABILITY
The fsck.minix command is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils
/util-linux/>.
util-linux June 2015 FSCK.MINIX(8)