30GB partition only allowing <1GB ?

[mb0]

i created the partition /dev/sda2 to be 30GB, (fdisk shows 31254426 blocks), but `df /dev/sda2` shows it's size as 950MB, and i have just been told it's full when copying files to it. What's up with this??

[Lee]

df shows the free space on a mounted fs, so try

df /mnt/sda2

If sda2 is mounted this should show its free space,otherwise it will show the free space of the root fs (which is likely in RAM, so not large)

[bmarkus]

Also don't forget to mount partion. Use

df -h ...

to get result in "human readable" units.

[mb0]

It is mounted and `df /mountpoint` returns exactly the same

(and FWIW it is already bigger than the RAM in the system)

[tinypoodle]

In case you mistakenly exhausted the space of your rootfs, better delete those files as soon as possible to prevent any consequences.

[tinypoodle]

Best to run a fsck, after umounting first.

[mb0]

fsck /dev/sda2:

Code: [Select]

fsck (busybox 1.19.3, 2011-10-30 01:47:29 UTC)
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda2 has been mounted 922 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found.  Create<y>? yes

Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda2: 162/62848 files (42.0% non-contiguous), 249033/251007 blocks


[tinypoodle]

That filesystem looks suspicious in several aspects...

mounted 922 times without being checked - is that about consistent with its history?

42.0% non-contiguous - unusually high!

/lost+found not found. - shouldn't occur without serious fs corruption (unless it was rm'ed manually)

Which fs type is that exactly? journalled or not?

[mb0]

it's ext4.. 922 times does seem higher than i would have expected (probably expected closer to 90?) and it's never been fsck'd..

[tinypoodle]

Can you run another fsck but with the "-v" option and post output again?

[mb0]

sudo fsck -v /dev/sda2:

Code: [Select]

fsck (busybox 1.19.3, 2011-10-30 01:47:29 UTC)
e2fsck 1.41.14 (22-Dec-2010)
/dev/sda2: clean, 162/62848 files, 249033/251007 blocks

intersting huh?

[tinypoodle]

Oh, sorry, make that "-vf".

[mb0]

Code: [Select]

fsck (busybox 1.19.3, 2011-10-30 01:47:29 UTC)
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

     162 inodes used (0.26%)
      68 non-contiguous files (42.0%)
       0 non-contiguous directories (0.0%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 150/2
  249033 blocks used (99.21%)
       0 bad blocks
       1 large file

     139 regular files
      14 directories
       0 character device files
       0 block device files
       0 fifos
       0 links
       0 symbolic links (0 fast symbolic links)
       0 sockets
--------
     153 files


[tinypoodle]

"249033 blocks used (99.21%)" appears to agree with output of df.

[mb0]

yes, but..

fdisk /dev/sda, 'p'

Code: [Select]

Disk /dev/sda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1   *        3892        4864     7815622+ 83 Linux
/dev/sda2               1        3891    31254426  83 Linux

Partition table entries are not in disk order
Which is in line with what i expected.