Hey Samuel,

Thanks.
Now i am also doing upgrades, and compilations and random things now daily
wanting to see if i can get it to show those issues.
I have deployed the latest ext2fs (so with mmap patch, and also the other
recovery_needed patch that are both in the repo).

This is what i do.
I run it with
qemu-system-x86_64 \
                                                 -m 512 -smp 4 -cpu host
-enable-kvm -machine pc \
                                                 -drive
file=/home/loshmi/Projects/hurd/debian-hurd-i386-20260314.img,if=ide,index=0,format=raw,cache=writethrough
\
                                                 -device ahci,id=ahci1 \
                                                 -drive
id=compil,if=none,format=raw,file=/home/loshmi/Projects/hurd/compil.img,cache=writeback
\
                                                 -device
ide-hd,drive=compil,bus=ahci1.0 \
                                                 -netdev user,id=net0,net=
192.168.76.0/24,dhcpstart=192.168.76.5,hostfwd=tcp:127.0.0.1:2222-:22 \
                                                 -device e1000,netdev=net0 \
                                                 -display none -no-reboot
-serial file:hurd_debug.log

I give it only 512mb of ram hoping it would stress test it a bit.
Both the root image ext2 is journaled, and the compil.img has a journaled
ext2 in it.

I am doing upgrades daily (two days now).
I am also recompiling hurd and gnumach.

Today I additionally did: (inside hurd)
$ sudo settrans -a /mnt/stress /hurd/ext2fs.static /dev/sd0
ext2fs: journaling enabled on /dev/sd0
loshmi@debian:~$ cd /mnt/stress/
loshmi@debian:/mnt/stress$ ls
lost+found  test
loshmi@debian:/mnt/stress$ cd test/
$ wget https://cdn.kernel.org/pub/linux/kernel/v7.x/linux-7.2.3.tar.xz
--2026-09-04 04:16:12--
https://cdn.kernel.org/pub/linux/kernel/v7.x/linux-7.2.3.tar.xz
Resolving cdn.kernel.org (cdn.kernel.org)... 151.101.65.176,
151.101.193.176, 151.101.1.176, ...
Connecting to cdn.kernel.org (cdn.kernel.org)|151.101.65.176|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 160060344 (153M) [application/x-xz]
Saving to: 'linux-7.2.3.tar.xz'

linux-7.2.3.tar.xz
 100%[=====================================================>] 152.64M
 7.66MB/s    in 53s

2026-09-04 04:17:04 (2.90 MB/s) - 'linux-7.2.3.tar.xz' saved
[160060344/160060344]

loshmi@debian:/mnt/stress/test$ tar -xf linux-7.2.3.tar.xz

loshmi@debian:/mnt/stress/test$
loshmi@debian:/mnt/stress/test$ ls
linux-7.2.3  linux-7.2.3.tar.xz

So far nothing. Either i untar, or compile, or upgrade...everything just
works without lockup or corruption for now.

Let me know if you think i should change something to more reflect what you
have, i really want to see why it locks up (if it still does that).

I will continue to do this daily, hoping to catch it.

Thanks
Milos



On Wed, Sep 2, 2026 at 4:14 PM Samuel Thibault <[email protected]>
wrote:

> Hello,
>
> Milos Nikic, le mar. 01 sept. 2026 21:12:53 -0700, a ecrit:
> > Question about how you get it to lock up? Is your root system also
> journaled
> > and then you do a massive apt upgrade?
>
> Yes, that is it. It does not always lock up, but since I upgrade roughly
> daily it does happen now and then.
>
> Samuel
>

Reply via email to