On 5/16/22 13:39, Panu Matilainen wrote:
On 5/13/22 21:54, Jason L Tibbitts III wrote:
So I went to do a dnf system-upgrade from F35 to F36 on a test machine,
as part of my usual testing. In the middle of the process, it appears
that /var filled up and that left the system in an unfortunate
On 5/16/22 18:55, Nico Kadel-Garcia wrote:
> On Mon, May 16, 2022 at 2:55 PM Dusty Mabe wrote:
>>
>>
>>
>> On 5/16/22 12:10, Chris Murphy wrote:
>>> On Fri, May 13, 2022 at 3:20 PM przemek klosowski via devel
>>
>>>
>>>
Unfortunately, I believe that the current upgrade workflow requires a
On Mon, May 16, 2022 at 2:55 PM Dusty Mabe wrote:
>
>
>
> On 5/16/22 12:10, Chris Murphy wrote:
> > On Fri, May 13, 2022 at 3:20 PM przemek klosowski via devel
>
> >
> >
> >> Unfortunately, I believe that the current upgrade workflow requires a
> >> root disk three times the total installed
On Mon, May 16, 2022 at 12:14 PM Chris Murphy wrote:
>
> On Mon, May 16, 2022 at 8:07 AM Nico Kadel-Garcia wrote:
> > An in-place system upgrade is not an "unexpected event". It is a risky
> > transaction.
> >
> > The big space pig is not /var/lib/rpm: it's /var/cache/dnf, which can
> > be quite
On 5/16/22 05:06, Nico Kadel-Garcia wrote:
On Mon, May 16, 2022 at 6:39 AM Panu Matilainen wrote:
Rpm has had a heuristic on the rpmdb growth for years, but no heuristics
can help against unexpected events eating the space.
An in-place system upgrade is not an "unexpected event". It is a
On 5/16/22 12:10, Chris Murphy wrote:
> On Fri, May 13, 2022 at 3:20 PM przemek klosowski via devel
>
>
>> Unfortunately, I believe that the current upgrade workflow requires a
>> root disk three times the total installed package size: each package is
>> there as the original version, the RPM
On Mon, May 16, 2022 at 8:07 AM Nico Kadel-Garcia wrote:
> An in-place system upgrade is not an "unexpected event". It is a risky
> transaction.
>
> The big space pig is not /var/lib/rpm: it's /var/cache/dnf, which can
> be quite flooded by updated packages tool suites such as openoffice
> or
On Fri, May 13, 2022 at 3:20 PM przemek klosowski via devel
wrote:
>
> I had issues with this for several releases now, although I never got a
> broken upgrade like you're reporting: every time so far I got a message
> 'you need additional 4GB on /' before the actual upgrade started. It
> would
On Mon, 2022-05-16 at 02:05 +0100, Sérgio Basto wrote:
> On Fri, 2022-05-13 at 13:54 -0500, Jason L Tibbitts III wrote:
> > So I went to do a dnf system-upgrade from F35 to F36 on a test
> > machine,
> > as part of my usual testing. In the middle of the process, it
> > appears
> > that /var
On 5/16/22 15:06, Nico Kadel-Garcia wrote:
On Mon, May 16, 2022 at 6:39 AM Panu Matilainen wrote:
On 5/13/22 21:54, Jason L Tibbitts III wrote:
So I went to do a dnf system-upgrade from F35 to F36 on a test machine,
as part of my usual testing. In the middle of the process, it appears
that
On Mon, May 16, 2022 at 6:39 AM Panu Matilainen wrote:
>
> On 5/13/22 21:54, Jason L Tibbitts III wrote:
> > So I went to do a dnf system-upgrade from F35 to F36 on a test machine,
> > as part of my usual testing. In the middle of the process, it appears
> > that /var filled up and that left the
On 5/13/22 21:54, Jason L Tibbitts III wrote:
So I went to do a dnf system-upgrade from F35 to F36 on a test machine,
as part of my usual testing. In the middle of the process, it appears
that /var filled up and that left the system in an unfortunate state.
Surprisingly (to me) it did boot with
Dne 13. 05. 22 v 20:54 Jason L Tibbitts III napsal(a):
3) Is there any better way to handle a lack of space in /var during an
RPM transaction?
I very often mount /var/cache/dnf as tmpfs as servers have more memory/swap
than rootfs.
4) Can we estimate how large the file will grow, and refuse
On Fri, 2022-05-13 at 13:54 -0500, Jason L Tibbitts III wrote:
> So I went to do a dnf system-upgrade from F35 to F36 on a test
> machine,
> as part of my usual testing. In the middle of the process, it
> appears
> that /var filled up and that left the system in an unfortunate state.
>
Ooops: forgot the awk statement:
dnf clean all --enablerepo=*
dnf check-update | grep '^[a-zA-Z0-0]' | awk '{print $1}' |while
read name; do
dnf update "$name" -y
done
On Sat, May 14, 2022 at 8:35 AM Nico Kadel-Garcia wrote:
>
> On Fri, May 13, 2022 at 2:54 PM Jason L
On Fri, May 13, 2022 at 2:54 PM Jason L Tibbitts III wrote:
>
> So I went to do a dnf system-upgrade from F35 to F36 on a test machine,
> as part of my usual testing. In the middle of the process, it appears
> that /var filled up and that left the system in an unfortunate state.
> Surprisingly
I had issues with this for several releases now, although I never got a
broken upgrade like you're reporting: every time so far I got a message
'you need additional 4GB on /' before the actual upgrade started. It
would be sad if the free space estimation code didn't work and allowed
broken,
So I went to do a dnf system-upgrade from F35 to F36 on a test machine,
as part of my usual testing. In the middle of the process, it appears
that /var filled up and that left the system in an unfortunate state.
Surprisingly (to me) it did boot with a random mix of F35 and F36
packages and even
18 matches
Mail list logo
