Package: btrfs-tools Version: 0.19-8 Severity: normal /etc/init.d/checkroot.sh runs fsck with an option of either -a or -y (depending on a configuration variable).
Since fsck.btrfs supports neither option, when root is on btrfs,
it does not get fscked at boot.
I'm not sure how important fscking is for btrfs. I'm also uncertian
whether fsck.btrfs would even be safe to run at boot, given that its
man page says only offline filesystems (read-only good enough?).
So this bug is either about an ugly boot message ("Could not open -a"),
or a data risking loss of fscking. You decide. :-)
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.31-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages btrfs-tools depends on:
ii e2fslibs 1.41.10-1 ext2/ext3/ext4 file system librari
ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib
ii libcomerr2 1.41.10-1 common error description library
ii libuuid1 2.16.2-0 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.
-- debconf-show failed
--
see shy jo
signature.asc
Description: Digital signature
