Hi,
Here is output pf fdisk -l. aslo I am not using any RAID.
With Best Regards
sunil
fdisk -l
Disk /dev/cciss/c0d0: 146.7 GB, 146778685440 bytes
255 heads, 63 sectors/track, 17844 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 14001 15000 8032500 83 Linux
/dev/cciss/c0d0p2 1 4000 32129968+ 82 Linux swap /
Solaris
/dev/cciss/c0d0p3 4001 10000 48195000 83 Linux
/dev/cciss/c0d0p4 10001 14000 32130000 5 Extended
/dev/cciss/c0d0p5 10001 14000 32129968+ 83 Linux
Partition table entries are not in disk order
Disk /dev/cciss/c0d1: 10001.7 GB, 10001711325184 bytes
255 heads, 63 sectors/track, 1215972 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d1p1 1 267350 2147483647+ ee EFI GPT
On Mon, Jun 6, 2011 at 11:38 AM, jdow <[email protected]> wrote:
> Can you cut and paste the fdisk -l output into an email? It can tell
> you a lot about what the drives really amount to.
>
> Are you running it as a RAID with checksum or simply striping? Your
> numbers suggest something like RAID 6.
>
> This is the system I am currently prepping to use as a name server,
> firewall, and email tool for a two person multi-computer (and a lot
> of "gadgets") network here.
>
> Disk /dev/sda: 500.1 GB, 500107862016 bytes
> 255 heads, 63 sectors/track, 60801 cylinders
>
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00007e83
>
>
> Device Boot Start End Blocks Id System
> /dev/sda1 * 1 64 512000 83 Linux
> Partition 1 does not end on cylinder boundary.
> /dev/sda2 64 60802 487873536 8e Linux LVM
>
> The header portion is REALLY interesting. It's a 500 gigabyte
> drive. But, it's only 488386584 1k blocks, 476940 1 meg blocks, or
> 465 1 gigabyte blocks when speaking of 1024 byte entities rather
> than 1000 byte entities.
>
> Your 12 1 terabyte disks striped array is only 10.91 TeraBytes
> in computer speak - 1024 per K rather than 1000 per k. Could
> that explain your discrepancy?
>
> {^_^} Joanne (First explained this to others in 1986. IMAO
> disks should be advertised both ways for clarity.)
>
>
> On 2011/06/05 22:11, Sunil M. Dogra wrote:
>
>> Hi,
>>
>> Ans: / = ~45GB
>> /boot =~2GB
>> /swap =~16GB
>>
>>
>> I have another question
>>
>> why gparted, fdisk -l, system-config-lvm are giving different outputs for
>> 12TB but giving the same output for 500GB
>>
>> With Regards
>> sunil
>>
>>
>> On Mon, Jun 6, 2011 at 3:28 AM, jdow <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> On 2011/06/03 06:47, Alec T. Habig wrote:
>>
>> James Holland writes:
>>
>> Don't know why this is... But check how big your other
>> partitions
>> are using gparted.
>>
>>
>> Could it be that he's comparing the "1TB" drives he's bought (which
>> are
>> marketed as decimal 1x10^12 bytes) with the expected (binary) 2^40
>> bytes?
>>
>> That's a 10% reduction in perceived space. If the disk format has
>> also
>> reserved the traditional (and now obsolete) 10% for root use only,
>> then
>> suddenly we're 2.5 TB down from what one would naively expect after
>> clicking on "Newegg, please send me 12 terabyte drives".
>>
>> gparted will show the whole capacity (ignoring this root reserve),
>> but
>> "df" won't.
>>
>>
>> How big are /, /boot, and /swap?
>>
>>
>>
>>
>>
>>
>>
>> (I'm old fashioned and silly, I like "/dev/fdisk -l /dev/sda >foo" as
>> a way of exporting the actual partitioning. I am not sure fdisk would
>> be happy with 12 TB, though. But showing us the actual partitioning
>> might be a good idea.)
>>
>> {o.o} Joanne. (Imprinted on the old tools back in about '88 on of
>> all things "Amiga Unix.")
>>
>>
>>
