Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Creating mountpoint in Linux from rawdevices without lv's Post 302928395 by rbatte1 on Thursday 11th of December 2014 10:41:39 AM
Old 12-11-2014
Can you share with us the output from fdisk -l so we can see what disks/slices you already have. If you could indicate which you think you want to use then we can talk about the process to format it to give you a filesystem.

It would be useful to know your OS version and level. The output from uname -a should be enough.



Thanks, in advance,
Robin
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

HPUX : identify NFS mountpoint

Is there a way to identify a directory as the start of an NFS mountpoint in HPUX 11.0? Using existing utilities & without root priv. If you stat the directory and use the S_ISNWK macro you can find network special files that way. The requirement will have to go through other channels if I need... (5 Replies)
Discussion started by: jim mcnamara
5 Replies

2. AIX

Do I need /etc/sysconfig/rawdevices on AIX

When install Oracle 10, for linux, I need input entries in /etc/sysconfig/rawdevices . However, for AIX, do I need input somthing in /etc/sysconfig/rawdevices ? (1 Reply)
Discussion started by: rainbow_bean
1 Replies

3. Solaris

problem in restoring mountpoint in Solaris

Hi, I am restoring the existing mount point on Solaris and getting below mentioned error mount: /dev/dsk/c0t2d0s6 is already mounted or /billing is busy I uses truss command to see the output and snapshot is below. Please help me to restore the mount point, # truss -fa mount -F... (3 Replies)
Discussion started by: helplineinc
3 Replies

4. Shell Programming and Scripting

Get mountpoint from filename

Dear Guru's Given a full filename /a/b/c/d/file.txt how do i determine what part is the mount point ( say /a/b). Cheers, Karel (6 Replies)
Discussion started by: karelb
6 Replies

5. UNIX for Dummies Questions & Answers

Testing NAS /mountpoint accessible

Hello. What's the best way to ensure that a NFS filesystem mounted from a disk-cabine (NAS) is accessible? My proposal: 1. ping to the ip of the cabine 2. verify filesystem is mounted 3. touch a file inside the /mountpoint Any other suggestions? Thank you! (2 Replies)
Discussion started by: asanchez
2 Replies

6. UNIX for Advanced & Expert Users

rawdevices help

why raw devices are used (6 Replies)
Discussion started by: robo
6 Replies

7. UNIX for Advanced & Expert Users

Filesystem and partition, mountpoint

Hello All, I am new to System/plat-form administration work. Right now I am facing some issues while creating the filesystem and mounpoint. I am using Linux 6.0 SuSE 11. Last time I was used one command to partition the given space along with filesystem in SuSE 9 and it was done in GUI mode but... (0 Replies)
Discussion started by: nvkuriseti
0 Replies

8. UNIX for Advanced & Expert Users

Unable to format new mountpoint

Can some one help me i try to mkfs new mountpoint from storageIBM but give some problem # mkfs -t ext3 /dev/sdd1 mke2fs 1.39 (29-May-2006) /dev/sdd1 is apparently in use by the system; will not make a filesystem here! my os is redhat 5.3 using fdisk # fdisk -l Disk /dev/sda: 298.9... (4 Replies)
Discussion started by: vickyid04
4 Replies

9. AIX

Space not getting released on the mountpoint

root@atldc-oragrid-ux01:/oragrid_01> du -sg * 0.58 11gR2gridBase 47.31 Grid_11203 4.17 app 0.00 lost+found 0.01 oraInventory root@atldc-oragrid-ux01:/oragrid_01> cd Grid_11203 root@atldc-oragrid-ux01:/oragrid_01/Grid_11203> du -sg *|sort 0.00 JRE 0.00 OPatch_old 0.00 ... (11 Replies)
Discussion started by: Vishal_dba
11 Replies

10. Shell Programming and Scripting

Mountpoint monitoring script

Hi, I am new to shell scripting. I prepared a very simple script to monitor mount points but not geting desired output. df -h|awk -F' ' '{ if ($5 >= 80) print "CRITICAL\n" $NF " mount point has reached " $5;}'|sed -n '3,$p' When I run above script in Sun solaris box it is executing... (8 Replies)
Discussion started by: sv0081493
8 Replies
fmthard(1M)															       fmthard(1M)

NAME
fmthard - populate label on hard disks SYNOPSIS
SPARC fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 The fmthard command updates the VTOC (Volume Table of Contents) on hard disks and, on systems, adds boot information to the Solaris fdisk partition. One or more of the options -s datafile, -d data, or -n volume_name must be used to request modifications to the disk label. To print disk label contents, see prtvtoc(1M). The /dev/rdsk/c?[t?]d?s2 file must be the character special file of the device where the new label is to be installed. On systems, fdisk(1M) must be run on the drive before fmthard. If you are using an system, note that the term ``partition'' in this page refers to slices within the fdisk partition on machines. Do not confuse the partitions created by fmthard with the partitions created by fdisk. The following options are supported: -d data The data argument of this option is a string representing the information for a particular partition in the current VTOC. The string must be of the format part:tag:flag:start:size where part is the partition number, tag is the ID TAG of the partition, flag is the set of permission flags, start is the starting sector number of the partition, and size is the number of sectors in the partition. See the description of the datafile below for more information on these fields. -i This option allows the command to create the desired VTOC table, but prints the information to standard output instead of modifying the VTOC on the disk. -n volume_name This option is used to give the disk a volume_name up to 8 characters long. -s datafile This option is used to populate the VTOC according to a datafile created by the user. If the datafile is "-", fmthard reads from standard input. The datafile format is described below. This option causes all of the disk par- tition timestamp fields to be set to zero. Every VTOC generated by fmthard will also have partition 2, by convention, that corresponds to the whole disk. If the input in datafile does not specify an entry for partition 2, a default partition 2 entry will be created auto- matically in VTOC with the tag V_BACKUP and size equal to the full size of the disk. The datafile contains one specification line for each partition, starting with partition 0. Each line is delimited by a new-line character ( ). If the first character of a line is an asterisk (*), the line is treated as a com- ment. Each line is composed of entries that are position-dependent, separated by "white space" and having the fol- lowing format: partition tag flag starting_sector size_in_sectors where the entries have the following values: partition The partition number. Currently, for Solaris SPARC, a disk can have up to 8 partitions, 0-7. Even though the partition field has 4 bits, only 3 bits are currently used. For , all 4 bits are used to allow slices 0-15. Each Solaris fdisk partition can have up to 16 slices. tag The partition tag: a decimal number. The following are reserved codes: 0 (V_UNASSIGNED), 1 (V_BOOT), 2 (V_ROOT), 3 (V_SWAP), 4 (V_USR), 5 (V_BACKUP), 6 (V_STAND), 7 (V_VAR), and 8 (V_HOME). flag The flag allows a partition to be flagged as unmountable or read only, the masks being: V_UNMNT 0x01, and V_RONLY 0x10. For mountable partitions use 0x00. starting_sector The sector number (decimal) on which the partition starts. size_in_sectors The number (decimal) of sectors occupied by the partition. You can save the output of a prtvtoc command to a file, edit the file, and use it as the datafile argument to the -s option. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ uname(1), format(1M), prtvtoc(1M), attributes(5) Only fdisk(1M), installgrub(1M) Special care should be exercised when overwriting an existing VTOC, as incorrect entries could result in current data being inaccessible. As a precaution, save the old VTOC. For disks under one terabyte, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose. 11 Apr 2005 fmthard(1M)
All times are GMT -4. The time now is 05:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy