GNU bug report logs - #56209
Shepherd 0.9 not cleanly unmounting root

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#56250: closed (File systems not cleanly unmounted?)
Date: Fri, 01 Jul 2022 10:30:03 +0000

[Message part 1 (text/plain, inline)]

Your message dated Fri, 01 Jul 2022 12:29:31 +0200
with message-id <87czep5do4.fsf <at> gnu.org>
and subject line Re: bug#56209: Shepherd 0.9 not cleanly unmounting root
has caused the debbugs.gnu.org bug report #56209,
regarding File systems not cleanly unmounted?
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
56209: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56209
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: bug-guix <at> gnu.org
Subject: File systems not cleanly unmounted?
Date: Mon, 27 Jun 2022 10:02:33 +0200

Hi!

I don’t reboot my laptop very often but over the last couple of months
maybe, I’ve had the impression that I see the “not cleanly unmounted”
message from fsck.ext4 during boot almost every time.

Someone on IRC just reported seeing the same kind of message for
/boot/efi (VFAT) and I’ve seen it on a recently-installed machine,
though I didn’t investigate.

It’s benign but it suggests that file systems are not being properly
unmounted upon shutdown.

Anyone else seeing that?  Ideas as to what might be wrong?

Thanks,
Ludo’.

[Message part 3 (message/rfc822, inline)]

From: Ludovic Courtès <ludo <at> gnu.org>
To: angry rectangle <angryrectangle <at> cock.li>
Cc: 56209-done <at> debbugs.gnu.org
Subject: Re: bug#56209: Shepherd 0.9 not cleanly unmounting root
Date: Fri, 01 Jul 2022 12:29:31 +0200

Hi,

angry rectangle <angryrectangle <at> cock.li> skribis:

> I tried your patch on one of my computers and it works.

Thanks for testing.

Pushed as 0483c71cc5aeb3b69f6deb154fe12c0b2e6dc17f.  The reason is took
me more time is that I wanted to have a system test for that to make
sure it doesn’t come back to haunt us in the future.  Now we should be
fine.  :-)

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.