[TriLUG] Resizing partition with ext3 file system

[Rick DeNatale]

I was going the other way. I made the partition bigger but kept it at
the same starting cylinder. As I understood it all the partition table
does is define where the partition starts and ends, and some other
attributes like whether it's bootable or not. The data isn't changed. 
The filesystem formatting is all relative to the starting cylinder of
the partition.

I still don't know what happened.

Before I had this:

/dev/hdc1 start=x, end=y
/dev/hdc2  start=y+1, end =z
freespace start=z+1, end=end of disk

after fdisk I had
/dev/hdc1 start=x, end=y
/dev/hdc2  start=y+1, end =end of disk

then I did the resize2fs, and all hell broke loose.


On Mon, 24 Jan 2005 16:03:13 -0500, Ian Kilgore <ian at trilug.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> | Umm there is a difference.  If you are NOT using LVM them Jason's case
> | does not apply and I am not sure that deleting the partition with fdisk
> | will work...  I think that once you fry the partition table and inode
> | relationship that you are out of luck.
> 
> Not quite.  I did this about a month ago (it was reiserfs, but it still
> applys), by resizing the actual filesystem with resizereiserfs or
> reiserfsresize (dont quite remember =]), and then deleting and
> recreating the partition with fdisk.  Worked fine.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFB9WKRwsRpgTiXSOERAhKKAKCUSCW8qKIMA06OTCgfIX78nUPV9ACdH6H6
> yvhXKZwU2cXWPnxkmKod+p8=
> =M67j
> -----END PGP SIGNATURE-----
> --
> TriLUG mailing list        : http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ  : http://trilug.org/faq/
> TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
> TriLUG PGP Keyring         : http://trilug.org/~chrish/trilug.asc
>