From: Frank Sorenson <frank@tuxrocks.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
itamar <itamar@ispbrasil.com.br>,
uml-user <user-mode-linux-user@lists.sourceforge.net>
Subject: Re: [uml-user] Re: [uml-devel] resizing root_fs
Date: Thu, 14 Apr 2005 15:53:26 -0600 [thread overview]
Message-ID: <425EE656.8040108@tuxrocks.com> (raw)
In-Reply-To: <200504142303.43628.blaisorblade@yahoo.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Blaisorblade wrote:
> On Wednesday 13 April 2005 06:07, itamar wrote:
>
>>dd if=/dev/zero of=root_fs.ext3 bs=1 count=1 seek=40G conv=notrunc
>
> Right enlarging command, it seems.
>
>>[root@router conacci]# resize2fs -p root_fs.ext3
>>resize2fs 1.36 (05-Feb-2005)
>>resize2fs: File too large while trying to determine filesystem size
>
>
> This old resize2fs has a problem because the file is >= 2G (or something like
> that), it seems... probably truncating the file to a more normal size and
> retesting will work, so you possibly hit a resize2fs bug... at least so I
> guess. It's strange though, but I don't see any other possible explaination.
Because the filesystem size was so small to begin with (256 MB if I
remember correctly), inodes only represent 1K of data. Resizing the
filesystem then creates more 1K blocks, but you run into the maximum
number of inodes that the filesystem can create. Try to determine the
maximum size you can resize to, or create the new large filesystem and
move everything from the old to the new.
Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
frank@tuxrocks.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCXuZWaI0dwg4A47wRAnFSAKCdfYAJsopZh/GmLiVvDiL/sTgoDgCeJy9R
KpeFtqFoDf9WkGOdEY1g03Y=
=ELrL
-----END PGP SIGNATURE-----
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-04-14 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 4:07 [uml-devel] resizing root_fs itamar
2005-04-14 21:03 ` Blaisorblade
2005-04-14 21:53 ` Frank Sorenson [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=425EE656.8040108@tuxrocks.com \
--to=frank@tuxrocks.com \
--cc=blaisorblade@yahoo.it \
--cc=itamar@ispbrasil.com.br \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.