fdisk delima

noir911 · 12-01-2006, 01:34 AM

fdisk shows I got a 146GB disk. But df shows no entry for "/dev/sda3" Moreover /dev/sda3 is showing as a Win95 slice!

I was wondering how can I safely allocate more space to /dev/sda1 using fdisk which is running out of disk space.

Quote:

athena:/ # fdisk -l

Disk /dev/sda: 146.8 GB, 146813222912 bytes
255 heads, 63 sectors/track, 17849 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 638 5124703+ 83 Linux
/dev/sda2 * 639 663 200812+ 83 Linux
/dev/sda3 6931 17849 87706867+ f W95 Ext'd
(LBA)
/dev/sda4 6539 6930 3148740 82 Linux swap
/dev/sda5 6931 8236 10490413+ 83 Linux

Partition table entries are not in disk order

athena:/ # df -h -P
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 4.9G 4.1G 890M 83% /
tmpfs 1013M 56K 1013M 1% /dev/shm
/dev/sda2 197M 39M 158M 20% /boot
/dev/sda5 11G 639M 9.4G 7% /var

acid_kewpie · 12-01-2006, 02:04 AM

sda3 is an extended partition, which contains logical partitions, you can't write data to sda3, and even more so, df only shows mouted partitions.

adding the space to sda1 wouldn't be fun, you'd need to look into parted or a similar tool to move other partitions, but i'd be more interested with sda5 - what is that all about?

noir911 · 12-01-2006, 02:14 AM

Quote:

Originally Posted by acid_kewpie

sda3 is an extended partition, which contains logical partitions, you can't write data to sda3, and even more
so, df only shows mouted partitions.

then why do I see sda3 with a Win95 id?

Quote:

Originally Posted by acid_kewpie

adding the space to sda1 wouldn't be fun, you'd need to look into parted or a similar tool to move other partitions

the disk is 146.8 GB. How can I know where's my unused/unallocated disk space?

acid_kewpie · 12-01-2006, 02:25 AM

Because that's what it is. They were invented by M$ when win95 came out...

Just look at the partition table itself, for example yours extended partition goes up to 17849 cylinders, which is the capacity of the disk, but the last partition ends at 8236, so you've got half your drive still unpartitioned.

noir911 · 12-01-2006, 03:03 AM

I did the following -

Code:

zeus:~ # fdisk /dev/sda

Command (m for help): p 

Disk /dev/sda: 146.8 GB, 146813222912 bytes
255 heads, 63 sectors/track, 17849 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         638     5124703+  83  Linux
/dev/sda2   *         639         663      200812+  83  Linux
/dev/sda3            6931       17849    87706867+   f  W95 Ext'd (LBA)
/dev/sda4            6539        6930     3148740   82  Linux swap
/dev/sda5            6931        8236    10490413+  83  Linux


Command (m for help): n
First cylinder (8237-17849, default 8237):
Using default value 8237
Last cylinder or +size or +sizeM or +sizeK (8237-17849, default 17849):
Using default value 17849

Command (m for help): p

Disk /dev/sda: 146.8 GB, 146813222912 bytes
255 heads, 63 sectors/track, 17849 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         638     5124703+  83  Linux
/dev/sda2   *         639         663      200812+  83  Linux
/dev/sda3            6931       17849    87706867+   f  W95 Ext'd (LBA)
/dev/sda4            6539        6930     3148740   82  Linux swap
/dev/sda5            6931        8236    10490413+  83  Linux
/dev/sda6            8237       17849    77216391   83  Linux

Partition table entries are not in disk order

Looks like it created a new /dev/sda6 partition. I didn't save it for I fear of losing data. Would it be safe to go ahead with this one?

acid_kewpie · 12-01-2006, 03:04 AM

yeah that looks fine, no danger at all.