[ale] Seagate Hdd Not Lining Up!?

[JK]

It looks as if GParted resized the partition, but didn't do anything to
the filesystem.  They're two different things: a "partition" is a physical
chunk of disk, whereas a "filesystem" is the meta-data that gets written
into a partition's iron oxide in order to keep track of which parts of the
disk platter are actually in use, and for what.  So the filesystem records
things like, "disk sectors 1 thru 5,000,000 are part of this filesystem",
and "blocks 1,7, and 8400 belong to file foo.txt".  Changing the size
of a partition doesn't do anything to the data ON the partition (the
filesystem); you have to resize the filesystem in order to add the
extra disk space to it.

-- JK

Marc Ferguson wrote:
> 
> On Sat, Jul 11, 2009 at 9:28 PM, Michael B. Trausch <mbt at zest.trausch.us 
> <mailto:mbt at zest.trausch.us>> wrote:
> 
>     On Sat, 11 Jul 2009, Brian Pitts wrote:
> 
>      > Marc Ferguson wrote:
>      > > [root at fergatron ~]# fdisk -l /dev/sdb
>      >>
>      >> Disk /dev/sdb: 320.0 GB, 320072933376 bytes
>      >> 255 heads, 63 sectors/track, 38913 cylinders
>      >> Units = cylinders of 16065 * 512 = 8225280 bytes
>      >> Disk identifier: 0x0b99f72f
>      >>
>      >>    Device Boot      Start         End      Blocks   Id  System
>      >> /dev/sdb1               1       38913   312568641   83  Linux
>      >> [root at fergatron ~]#
>      >>
>      >> I'm not fully comprehending these outputs. Do they indicate
>     anything of
>      >> significance?
>      >>
>      >
>      > That looks like one (roughly) 320 GB partition to me. You could
>     try to
>      > grow the filesystem by running the following as root
>      >
>      > umount /dev/sdb1
>      > e2fcsk -f /dev/sdb1
>      > resize2fs -p /dev/sdb1
>      > mount /dev/sdb1 /media/backup
> 
>     If the kernel is recent enough, and the filesystem is extXfs, it
>     should be
>     growable online.
> 
>            --- Mike
>     _______________________________________________
>     Ale mailing list
>     Ale at ale.org <mailto:Ale at ale.org>
>     http://mail.ale.org/mailman/listinfo/ale
> 
> 
> Well Brian and Folks, 66GB used and 227.4 GB free. Well done.  I don't 
> understand how simply running a resize program fixed my issue. Should I 
> have not formatted the drive via GParted? Or was there something I 
> should have done in GParted?  Thanks for a little clarification and 
> thanks for helping me expand this drive.
> 
> The commands worked and I now have
> 
> [root at fergatron ~]# e2fsck -f /dev/sdb1
> e2fsck 1.41.4 (27-Jan-2009)
> 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
> DataBackup: 89242/3842048 files (0.5% non-contiguous), 13643580/15360140 
> blocks
> [root at fergatron ~]# man resize2fs
> Formatting page, please wait...
> [root at fergatron ~]# resize2fs -p /dev/sdb1
> resize2fs 1.41.4 (27-Jan-2009)
> Resizing the filesystem on /dev/sdb1 to 78142160 (4k) blocks.
> Begin pass 1 (max = 1916)
> Extending the inode table     XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
> The filesystem on /dev/sdb1 is now 78142160 blocks long.
> 
> [root at fergatron ~]# mount /dev/sdb1 /media/backup
> [root at fergatron ~]# 
> 
> 
> -- 
> Marc F.
> 
> "When life gives me lemons... I make Linuxaide, hmm good stuff!"
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale