Your message dated Sun, 10 Mar 2013 22:17:35 +0000
with message-id <e1ueoyh-0002fk...@franck.debian.org>
and subject line Bug#701936: fixed in btrfs-tools 
0.19+20130131-3+really20121004-1
has caused the Debian Bug report #701936,
regarding btrfs can't fsck /run/rootdev on boot with sysvinit
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
701936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701936
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: btrfs-tools
Version: 0.19+20130131-2
Severity: critical
Justification: renders systems with btrfs as root file-system unbootable

Hi,

Axel Beckert wrote on Wed, 27 Feb 2013 20:01:30 +0100:
> >  btrfs-tools (0.19+20130131-2) unstable; urgency=low
> >  .
> >    * Replacing fsck.btrfs with wrapper arround 'btrfs check' to avoid
> >      different behaviour based on the filename btrfs is copied to (Closes:
> >      #701776).
> 
> Thanks for the quick fix, but unfortunately the problem persists, just
> with a different error message and a different exit-code, but with the
> same symptom: The system fails to start.
> 
> check_mounted(): Could not open /run/rootdev
> Could not check mount status: No such device or address
> fsck died with exit status 250

There's one more confirmation that there's still an issue which breaks
systems, even with the newest version, at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701776#65

Additionally, several people contacted me on Jabber/IRC about how to
fix this issue, too, so I'm posting a recipe at the end of this mail
and also Cc this mail to #701776.

> Do you have any preference if #701776 should be reopend or if a new
> bug should be filed for that?

Since I didn't get a reply from Daniel on this question within a day,
I'm herewith filing a new bug report as the issue may have a different
cause despite very similar symptoms and the affected systems still
being broken if you don't downgrade btrfs-tools to 0.19+20121004-1 or
earlier.

As I already wrote in #701776, I consider such breakage of severity
critical since http://www.debian.org/Bugs/Developer.en.html#severities
defines "critical" as "makes unrelated software on the system (or the
whole system) break". I see this condition as given.


For all those who are also suffering from this issue, too, here's the
recipe how I downgraded btrfs-tools to the version from testing again
on my system:

At the maintenance mode password prompt, enter the root password.

You may need to add /sbin and /usr/sbin to the path depending on your
login shell setup. Thanks Christian Stalp!
# export PATH="/sbin:/usr/sbin:$PATH"

With the default setup, sourcing /etc/profile should suffice.
# . /etc/profile

Mount the root file system read-write:
# mount -o remount,rw /

Mount the /boot partition, if existing:
# mount /boot

Either get network, ...
# dhclient eth0

(Since Julien Cristau NMUed btrfs-tools in Wheezy yesterday[1], you
may want to update your package lists, too.)
# apt-get update

..., fetch the version from testing (assuming you have a deb-line with
testing in your sources.list, too) and downgrade to it, ...
# apt-get install -t testing btrfs-tools

... or, if you haven't done "apt-get clean" for a while, you may be able to
just do
# dpkg -i /var/cache/apt/archives/btrfs-tools_0.19+20121004-1_*.deb

Then call sync to make sure the new version is on disk:

# sync

and reboot, e.g. by pressing Ctrl-D.

That way, both, Christian and me got working systems back again.


[1] http://packages.qa.debian.org/b/btrfs-tools/news/20130228T204729Z.html

                Regards, Axel
-- 
 ,''`.  |  Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-    |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5

--- End Message ---
--- Begin Message ---
Source: btrfs-tools
Source-Version: 0.19+20130131-3+really20121004-1

We believe that the bug you reported is fixed in the latest version of
btrfs-tools, which is due to be installed in the Debian FTP archive.

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 701...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luk Claes <l...@debian.org> (supplier of updated btrfs-tools 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 ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sun, 10 Mar 2013 22:28:39 +0100
Source: btrfs-tools
Binary: btrfs-tools btrfs-tools-udeb btrfs-tools-dbg
Architecture: source amd64
Version: 0.19+20130131-3+really20121004-1
Distribution: unstable
Urgency: low
Maintainer: Luk Claes <l...@debian.org>
Changed-By: Luk Claes <l...@debian.org>
Description: 
 btrfs-tools - Checksumming Copy on Write Filesystem utilities
 btrfs-tools-dbg - Checksumming Copy on Write Filesystem utilities (debug)
 btrfs-tools-udeb - Checksumming Copy on Write Filesystem utilities (udeb) 
(udeb)
Closes: 701936
Changes: 
 btrfs-tools (0.19+20130131-3+really20121004-1) unstable; urgency=low
 .
   * Taking over maintenance with maintainer's consent.
   * Reverting to previous upstream (Closes: #701936).
Checksums-Sha1: 
 a51fe2d39b3b301cd353a6933fda4a3ecef776a8 2068 
btrfs-tools_0.19+20130131-3+really20121004-1.dsc
 6b8587744f6c7ea221ec4b6eaf2ad20a0cf3d1f7 188784 
btrfs-tools_0.19+20130131-3+really20121004.orig.tar.xz
 20727b50ac35922311af4e397876da1410f18416 10488 
btrfs-tools_0.19+20130131-3+really20121004-1.debian.tar.xz
 0f713c1c23a4e4a035fe25e79057b0047b2a417b 277780 
btrfs-tools_0.19+20130131-3+really20121004-1_amd64.deb
 410875e94f568ed033ea49f6edcb26d87773c948 120506 
btrfs-tools-udeb_0.19+20130131-3+really20121004-1_amd64.udeb
 49e6da101e78428bee160a349ac6b30869eae47f 4509996 
btrfs-tools-dbg_0.19+20130131-3+really20121004-1_amd64.deb
Checksums-Sha256: 
 086e092962bd1e9a9534a14ec05d2840e00e0ad6b718c26dc4cac15d7e2e8cb4 2068 
btrfs-tools_0.19+20130131-3+really20121004-1.dsc
 3e504ccc322b3a19b4e69f5ca92a54e31dbdcf442f1427898feadfb71f391c68 188784 
btrfs-tools_0.19+20130131-3+really20121004.orig.tar.xz
 45d3f2da04a6cb26ded4063b5ddec99867b5db4d98dde1f765bce634ab13b4f7 10488 
btrfs-tools_0.19+20130131-3+really20121004-1.debian.tar.xz
 473af4dc3dba77bdf854eeff20302c12d6059ba9d0eeebe094e40c5f26684dbe 277780 
btrfs-tools_0.19+20130131-3+really20121004-1_amd64.deb
 dc842701b8c37d63d92a002a06a81ca3a6ebdc813137259720c06070dac86832 120506 
btrfs-tools-udeb_0.19+20130131-3+really20121004-1_amd64.udeb
 cafce1670bbe7a8aea6adfddcd9af4b7cdf5d023b12ac0645976d7356d5395e0 4509996 
btrfs-tools-dbg_0.19+20130131-3+really20121004-1_amd64.deb
Files: 
 3f4f0c95ae5b92bd1fde3866c25c64ad 2068 admin optional 
btrfs-tools_0.19+20130131-3+really20121004-1.dsc
 e248c6429a38c0828a0b6c1b06e1ce61 188784 admin optional 
btrfs-tools_0.19+20130131-3+really20121004.orig.tar.xz
 da0921467d84de40bc1cbb00abc31aaa 10488 admin optional 
btrfs-tools_0.19+20130131-3+really20121004-1.debian.tar.xz
 27fcec34639739037dda4951640f473e 277780 admin optional 
btrfs-tools_0.19+20130131-3+really20121004-1_amd64.deb
 62ada4275bdeb5d002de2ef6e193191c 120506 debian-installer optional 
btrfs-tools-udeb_0.19+20130131-3+really20121004-1_amd64.udeb
 f2d792de98be80b2b6231625c4b77046 4509996 debug extra 
btrfs-tools-dbg_0.19+20130131-3+really20121004-1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIbBAEBAgAGBQJRPQRAAAoJECEnNxubsjBiUCAP+LVUtvzIXUCLuiZLKsOqaxoT
FAkQqnXnHukZIFozlhdgJCCfqKXgQhtUi4LFXQYLZb6lniSZDItglA1500N7S8bv
+pDrtNH5ePeMdrTTxjo2y0EvzySOUpTfU0J0iw0hM4z/X/bwgSt/+4hTnO9RIOdi
HdtqT4UpsE+nhtNE1Yt9YTAta2U7rlZzzut6pNR4ZLHzf6fKoUgMx+sgMX32f9sJ
8SOoY4J0Uh/PBj7ZVZSbom9BYSUy1OLKvVablJWyDqPy86TgLkD1RIpe5NNSSqO9
K9DyxeHfbcbBDRqIG5IolNEAWG9fbpILfzaXl5Hqhn31uN+RLEiiFqwHQ1W5/tFT
sRx8WzIjZ4MJtgoO6dkAx0N0EFea8rq3XBtv/t4VMMVs2AwEL3UKwzLIXfcyEmgz
JdoMie6ILKUPB/Rs6bU0qA20gmAhjIxecgHXAtR1dtqpxow1/+cq15dDRazwqwun
HY2ULHawXdJKRibMPhw8ZYynwUarRJiAwSGa7SYc6+RYY+oXu/05S+iZt1HaJFV7
omFM7+3ALfTkNWBo7OhfOZb/cFBI8UZVXdrEliSu9Sg72/AKJQdLflzZFyjr+wzF
fuPftQeBb42lXfVM9NGbSdd36JCNF85YkoCHDygf4W8+BHCtHs4YKqq0Ck/G2aMb
zzq3vMqLntX565bKW/c=
=GHnm
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to