linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Benson <erbenson@alaska.net>
To: Eric Peden <ericpeden@homemail.com>
Cc: LinuxPPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: partition size funkiness
Date: Tue, 23 May 2000 23:01:28 -0800	[thread overview]
Message-ID: <20000523230128.F7243@plato.local.lan> (raw)
In-Reply-To: <B550A5BA.464A%ericpeden@homemail.com>; from ericpeden@homemail.com on Tue, May 23, 2000 at 09:16:42PM -0500

[-- Attachment #1: Type: text/plain, Size: 2507 bytes --]

On Tue, May 23, 2000 at 09:16:42PM -0500, Eric Peden wrote:

[deletia]
> 
> I've begun to suspect that my problems are due to the method I used to
> "re-partition" the drive; I simply used pdisk to re-arrange the partition
> map, thus doing a non-destructive repartitioning. I've only managed to find
> one mention of a problem similar to mine at:

how exactly did you backup/restore the data?  you cannot just change
the partition tables without doing something to the filesystems too,
you can use ext2resize, or tar up the data and mke2fs the partition,
and untar everything back.  but if you just changed the partition
table and did nothing to the filesystems you are looking at filesystem
corruption and massive data loss to occur very soon.  this is because
the filesystem has its own idea about the size of the partition.  

> http://slashdot.org/askslashdot/99/08/09/0315246.shtml
> 
> The cause is different, and of course no solution is offered, but the
> symptoms are the same. Is partition information stored somewhere other than
> the partition map? Is df just reading this information incorrectly, or is
> the extra space on /dev/sda7 truly unusable? Is there some low-level
> information I could modify to properly reflect the size of root?

partition sizes just define to the kernel how much space it should
allocate to a given device node eg /dev/hda2.  the filesystem when
mounted has its own definition of its size, and this has nothing to do
with the partition size.  if they do not match though you can end up
in trouble, either the partition is larger then the filesystem and you
have hidden wasted space or you have the filesystem too large and you
end up writing data off the end of the device (which the kernel won't
permit i don't think) either way its a bad thing.  

this is why i am not a big fan of screwing with partitions in
non-destructive ways, it just is more trouble then it is worth and
usually does not work that well.

> Again, help is appreciated...

wipe your partition table entirely, partition everything properly and
install debian while your at it ;-)

i know its harsh advice but really i think your just going to waste
alot of time and trouble messing around trying to get this fixed with
a high liklyhood of destroying the filesystems anyway, why bother with
the headache you will be happier in the long run with a properly
partitioned, cleaned up system. 

-- 
Ethan Benson
http://www.alaska.net/~erbenson/

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

      parent reply	other threads:[~2000-05-24  7:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-24  2:16 partition size funkiness Eric Peden
2000-05-24  5:51 ` Michel Lanners
2000-05-24  7:01 ` Ethan Benson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20000523230128.F7243@plato.local.lan \
    --to=erbenson@alaska.net \
    --cc=ericpeden@homemail.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).