Please try harder when remounting in checkroot.sh
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sysvinit (Debian) |
Fix Released
|
Unknown
|
|||
sysvinit (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
Automatically imported from Debian bug report #259979 http://
Debian Bug Importer (debzilla) wrote : | #1 |
Debian Bug Importer (debzilla) wrote : | #2 |
Message-Id: <1090081294.
Date: Sat, 17 Jul 2004 12:21:35 -0400
From: "Grzegorz B. Prokopski" <email address hidden>
To: <email address hidden>
Subject: Please try harder when remounting in checkroot.sh
Package: initscripts
Version: 2.85-22
Severity: serious
Justification: Makes some systems unusable until fixed by hand.
In last few days I have seen the below problem happening on _several_
machines: sparc, kernel 2.4.21, ext3.
After an upgrade and a reboot I was getting errors from
/etc/init.
mainly two problems:
1. At first checkroot.sh tried to remount root read-only which
apparently failed and caused this error:
"You must specify the filesystem type"
which in turn caused this warning:
"*** ERROR! Cannot fsck root fs because it is not mounted read-only!"
2. But apparently the root already was in ro mode and what's worse,
the script failed to remount root in rw mode, so I got flooded with
errors from starting services and others that filesystem is
read-only and they were unable to write anything to it.
I've read in BTS about troubles with remounting root caused by bugs (or
differences) in older kernels and on different architectures. The
fix I did in checkroot.sh should not affect any platforms/machines
on which current checkroot.sh works.
I modified remounting root read-only in the following way:
if [ "$rootcheck" = yes ]
then
#
# Ensure that root is quiescent and read-only before fsck'ing.
#
if ! mount -n -o remount,ro $rootdev /
then
if ! mount -n -o remount,ro /
then
fi
fi
fi
And then remounting root read-write similarly:
#
# Remount root to final mode (rw or ro).
#
if ! mount -n -o remount,
then
mount -n -o remount,
fi
I am still getting "You must specify the filesystem type" error,
probably from the first remount, but the second try succeeds and
the system is able to come up like it used to do.
Please note, that this additional remount is only executed when
the first try fails, so it will not affect at all any configurations
in which the current script works well.
Hope this helps,
Grzegorz B. Prokopski
--
Grzegorz B. Prokopski <email address hidden>
Debian GNU/Linux http://
SableVM - LGPL'ed Java VM http://
Why SableVM ?!? http://
Fabio Massimo Di Nitto (fabbione) wrote : | #3 |
i have never seen this happening on any of my systems.
Matt Zimmerman (mdz) wrote : | #4 |
I have heard of similar things before, but never experienced it myself. This
particular case happened on sparc...
Matt Zimmerman (mdz) wrote : | #5 |
I think this is an indication of some sort of kernel/initrd screwup...it would
be nice to have confirmation from someone closer to the problem, though
In Debian Bug tracker #259979, Matt Zimmerman (mdz) wrote : | #6 |
This seems to be related to the fix for #239735. Your modifications (as
best I can tell at a glance, since you didn't provide a diff) try the
current method first, and then if it fails, try the old method.
This would still produce some alarming error messages in this case, though.
What architecture are you using, and what version of mount? #239735 seems
to say that this is actually a bug elsewhere in the system.
--
- mdz
Debian Bug Importer (debzilla) wrote : | #7 |
Message-ID: <email address hidden>
Date: Mon, 26 Jul 2004 14:30:53 -0700
From: Matt Zimmerman <email address hidden>
To: <email address hidden>
Cc: "Grzegorz B. Prokopski" <email address hidden>
Subject: Re: Please try harder when remounting in checkroot.sh
This seems to be related to the fix for #239735. Your modifications (as
best I can tell at a glance, since you didn't provide a diff) try the
current method first, and then if it fails, try the old method.
This would still produce some alarming error messages in this case, though.
What architecture are you using, and what version of mount? #239735 seems
to say that this is actually a bug elsewhere in the system.
--
- mdz
Matt Zimmerman (mdz) wrote : | #8 |
No evidence that this affects Warty architectures so far; submitter is
unresponsive. Downgrading.
In Debian Bug tracker #259979, Ian Gulliver (ian-penguinhosting) wrote : Issue Reintroduced | #9 |
Severity: critical
Justification: prevents the system from coming up
Tags: sarge
This issue was fixed in sysvinit-2.85-13, closing bug #239735, but
reintroduced in 2.85-21 in response to bug #254724. sparc is back to
experiencing the same issues:
-------
mount: you must specify the filesystem type
*** ERROR! Cannot fsck root fs because it is not mounted read-only!
mount: you must specify the filesystem type
-------
This is a clean 3.0R2 install, dist-upgraded to testing immediately
after install (today), and immediately rebooted.
--
Ian Gulliver
Penguin Hosting
"Failure is not an option; it comes bundled with your Microsoft products."
Debian Bug Importer (debzilla) wrote : | #10 |
Message-ID: <email address hidden>
Date: Thu, 29 Jul 2004 16:20:06 +0000
From: Ian Gulliver <email address hidden>
To: <email address hidden>
Subject: Issue Reintroduced
--b1450902dea57
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol=
--6WlEvdN9Dv0WHSBl
Content-Type: text/plain; charset=us-ascii
Content-
Content-
Severity: critical
Justification: prevents the system from coming up
Tags: sarge
This issue was fixed in sysvinit-2.85-13, closing bug #239735, but
reintroduced in 2.85-21 in response to bug #254724. sparc is back to
experiencing the same issues:
-------
mount: you must specify the filesystem type
*** ERROR! Cannot fsck root fs because it is not mounted read-only!
mount: you must specify the filesystem type
-------
This is a clean 3.0R2 install, dist-upgraded to testing immediately
after install (today), and immediately rebooted.
--=20
Ian Gulliver
Penguin Hosting
"Failure is not an option; it comes bundled with your Microsoft products."
--6WlEvdN9Dv0WHSBl
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBCSO2efI
5dC5iu4V2M6lvEt
=D2uJ
-----END PGP SIGNATURE-----
--6WlEvdN9Dv0WH
--b1450902dea57
Content-Type: application/
Version: 1.1
Mint-Hash: ySytfVjkj9/
To: <email address hidden>
Date: 20040729T16:20:06
Amount: 24
3e899c
--b1450902dea57
Matt Zimmerman (mdz) wrote : | #11 |
OK, maybe this is important after all. I still have no idea how to reproduce
it, though.
In Debian Bug tracker #259979, Thomas Hood (jdthood-aglu) wrote : merge | #12 |
severity 259979 normal
tags 259979 wontfix
merge 259979 255230
thanks
I am merging #259979 with #255230 which is marked 'wontfix'
because the problem has been fixed at the kernel level.
Miquel may still want to take a look at the code provided in
#259979, though.
--
Thomas
Hood
In Debian Bug tracker #259979, Miquel van Smoorenburg (miquels) wrote : Re: Bug#259979: merge | #13 |
On Thu, 29 Jul 2004 23:31:32, <email address hidden> wrote:
> severity 259979 normal
> tags 259979 wontfix
> merge 259979 255230
> thanks
>
> I am merging #259979 with #255230 which is marked 'wontfix'
> because the problem has been fixed at the kernel level.
> Miquel may still want to take a look at the code provided in
> #259979, though.
In fact, I did look at that and in the pending -23 I have
taken that approach. Code sample:
#
# Ensure that root is quiescent and read-only before fsck'ing.
#
# mount -n -o remount,ro / would be the correct syntax but
# mount can get confused when there is a "bind" mount defined
# in fstab that bind-mounts "/" somewhere else.
#
# So we use mount -n -o remount,ro $rootdev / but that can
# fail on older kernels on sparc64/alpha architectures due
# to a bug in sys_mount().
#
# As a compromise we try both.
#
if ! mount -n -o remount,ro $rootdev / 2>/dev/null &&
! mount -n -o remount,ro /
then
....
Mike.
Debian Bug Importer (debzilla) wrote : | #14 |
Message-Id: <email address hidden>
Date: Thu, 29 Jul 2004 21:31:32 GMT
From: <email address hidden>
To: <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: merge
severity 259979 normal
tags 259979 wontfix
merge 259979 255230
thanks
I am merging #259979 with #255230 which is marked 'wontfix'
because the problem has been fixed at the kernel level.
Miquel may still want to take a look at the code provided in
#259979, though.
--
Thomas
Hood
Matt Zimmerman (mdz) wrote : | #15 |
wontfix in Debian; apparently it's fixed in the kernel and probably doesn't
affect Warty's 2.6
Debian Bug Importer (debzilla) wrote : | #16 |
Message-ID: <email address hidden>
Date: Fri, 30 Jul 2004 00:48:04 +0200
From: Miquel van Smoorenburg <email address hidden>
To: <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#259979: merge
On Thu, 29 Jul 2004 23:31:32, <email address hidden> wrote:
> severity 259979 normal
> tags 259979 wontfix
> merge 259979 255230
> thanks
>
> I am merging #259979 with #255230 which is marked 'wontfix'
> because the problem has been fixed at the kernel level.
> Miquel may still want to take a look at the code provided in
> #259979, though.
In fact, I did look at that and in the pending -23 I have
taken that approach. Code sample:
#
# Ensure that root is quiescent and read-only before fsck'ing.
#
# mount -n -o remount,ro / would be the correct syntax but
# mount can get confused when there is a "bind" mount defined
# in fstab that bind-mounts "/" somewhere else.
#
# So we use mount -n -o remount,ro $rootdev / but that can
# fail on older kernels on sparc64/alpha architectures due
# to a bug in sys_mount().
#
# As a compromise we try both.
#
if ! mount -n -o remount,ro $rootdev / 2>/dev/null &&
! mount -n -o remount,ro /
then
....
Mike.
In Debian Bug tracker #259979, Miquel van Smoorenburg (miquels) wrote : Bug#259979: fixed in sysvinit 2.86-1 | #17 |
Source: sysvinit
Source-Version: 2.86-1
We believe that the bug you reported is fixed in the latest version of
sysvinit, which is due to be installed in the Debian FTP archive:
initscripts_
to pool/main/
sysv-rc_
to pool/main/
sysvinit_
to pool/main/
sysvinit_2.86-1.dsc
to pool/main/
sysvinit_
to pool/main/
sysvinit_
to pool/main/
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Miquel van Smoorenburg <email address hidden> (supplier of updated sysvinit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.7
Date: Fri, 30 Jul 2004 14:17:05 +0200
Source: sysvinit
Binary: sysv-rc sysvinit initscripts
Architecture: source i386 all
Version: 2.86-1
Distribution: unstable
Urgency: medium
Maintainer: Miquel van Smoorenburg <email address hidden>
Changed-By: Miquel van Smoorenburg <email address hidden>
Description:
initscripts - Standard scripts needed for booting and shutting down
sysv-rc - Standard boot mechanism using symlinks in /etc/rc?.d
sysvinit - System-V like init
Closes: 244908 248210 250089 255303 255820 255849 255880 256726 258065 259971 259979 261342
Changes:
sysvinit (2.86-1) unstable; urgency=medium
.
* Better algorithm for pidof (closes: #248210)
* Include fsck.nfs.8 (closes: #250089)
* Include new skeleton script (closes: #244908)
* Better error message on failure to find path to mtab (closes: #255820)
* Add support for fstype ncp (alias for ncpfs) (closes: #259971)
* Touch /tmp/.clean earlier (closes: #255303)
* Don't include halt and reboot for hurd-i386 (closes: #255880)
* Remove XSIisms in mountvirtfs and invoke-rc.d (closes: #256726)
* Add "-t $roottype" to mount -f for / (closes: #255849)
* Always initialize PATH (to /bin:/usr/
* Try harder to remount ro and rw (closes: #259979)
* Add support for LABEL=/UUID= in checkroot.sh (closes: #261342)
Files:
cbb7b8ffd2d051
e27bd78e92443b
73803f3b8d7bb4
5916bdf9469cca
f9e19cb06699c3
9115b0d88d2bd7
-----BEGIN PGP SIGNATURE----- iQB1AwUBQQuhdFi
Version: GnuPG v1.2.4 (GNU/Linux)
Debian Bug Importer (debzilla) wrote : | #18 |
Message-Id: <email address hidden>
Date: Sat, 31 Jul 2004 09:49:55 -0400
From: Miquel van Smoorenburg <email address hidden>
To: <email address hidden>
Subject: Bug#259979: fixed in sysvinit 2.86-1
Source: sysvinit
Source-Version: 2.86-1
We believe that the bug you reported is fixed in the latest version of
sysvinit, which is due to be installed in the Debian FTP archive:
initscripts_
to pool/main/
sysv-rc_
to pool/main/
sysvinit_
to pool/main/
sysvinit_2.86-1.dsc
to pool/main/
sysvinit_
to pool/main/
sysvinit_
to pool/main/
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Miquel van Smoorenburg <email address hidden> (supplier of updated sysvinit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.7
Date: Fri, 30 Jul 2004 14:17:05 +0200
Source: sysvinit
Binary: sysv-rc sysvinit initscripts
Architecture: source i386 all
Version: 2.86-1
Distribution: unstable
Urgency: medium
Maintainer: Miquel van Smoorenburg <email address hidden>
Changed-By: Miquel van Smoorenburg <email address hidden>
Description:
initscripts - Standard scripts needed for booting and shutting down
sysv-rc - Standard boot mechanism using symlinks in /etc/rc?.d
sysvinit - System-V like init
Closes: 244908 248210 250089 255303 255820 255849 255880 256726 258065 259971 259979 261342
Changes:
sysvinit (2.86-1) unstable; urgency=medium
.
* Better algorithm for pidof (closes: #248210)
* Include fsck.nfs.8 (closes: #250089)
* Include new skeleton script (closes: #244908)
* Better error message on failure to find path to mtab (closes: #255820)
* Add support for fstype ncp (alias for ncpfs) (closes: #259971)
* Touch /tmp/.clean earlier (closes: #255303)
* Don't include halt and reboot for hurd-i386 (closes: #255880)
* Remove XSIisms in mountvirtfs and invoke-rc.d (closes: #256726)
* Add "-t $roottype" to mount -f for / (closes: #255849)
* Always initialize PATH (to /bin:/usr/
* Try harder to remount ro and rw (closes: #259979)
* Add support for LABEL=/UUID= in checkroot.sh (closes: #261342)
Files:
cbb7b8ffd2d051
e27bd78e92443b
73803f3b8d7bb4
5916bdf9469cca
f9e19cb06699c3
Changed in sysvinit: | |
status: | Unknown → Fix Released |
Automatically imported from Debian bug report #259979 http:// bugs.debian. org/259979