mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: Enrico Joerns <ejo@pengutronix.de>
To: rauc@pengutronix.de
Cc: jlu@pengutronix.de
Subject: Re: [RAUC] Partition resize
Date: Wed, 6 Feb 2019 18:13:07 +0100	[thread overview]
Message-ID: <5d9e0af1-665f-d975-3665-e52c0b33d720@pengutronix.de> (raw)
In-Reply-To: <1501689280.2890.17.camel@pengutronix.de>

On 8/2/17 5:54 PM, Jan Lübbe wrote:
> Hi Caglar,
> 
> On Wed, 2017-08-02 at 11:53 +0000, Kilimci, Caglar wrote:
>> I have a question or a missing point. After the successful update, my
>> partition size is reduced. If I extend it, it would be as expected.
>> Like this:
>>
>> Before update:
>> root@phyboard-regor-am335x-1:~# df -h
>> Filesystem                Size      Used Available Use% Mounted on
>> /dev/root               375.8M    207.7M    144.6M  59% /
>> devtmpfs                240.9M         0    240.9M   0% /dev
>> ..
>>
>> After update:
>> root@phyboard-regor-am335x-1:~# df -h
>> Filesystem                Size      Used Available Use% Mounted on
>> /dev/root               305.8M    207.7M     77.9M  73% /
>> ..
>>
>> Is there any automatic way to extend partition or am I doing
>> something wrong?
> 
> I'm guessing your root-FS type is ext4? In that case, you are probably
> installing a filesystem image with was produced with a fixed size less
> than the device size. RAUC doesn't modify the image during
> installation.
> 
> The easiest way for you is probably to use a .tar.gz archive instead of
> the filesystem image. Then RAUC will format the partiton using
> mkfs.ext4 and extract the tar into the new filesystem. In that case no
> resize is needed.
> 
> Alternatively, it could be useful to optionally let RAUC call resize2fs
> on installation of a ext4 image.
> 
> Regards,
> Jan

FTR: For those who require this: With https://github.com/rauc/rauc/pull/403 
merged we have support for this in master now.

Regards, Enrico

-- 
Pengutronix e.K.                           | Enrico Jörns                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

      parent reply	other threads:[~2019-02-06 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 11:53 Kilimci, Caglar
2017-08-02 15:54 ` Jan Lübbe
2017-08-03  9:54   ` [RAUC] [External] " Kilimci, Caglar
2019-02-06 17:13   ` Enrico Joerns [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=5d9e0af1-665f-d975-3665-e52c0b33d720@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=jlu@pengutronix.de \
    --cc=rauc@pengutronix.de \
    /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