Debian Bug report logs - #585568
please provide non-initramfs-tools integration

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Christoph Anton Mitterer <calestyo@scientia.net>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: btrfs-tools: add "btrfsctl -a" for systems not using initramfs images

Date: Fri, 11 Jun 2010 22:05:30 +0200

Package: btrfs-tools
Version: 0.19+20100601-2
Severity: normal

Hi.

This is in principle a follow-up to #559710.

While your hooks solve the problem for systems using initramfs-images
it's still open for systems without initramfs at all (which is totally
legal I guess).

I'm however not sure how to do this the right way:
1) I guess it must be an init script that reverse depends (LSB header
X-Start-Before) on "$local_fs".

2) Does btrfsctl automatically load the btrfs module, or do we have to
manully do that before? (which is somehow ugly IMO)

3) The script should not fail if the module cannot be loaded, perhaps
just warn, that scanning could not be performed.
btrfs-tools might be installed, but a custom kernel might be used without
btrfs being compiled as module or statically.

4) Is there a good way to prevent doubled scanning, if that already
happened in the initramfs?


Cheers,
Chris.



-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.33-heisenberg (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages btrfs-tools depends on:
ii  e2fslibs                1.41.12-2        ext2/ext3/ext4 file system librari
ii  libc6                   2.11.1-3         Embedded GNU C Library: Shared lib
ii  libcomerr2              1.41.12-2        common error description library
ii  libuuid1                2.17.2-3         Universally Unique ID library
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

btrfs-tools recommends no packages.

btrfs-tools suggests no packages.

-- no debconf information

Message #10 received at 585568@bugs.debian.org (full text, mbox, reply):

From: Christoph Anton Mitterer <calestyo@scientia.net>

To: 585568@bugs.debian.org

Subject: Re: btrfs-tools: add "btrfsctl -a" for systems not using initramfs images

Date: Fri, 11 Jun 2010 22:18:34 +0200

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

btw: There was a similar issue in read hat
(https://bugzilla.redhat.com/show_bug.cgi?id=581204)
Can it be that they solved this cleanly with udev?

Cheers,
Chris.

[smime.p7s (application/x-pkcs7-signature, attachment)]

Message #15 received at 585568@bugs.debian.org (full text, mbox, reply):

From: Daniel Baumann <daniel@debian.org>

To: Christoph Anton Mitterer <calestyo@scientia.net>

Cc: 585568@bugs.debian.org

Subject: Re: Bug#585568: btrfs-tools: add "btrfsctl -a" for systems not using initramfs images

Date: Fri, 11 Jun 2010 22:19:10 +0200

severity 585568 wishlist
thanks

On 06/11/2010 10:05 PM, Christoph Anton Mitterer wrote:
> While your hooks solve the problem for systems using initramfs-images
> it's still open for systems without initramfs at all (which is totally
> legal I guess).

is it? there are many things that don't work properly once you don't use
an initrd with initramfs-tools.

i'm not sure it's worth the effors to support non-initramfs related
things, in particular because the fsck -a goes away at some point anyway
(am currently thinking about just applying the patch to add -a and be
done with it).

> 1) I guess it must be an init script that reverse depends (LSB header
> X-Start-Before) on "$local_fs".

correct.

> 2) Does btrfsctl automatically load the btrfs module, or do we have to
> manully do that before? (which is somehow ugly IMO)

off-hand i'd say no, but didn't check (rebooting now sucks :).

> 4) Is there a good way to prevent doubled scanning, if that already
> happened in the initramfs?

the initramfs script could touch something in /var/tmp (or somewhere
like that), and the initscript could skip if the file is found.

-- 
Address:        Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email:          daniel.baumann@panthera-systems.net
Internet:       http://people.panthera-systems.net/~daniel-baumann/

Message #22 received at 585568@bugs.debian.org (full text, mbox, reply):

From: Christoph Anton Mitterer <calestyo@scientia.net>

To: daniel@debian.org

Cc: 585568@bugs.debian.org

Subject: Re: Bug#585568: btrfs-tools: add "btrfsctl -a" for systems not using initramfs images

Date: Fri, 11 Jun 2010 22:28:00 +0200

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

On Fri, 2010-06-11 at 22:19 +0200, Daniel Baumann wrote:
> is it? there are many things that don't work properly once you don't
> use
> an initrd with initramfs-tools.
Does it? I did so very long and still have several systems that use no
initrd.
I think we should not start to "force" users to using such things, if
not necessary :)


> i'm not sure it's worth the effors to support non-initramfs related
> things, in particular because the fsck -a goes away at some point
> anyway
Uhm... you mean btrfsctl -a? Or btrfsck -a?
Has upstream announced this? And is the module than doing the scan?


> (am currently thinking about just applying the patch to add -a and be
> done with it).
Well perhaps you can have a look at that redhat udev thingy,... (I'm
absolutely no udev expert ^^) whether this is a better solution.

In the end I'd like to see that both initramfs/non-initramfs systems
support this,... and that stuff is only added to the initramfs if needed
(see #584714) :)


> > 2) Does btrfsctl automatically load the btrfs module, or do we have
> to
> > manully do that before? (which is somehow ugly IMO)
> off-hand i'd say no, but didn't check (rebooting now sucks :).
^^ dito  ;)


> > 4) Is there a good way to prevent doubled scanning, if that already
> > happened in the initramfs?
> the initramfs script could touch something in /var/tmp (or somewhere
> like that), and the initscript could skip if the file is found.
Yeah,.. the would also be the first solution that came across my mind,..
but better /tmp,.. I guess, as /var/tmp is not clean


Cheers,
Chris.

[smime.p7s (application/x-pkcs7-signature, attachment)]

Message #27 received at 585568@bugs.debian.org (full text, mbox, reply):

From: Christoph Anton Mitterer <calestyo@scientia.net>

To: 585568@bugs.debian.org

Subject: Re: btrfs-tools: add "btrfsctl -a" for systems not using initramfs images

Date: Sat, 12 Jun 2010 01:09:15 +0200

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

btw: A udev based solution would have the advantage, that it covers also
any hotplugged devices, which may have btrfs filesystems... :)

Cheers,
Chris.

[smime.p7s (application/x-pkcs7-signature, attachment)]

Message #34 received at 585568@bugs.debian.org (full text, mbox, reply):

From: Adrian Friedli <adi@koalatux.ch>

To: 585568@bugs.debian.org

Subject: Re: btrfs-tools: add "btrfsctl -a" for systems not using initramfs images

Date: Sun, 5 Sep 2010 04:13:49 +0200

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

tags 585568 patch
thank you

Hallo

I've written an init script for this by copying most of the things from the 
lvm init script. This is also useful if you don't have your root filesystem on 
the btrfs raid, so you could drop the btrfs stuff from the initramfs.

I used "btrfs device scan" instead of "btrfsctl -a" because I think it's now 
the recommended way.

Cheers, Adi

[btrfs.init (application/x-shellscript, attachment)]

Message #41 received at 585568@bugs.debian.org (full text, mbox, reply):

From: Maik Zumstrull <maik@zumstrull.net>

To: 585568@bugs.debian.org

Subject: Late devices

Date: Sat, 22 Jan 2011 01:30:17 +0100

In my opinion, this bug should be upgraded from wishlist and retitled.
There is a real need to scan for btrfs filesystems later than at the
initramfs stage, because of devices that don't exist yet at that
point. That includes not only actual hotplugging of the hardware, but
also late-open cryptsetup and lvm devices, and other things that come
up late like network block devices or complex HW-RAID setups. As a
specific example, two-disk btrfs over dm-crypt fails mount -a even
with initramfs, because the dm-crypt devices don't exist during the
first and only scan.
Initrd-less boot should be supported as a side effect if you have udev
trigger btrfs device scan.

Message #50 received at 585568@bugs.debian.org (full text, mbox, reply):

From: Martin Steigerwald <Martin@lichtvoll.de>

To: 585568@bugs.debian.org

Subject: udev rules for btrfs device scan and more

Date: Mon, 9 Apr 2012 14:13:18 +0200

Hi!

Please see my two mails to

please support raid configurations automatically
http://bugs.debian.org/cgi-bin/634658

dracut already ships with udev rules that do btrfs device scan and more.

I suggested merging of this and my bug report already as it seems that I 
created a duplicate.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

Message #55 received at 585568-close@bugs.debian.org (full text, mbox, reply):

From: Daniel Baumann <daniel.baumann@progress-technologies.net>

To: 585568-close@bugs.debian.org

Subject: Bug#585568: fixed in btrfs-tools 0.19+20120328-3

Date: Wed, 13 Jun 2012 15:03:34 +0000

Source: btrfs-tools
Source-Version: 0.19+20120328-3

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:

btrfs-tools-dbg_0.19+20120328-3_i386.deb
  to main/b/btrfs-tools/btrfs-tools-dbg_0.19+20120328-3_i386.deb
btrfs-tools-udeb_0.19+20120328-3_i386.udeb
  to main/b/btrfs-tools/btrfs-tools-udeb_0.19+20120328-3_i386.udeb
btrfs-tools_0.19+20120328-3.debian.tar.gz
  to main/b/btrfs-tools/btrfs-tools_0.19+20120328-3.debian.tar.gz
btrfs-tools_0.19+20120328-3.dsc
  to main/b/btrfs-tools/btrfs-tools_0.19+20120328-3.dsc
btrfs-tools_0.19+20120328-3_i386.deb
  to main/b/btrfs-tools/btrfs-tools_0.19+20120328-3_i386.deb



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

Debian distribution maintenance software
pp.
Daniel Baumann <daniel.baumann@progress-technologies.net> (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 ftpmaster@debian.org)


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

Format: 1.8
Date: Wed, 13 Jun 2012 16:00:13 +0200
Source: btrfs-tools
Binary: btrfs-tools btrfs-tools-udeb btrfs-tools-dbg
Architecture: source i386
Version: 0.19+20120328-3
Distribution: unstable
Urgency: low
Maintainer: Daniel Baumann <daniel.baumann@progress-technologies.net>
Changed-By: Daniel Baumann <daniel.baumann@progress-technologies.net>
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: 567681 571300 585568 612809 634658 638778 642302 653632 668832
Changes: 
 btrfs-tools (0.19+20120328-3) unstable; urgency=low
 .
   * Adding udev rule to automatically call 'btrfs scan' upon discovering
     btrfs devices in order to allow using btrfs raid devices
     automatically (Closes: #585568, #634658, #653632).
   * Adding patch to update btrfs manpage to match /sbin/btrfs (Closes:
     #638778, #642302).
   * Also including /sbin/btrfs in udeb.
   * Adding patch from Sten Heinze <shze@gmx.de> to ignore all arguments
     starting with -a in btrfsck for the time being (Closes: #567681,
     #571300, #612809, #668832).
   * Adding back symlink for fsck.btrfs.
Checksums-Sha1: 
 4efdfc048d66127949392438d0886f9f56596496 1339 btrfs-tools_0.19+20120328-3.dsc
 cf6580067f46115b1ee9159e00d0a2cdb7011d13 9043 btrfs-tools_0.19+20120328-3.debian.tar.gz
 f162921cea5af9920053c52210e9f4c2a895cd6e 1173790 btrfs-tools_0.19+20120328-3_i386.deb
 84abb003ed5c4a0b55a7b60fe5447695e79317f8 104622 btrfs-tools-udeb_0.19+20120328-3_i386.udeb
 4187c9cc7969b9c13904c120d94929fe57524f98 3836424 btrfs-tools-dbg_0.19+20120328-3_i386.deb
Checksums-Sha256: 
 90daf54742c19b83f6a832d0ea56ddddf2cd63e5730250896d5dfdf3e254c9ef 1339 btrfs-tools_0.19+20120328-3.dsc
 1881ca47b49d6e17aafd2dc54b5e908861b4aa1b2c3a9d85b7d12c5d437538af 9043 btrfs-tools_0.19+20120328-3.debian.tar.gz
 12ab6d3c468c1277a3821aa764b4820841e6543ab89341a307e286596dceb808 1173790 btrfs-tools_0.19+20120328-3_i386.deb
 1c429a90b86cdae50e058393db4224f1788b7b6227d39bda1b829ae7b2b2f000 104622 btrfs-tools-udeb_0.19+20120328-3_i386.udeb
 c7fd45963c5fb2f65f1745c2729b377a588300c944313d16f0a3200ad5c87523 3836424 btrfs-tools-dbg_0.19+20120328-3_i386.deb
Files: 
 fa56ea2f1fe66c26b0c3899e51769cb0 1339 admin optional btrfs-tools_0.19+20120328-3.dsc
 96b50748fb4dd937902c69d104d9b743 9043 admin optional btrfs-tools_0.19+20120328-3.debian.tar.gz
 c2e9c7e2c01632ebb07e3af8b452d559 1173790 admin optional btrfs-tools_0.19+20120328-3_i386.deb
 debd19bd53f1a2ea33500ee3b53b29c2 104622 debian-installer optional btrfs-tools-udeb_0.19+20120328-3_i386.udeb
 1e55f6484e287c5239d36b46d30f6ec7 3836424 debug extra btrfs-tools-dbg_0.19+20120328-3_i386.deb
Package-Type: udeb

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

iEYEARECAAYFAk/YnZkACgkQ+C5cwEsrK54pOQCgk/yPeK8r9vvt5/W93dj5L9yv
3w4AoI4Z0xf3QYEsW9ZoqNVliv2Jn3OT
=M/i1
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.