Your message dated Thu, 6 Jun 2013 00:12:28 +0200 with message-id <[email protected]> and subject line Closing has caused the Debian Bug report #572535, regarding btrfs-tools: Wrong size shown of btrfs partition after migrating from ext4 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 [email protected] immediately.) -- 572535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572535 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: btrfs-tools Version: 0.19-8 Severity: important Hi, I migrated from ext4 to btrfs using btrfs-convert. If I check the size of each partitions using df -h or btrfs-show, both of them give me wrong size of one of migrated partitions as shown below: btrfs-show: --------------------------------------------------------------------------------- Label: none uuid: 08f9f21a-92b9-4fa8-936b-35f10a649d5e Total devices 1 FS bytes used 1.39GB devid 1 size 1.00GB used 1.00GB path /dev/mapper/linux_lvm-debian_home Btrfs Btrfs v0.19 --------------------------------------------------------------------------------- df -h: --------------------------------------------------------------------------------- Filesystem Size Used Avail Use% Mounted on /dev/mapper/linux_lvm-debian_home 1.0G -64Z -428M 100% /home --------------------------------------------------------------------------------- fsck.btrfs -f /dev/mapper/linux_lvm-debian_home : --------------------------------------------------------------------------------- root 256 inode 257 errors 800 found 752316416 bytes used err is 1 total csum bytes: 617340 total tree bytes: 29261824 total fs tree bytes: 25804800 btree space waste bytes: 6544740 file data blocks allocated: 1356222464 referenced 1311866880 Btrfs Btrfs v0.19 --------------------------------------------------------------------------------- As you can see, no correct info about partition size are given. Because even if it is a partition with no space left, I am able to write there some files in total size of more than few tens of MB without any message talking about no space left on device or something like that. Have a look below: --------------------------------------------------------------------------------- pato@debian:~$ du -h tublatanka/ 28M tublatanka/ pato@debian:~$ cp tublatanka/ ./test -r pato@debian:~$ du -h tublatanka/ test/ 28M tublatanka/ 28M test/ --------------------------------------------------------------------------------- If more info would be needed, just ask, i'll be watching this bug. Thank you very much. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages btrfs-tools depends on: ii e2fslibs 1.41.10-1 ext2/ext3/ext4 file system librari ii libc6 2.10.2-6 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. -- no debconf information
--- End Message ---
--- Begin Message ---Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.0 / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to [email protected] with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz
--- End Message ---
