06-30-2009
device size mismatch after mounting
Hi,
I have a created a logical partition sda5 in ubuntu server 9.0.4.
which is
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00053d78
Device Boot Start End Blocks Id System
/dev/sda1 * 1 1216 9767488+ 83 Linux
/dev/sda2 1217 1702 3903795 82 Linux swap / Solaris
/dev/sda3 1703 30401 230524717+ 5 Extended
/dev/sda5 1703 30401 230524686 83 Linux
formatted the device as mkfs -t ext3 /dev/sda5
then i mounted it on to a directory which belongs to root user.
once I mounted the /dev/sda5 device on to a local directory.
I am seeing that the filesystem size is way too difference than what i have created.
/dev/sda5 10325748 1098212 8703016 12% /var/lib/vmware/vmwarehosts
Can somebody please let me know where i am going wrong here. why am i not seeing the full 230 gigs which shows in fdisk.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a small scsi memory disk device that my computer claims is a /dev/sda mount type.. and I have mounted it in the past.. but I just recently reinstalled my whole system to check out a couple of things on my database. including the scsi device and now I can't get it to mount.. i tried to mount... (20 Replies)
Discussion started by: moxxx68
20 Replies
2. UNIX for Dummies Questions & Answers
How do you mount a USB flash drive on Sun Blade 2000 or 2500 with solaris 8?
Thanks in advance ;) (1 Reply)
Discussion started by: xeroxtechnician
1 Replies
3. Linux
Hi Folks,
I want to know how to mount usb device (cd,dvd etc) in linux,
Regards,
Manoj (4 Replies)
Discussion started by: manoj.solaris
4 Replies
4. UNIX and Linux Applications
When I attach a USB storage device to my Solaris server, the mount point is coming up as /rmdisk/unnamed_rmdisk
Is there anyway I can have this device come up as a mounted device with a predetermined mount name eg /morespace rather than unnamed_rmdisk ? (0 Replies)
Discussion started by: jimthompson
0 Replies
5. UNIX for Advanced & Expert Users
When I attach a USB storage device to my Solaris server, the mount point is coming up as /rmdisk/unnamed_rmdisk
Is there anyway I can have this device come up as a mounted device with a predetermined mount name eg /morespace rather than unnamed_rmdisk ? (2 Replies)
Discussion started by: jimthompson
2 Replies
6. Shell Programming and Scripting
Hello,
I've written a Perl script that copies a set of files from one server to another.
Prior to transferring a file the script gets the file size from the source system and compares this to the file size received in the target system.
Except that the file sizes are slightly different.
... (1 Reply)
Discussion started by: mbb
1 Replies
7. Red Hat
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Discussion started by: Tanmoy
0 Replies
8. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
9. AIX
I am trying to configure dump devices on my AIX server. Running 7100-03-04-1441. My dump device needs to be about 2GB in size. My PP Size is 1024MB, so I create the device with 2 PPs. When I run lslv on the dump device, it shows the 2 PPs, and a PP Size of 1024 megabytes. However, a dumpcheck... (4 Replies)
Discussion started by: paqman
4 Replies
SD(4) Linux Programmer's Manual SD(4)
NAME
sd - Driver for SCSI Disk Drives
SYNOPSIS
#include <linux/hdreg.h> /* for HDIO_GETGEO */
#include <linux/fs.h> /* for BLKGETSIZE and BLKRRPART */
CONFIGURATION
The block device name has the following form: sdlp, where l is a letter denoting the physical drive, and p is a number denoting the parti-
tion on that physical drive. Often, the partition number, p, will be left off when the device corresponds to the whole drive.
SCSI disks have a major device number of 8, and a minor device number of the form (16 * drive_number) + partition_number, where drive_num-
ber is the number of the physical drive in order of detection, and partition_number is as follows:
partition 0 is the whole drive
partitions 1-4 are the DOS "primary" partitions
partitions 5-8 are the DOS "extended" (or "logical") partitions
For example, /dev/sda will have major 8, minor 0, and will refer to all of the first SCSI drive in the system; and /dev/sdb3 will have
major 8, minor 19, and will refer to the third DOS "primary" partition on the second SCSI drive in the system.
At this time, only block devices are provided. Raw devices have not yet been implemented.
DESCRIPTION
The following ioctls are provided:
HDIO_GETGEO
Returns the BIOS disk parameters in the following structure:
struct hd_geometry {
unsigned char heads;
unsigned char sectors;
unsigned short cylinders;
unsigned long start;
};
A pointer to this structure is passed as the ioctl(2) parameter.
The information returned in the parameter is the disk geometry of the drive as understood by DOS! This geometry is not the physical
geometry of the drive. It is used when constructing the drive's partition table, however, and is needed for convenient operation of
fdisk(1), efdisk(1), and lilo(1). If the geometry information is not available, zero will be returned for all of the parameters.
BLKGETSIZE
Returns the device size in sectors. The ioctl(2) parameter should be a pointer to a long.
BLKRRPART
Forces a reread of the SCSI disk partition tables. No parameter is needed.
The scsi(4) ioctl(2) operations are also supported. If the ioctl(2) parameter is required, and it is NULL, then ioctl(2) will fail
with the error EINVAL.
FILES
/dev/sd[a-h]: the whole device
/dev/sd[a-h][0-8]: individual block partitions
COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 1992-12-17 SD(4)